On 04.03.2012 00:50, Ed - 0x1b, Inc. wrote:
pardon the late entry - I have found the OpenBSD fixed cycle a good way to eliminate feature driven release arguments - and it is a lot easier to manage from the users perspective. http://www.youtube.com/watch?v=i7pkyDUX5uM
Interesting talk, but I'm not quite sure how we can apply it to Trac. Did you have a specific point in mind?
Slides: http://www.openbsd.org/papers/asiabsdcon2009-release_engineering/ Summary: * Maximize testing, minimize time lost to release process * Don't split team in developers and release engineers * Freeze development until release is done * Freeze is an unannounced surprise * Force developers to do testing, punish slackers with commit-bans * Do daily builds, don't accept broken builds * Mock people that break builds * Dog food daily builds in day to day development * Do a release after exactly 6 months to the day I guess you mainly referred to that last point? -- Peter -- 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.
