On 2012-03-04 10:27, Peter Suter wrote:
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?
I would propose something like Mercurial's release plan:
http://mercurial.selenic.com/wiki/TimeBasedReleasePlan
A release interval of 3 months will make the life easier
for corporate users, since snapshots/dev builds
are not always approved in that kind of environments.
Have a nice day,
Eduard
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-dev@googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
