> 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

Sorry for not being more active these days, I've just left my previous
job for a new one and moved 300kms south, so I don't have much spare
time for Trac at the moment ;-(

Cheers,
Manu

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to