On Mon, Apr 26, 2010 at 8:54 AM, Michael McCandless < luc...@mikemccandless.com> wrote:
> > Changes that go into stable need to be merged forwards to unstable -- > this may happen commit by commit, or be periodically swept, or some > combination (like flex) -- we can hash out this logistical detail out > with time. > > -1. Instead trunk (unstable) should have all the latest features, and appropriate things merged back to the stable branch. This gives the added benefit of not needing to freeze development for long periods of time while releases are happening, etc. -- Robert Muir rcm...@gmail.com
