[development] Please be careful marking release nodes "Security update"

Frederik 'Freso' S. Olesen freso.dk at gmail.com
Thu Oct 25 09:18:26 UTC 2007

2007/10/25, Karoly Negyesi <karoly at negyesi.net>:
>>Could we add a flag that say "change the use of the DB"?
>>If it doesn't, testing/upgrading is just a matter of moving a
>>directory and copy the new version in the right place.
>>If there is some change at the DB level (schema or code that use the
>>DB) a backup would be a more conservative choice.
>DB and API changes must happen in a new branch. Any given branch
>should not contain anything else but bugfixes just like Drupal core.

Several Drupal modules have their own database tables – I think this
was meant as for changes to those. (Since this thread is about
developers working in contrib to begin with.) And I doubt all contrib
authors know about that branching rule – and even if they do, they
might make branches that don't change the DB, and as such would still
be a simple file replacing.

Frederik 'Freso' S. Olesen <http://freso.dk/>

More information about the development mailing list