On 29/01/2019 17:24, Stephen Kitt wrote: > Hi, > > In last week’s TSC call we had a brief discussion around the use of > branches. One issue that comes up regularly is what to use the various > branches for, and it occurred to me that we might be missing a branch > (groan). > > When we start the freeze, we cut stable branches, and since we’re > trying to be ever more rigorous, those stable branches are only > supposed to receive fixes for blocking bugs. What master is used for > then is up to each project, but typically it ends up receiving patches > for the next release cycle (Sodium now). What’s missing in this > scenario is somewhere to queue patches for the next service release > (Neon SR1), at least until the freeze is over and we thaw the stable > branches.
Well, we always have this gap around code freezes -- even when you freeze for SR1, there is gap. Now the primary question is why is this a pain and how exactly these additional branches fold into the general lifecycle, especially when release train overlap is considered -- for all the projects I work on they end up being pure overhead... Regards, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
