Matt Good wrote: > Ilias Lazaridis wrote: > > Are there any repository commit guidelines within the trac project? > > > > If not, those here could serve as a foundation to create some > > guidelines: > > > > http://dev.lazaridis.com/base/wiki/CommitGuidelines > > Well, I think most of those fall under common sense,
Isn't "common sense" a main topic of disagreement? > and the developers already follow them. I cannot rate if they've followed "them" here, (as the policies are unspecified): http://trac.edgewall.org/ticket/4001 24h broken trunk > Marking commits as "draft" or whatever isn't > really necessary since experimental development only happens in the > sandbox. that would not be about 'experimental' but about (collaborative) 'incremental' development. in 'trunk' in 'branches' or 'sandboxes'. > All commits to the trunk should be pretty stable. They "should". The Guide should state the process for what happens if they are not, thus anyone can act. - Just Thoughts - The Team Decides! . --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
