+1 for reusing SM or creating a new one SMX (without the 5 at the end) Sent from a mobile device Am 06.02.2013 21:46 schrieb "Gert Vanthienen" <[email protected]>:
> L.S., > > > The new development trunk for 5.0 is available at > http://svn.apache.org/repos/asf/servicemix/smx5/trunk/ - I also set up a > CI > build at https://builds.apache.org/job/ServiceMix5/ and a first set of > SNAPSHOTs has been deployed to repository.apache.org. > > The container itself is starting, but several bundles are not starting > correctly (probably due to version mismatches or config changes that are > required by the newer versions of specs, changes in ActiveMQ, ...). Apart > from ironing out these issues, we probably want to convert the integration > tests to pax-exam-karaf as well (cfr. > https://issues.apache.org/jira/browse/SMX4-1282). Let's start raising > JIRA > issues for these remaining issues and tasks, but that brings us to the next > question... > > What would be the best way to track issues for this new release? We could > get a new JIRA for SMX5 as we have for SMX4, but we already have quite a > few JIRA projects to work with. We could also just add a version to > project SMX4 (though this project name might confuse users) or start > re-using the SM project for 5.0.x (since we are no longer actively > maintaining 3.x). Any preferences? > > > Regards, > > Gert > > > On Tue, Feb 5, 2013 at 10:40 AM, Gert Vanthienen > <[email protected]>wrote: > > > L.S., > > > > > > I was planning to move the old code to a branch and set up the build > today > > or tomorrow, so we can start working on this once the 4.5.0 release is > out. > > > > > > Regards, > > > > Gert Vanthienen > > > > > > On Tue, Feb 5, 2013 at 8:13 AM, Henryk Konsek <[email protected]> > wrote: > > > >> > +1 sounds good > >> > >> Facing this swarm of +1s, when do you plan to start working on the SMX > >> 5.0 release? I'll be more than happy to help as much as my limited > >> time resources allow me to :) . > >> > >> -- > >> Henryk Konsek > >> http://henryk-konsek.blogspot.com > >> > > > > >
