Excerpts from Maciej (Matchek) Blizinski's message of Wed Oct 14 11:11:30 -0400 2009:
> I suggested that promotions from testing to current and from current > to stable could be done periodically (quarterly?), as snapshots. Bug > and security fixed would be promoted bypassing the periodic schedule. > > Thoughts? Overall, I like this, and I think that my only hesitations on the current draft are related to technical workflow issues (eg: tagging a release and then having it rejected leads to...?). These can certainly be handled. The overall plan/flow looks sound. So, apart from the automation tools required, what is preventing us from implementing this with manual methods now? Can we agree on a point at which we'd be happy to carve off a new stable and begin this process? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
