Same here. --Grant
On 3 Nov, 2008, at 10:05, Jeffrey Harris wrote: > +1 > > Jeffrey > > Jared Rhine wrote: >> A while back, OSAF adopted a two-branch-commit policy for >> development. >> When development velocity is high, it's helpful to be stabilizing one >> branch while using trunk as an experimental branch. >> >> This is kind of a pain because everything needs to be committed >> twice. >> The overall procedure is reasonable, but just not needed for >> slower-moving projects. >> >> I propose we officially switch the Chandler Desktop subversion >> policy to >> "commit only to trunk", then we branch from trunk when we're ready to >> stabilize a release. >> >> I made a similar proposal for the Cosmo tree. There weren't any >> takers, >> but the thought process is pretty much the same: >> >> http://lists.osafoundation.org/pipermail/cosmo-dev/2008-October/006126.html >> >> The number of active committers is low right now, so if we get at >> least >> one +1 and no -1s, we can just implement the policy change. Trunk >> and >> the active branch should be in sync right now except for the >> Ubuntu-related patches I just made to trunk. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
