On segunda-feira, 6 de agosto de 2012 21.22.27, [email protected] wrote: > What do others think?
Thanks for putting it together. I like it. It's what we had discussed over a
year ago and it makes sense to me.
I think that the patch release process could be adjusted a little. For
example, the Release Team might decide that too many changes have gone in and
start the process sooner, rather than later. It's their decision, which must
be justified.
One think I'd like to know from others is: what does dripping-bucket contain
when changes are not going in, in-between releases? From the description and
from the graph, it sounds like that branch contains the next release before it
is tested out. That is, it's a branch that is in a state of Release Candidate
all the time because the final notches on the actual release haven't been done.
If we move the release testing onto leaky-faucet, then dripping-bucket
contains only the latest release, with at most a critical patch or two.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
