On Sunday 02 September 2007 4:26:50 pm Eli wrote: > Seeking to improve software quality and move toward a solid 0.11 release, > the following developer policy is proposed: > > 1 Anything beyond a 'trivial' bugfix requires a branch. > 2 A branch must be reviewed and approved by another developer before > merging to trunk. If something is committed to trunk with insufficient > review, anyone can backout changes, preferably to a branch. > 3 Branches should have a purpose statement on t.e.o under TracDev/Branches > and an announcement to trac-dev. > > Votes/Comments?
+1 Comments: 1 I expect 'trivial' new features to use a branch, since they should include unittests for the new functionality and documentation. 2 'backout to a branch' means reverting a changeset on trunk, creating a new branch, and committing the reverted changeset to the new branch. While not strictly required, I do see that as a more polite way of reverting someone else's change. 3 Branches for 'small' changes may skip the wiki page, but there should still be an announcement to trac-dev to gather reviewers. It is critical that we all make the effort to review other developers' branches in a timely manner, and provide useful, constructive feedback as early in the development process as possible. Eli ------------------. "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram [EMAIL PROTECTED] `------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
