Jorg Heymans wrote: > > +1, separate release cycles for more and quicker releases. > > We could start this process incrementally today by just deploying > snapshots of the 2.2 core jar. No huge announcements or anything, just > get it out there for the bleeding-edgers and to test the release > process. Once we feel comfortable we can do the same for a few blocks. > To avoid the deployment issue, we can opt to just distribute the jars > and assume the bleeding-edgers being clever enough to add the block > configuration themselves from the docs. > > In parallel we can maintain a core 2.2 archetype that sets up a working > webapp structure for the 2.2 core (and perhaps some samples to > demonstrate). This should satisfy the "curious-but-not-bleeding-edge" > people in their eagerness to explore the new and noteworthy in 2.2 core. > > > How does that sound? > +1
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
