| Re: [scout-dev] marking bugs that require a migration |
and - whenever possible - try to avoid fixing bugs in a way that breaks the code of existing scout applications. help to keep the list of bugs requiring a migration as small as possible -----Ursprüngliche Nachricht----- Von: Matthias Zimmermann Gesendet: Donnerstag, 17. Januar 2013 12:29 An: Mailing list for Eclipse Scout developer discussion Betreff: marking bugs that require a migration committers, in case you fix a bug in a way that needs the user to migrate existing code: do the following: 1) add 'Migration Notes:' with a step by step description of the necessary things to do 2) flag this bug as migration relevant by adding the word 'migration' to the bugzilla 'whiteboard' field. doing 2) will make sure the bug is listed in the wiki migration guide [1]. see this bug [2] as an example. tx matthias [1] http://wiki.eclipse.org/Scout/Migration/3.9 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=396871
Attachment:
smime.p7s
Description: S/MIME cryptographic signature