Hi Krzysztof,
Just saw I forgot to hit send earlier today. We can use a branch or just revert the commit and reapply it afterwards. I ended up choosing the latter approach, but either solution would have worked fine, I guess. Thanks, Gert On Mon, Jul 21, 2014 at 11:57 PM, Krzysztof Sobkowiak <[email protected]> wrote: > Hi Gert > > Could we create a temporary branches from the commit before Karaf > upgrade (and eventually cherry-pick the later commits) and release from > the branches? > > Best regards > Krzysztof > > On 21.07.2014 09:30, Gert Vanthienen wrote: >> L.S., >> >> >> I though we were planning to do 5.0.3/5.1.1 with Karaf 2.3.4 and then >> follow up with 5.0.4/5.1.2 for the upgrade to Karaf 2.3.6. When I was >> looking into doing some of these builds over the weekend, I noticed >> the codebase got upgraded to 2.3.6-SNAPSHOT last week, so that was a >> bit confusing. I probably have some time today and tomorrow to cut >> those two releases, but if we prefer waiting around for the Karaf >> 2.3.6 release, that would be fine for me too. >> >> >> Regards,ate >> >> Gert Vanthienen >> >> >> On Mon, Jul 14, 2014 at 12:47 PM, Sobkowiak, Krzysztof >> <[email protected]> wrote: >>> +1 for SMX 5.0.3 and 5.1.1 with current code base and 5.0.4 and 5.1.2 >>> with Karaf 2.3.6. >>> +1 for SMX 5.2.x with Karaf 2.4.0 >>> >>> With SMX 6 we should wait until Karaf 3.0.2 is available and contains >>> the fix for the deploy folder problem. >>> >>> Best regards >>> Krzysztof >>> >>> >>> > > > -- > Krzysztof Sobkowiak > > JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer > @ ASF > Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center > <http://www.pl.capgemini-sdm.com/> | Wroclaw > e-mail: [email protected] <mailto:[email protected]> | > Twitter: @KSobkowiak > Calendar: http://goo.gl/yvsebC
