Carsten Ziegeler wrote: > Let's move this into a different thread :) > > Daniel Fagerstrom wrote: > >>>I'd say, let's release 2.2M1 at the same time as 2.1.8, say, just after >>>the GetTogether. >> >> >>+1 >> >>When the OSGi stuff are changed to R4 and is usefull enough we can start >>to include it within 2.2.x releases for early adaptors. And when it is >>stable enough and we have all infrastructure in terms of block >>repositories, deploy tools, build system etc in place, we can remove the >>"classic" way and release a 3.0. >> > > Ok, this sound reasonable. I see currently two major things that have to > be done for releasing a version of 2.2: > > a) Sync 2.1.x and 2.2: Many things that have been added to 2.1.x are not > in 2.2 yet; this has to be fixed. we have just over 50 blocks, so if > everyone syncs between one and four blocks, we can get over this very > quickly. > b) Adjust the build scripts to exclude the osgi stuff as Daniel suggested. > > If these things are fixed, +1 for 2.2M1 after the GT. > > Carsten > And releasing 2.2 would mean that *NO NEW FEATURES GO TO 2.1.x* from this point on :)
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
