On 28 November 2012 13:50, Simon IJskes - QCG <si...@qcg.nl> wrote: > On 28-11-12 14:40, Peter Firmstone wrote: > >> Can we have a shared skunk branch? At present we each have our own >> skunk branches. >> > > Good idea. Lets try it. > > I concur, who else should we seek agreement from?
> > I think that what Sim was trying to achieve was a more cohesive >> collaborative approach by developing in trunk, I think we could have >> that with a shared skunk development branch. >> > > Indeed, but this new idea of yours works has more benefits. > > Agreed. > > At stable points the skunk development branch can replace trunk. We >> might have a period of refactoring and bug fixing, followed by a period >> of stabilisation, testing and documenting, before replacing trunk, then >> branching off a release. >> > > I would patch or selectively merge from skunk to trunk in this case. > > > I'd also like to see the qa test suite broken out and managed >> separately, this would allow the same test libraries to run against both >> skunk development and trunk branches. >> > > Please explain some more. > > Gr. Sim > > > -- > QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl > Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397 >
