We are changing the milestone process to make it clearer and to save people from having to work nights to push out the milestone bits.
First, on the announced milestone date a branch will be created for the milestone. Specific time is subject to discussion, but since creating a branch is a pretty simple process it can be delegated as needed. Nobody should need to stay up late just to create a branch. Once the branch has been created, instructions on how to pull the branch are sent out (by whoever made the branch). After this point development on the trunk can continue as usual. Development on the branch is effectively stopped. Checkins happen by exception only. QA and release start creating candidate builds that are smoketested, and verified against past demos. These may happen the same date, or may be pushed to the next day if it is late. Smoketests should pass, and it should be possible to demo everything that was demoed before. If smoketests or demos cannot be run, they are filed as regression bugs and are blocking the milestone. Fixes for these blocker regressions are allowed on the branch. These must be reviewed before checkin. They are high priority. Once QA and release verifies smoketests pass and demos can be run the official milestone bits are made and the milestone is published. -- Heikki Toivonen for himself, Lisa, Sheila, Philippe, Aparna, Katie, Ted
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
