On Sat, 2009-02-21 at 09:51 +0900, Stephen Gunnell wrote: > Now with my professional configuration and release manager hat on I > would be saying that monthly releases are awfully ambitious for anyone > not doing tightly controlled RAD, XP or a similar fast cycle development > methodology. As a configuration manager I would reject this numbering > scheme if it came from any project under my authority.
This team is already doing monthly releases, and has been for an awfully long time. There's no silver bullet methodology here; there are some basic procedures and guidelines, backed up by a lot of JFDI. Remember, some high-velocity web teams are known for doing *daily* releases. Parrot doesn't do that (and perhaps can't/shouldn't), but as a simple fact Parrot has matched its monthly release schedule better than just about any project I know of has matched *any* release schedule, in or out of the FOSS space. Having led software teams in both high- and low-velocity companies, and written and maintained change management software (and thus tracked a plethora of amazing ways plans and schedules go awry), I continue to be impressed by this. -'f _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
