[jbosstools-dev] Fwd: ACTIONS REQUIRED :: Branching today for CR1 and future 4.1.x releases

[Gorkem Ercan]

Done for cordova tools...

I replied to Nick in the first time

---------- Forwarded message ----------
From: Gorkem Ercan <gorkem.ercan at gmail.com>
Date: Thu, Jun 27, 2013 at 10:10 PM
Subject: Re: [jbosstools-dev] ACTIONS REQUIRED :: Branching today for CR1
and future 4.1.x releases
To: Nick Boldt <nboldt at redhat.com>


All clear for cordova tools

--
Gorkem


On Thu, Jun 27, 2013 at 11:49 AM, Nick Boldt <nboldt at redhat.com> wrote:

> Today is CODE AND FEATURE FREEZE for the upcoming JBT 4.1.0 / JBDS 7.0.0
> releases.
>
> Project leads are required to (at some point today) do the following 5
> steps:
>
> a) switch their project's root pom to point at the JBT parent pom
> version 4.1.0.CR1 (not Beta2 or Beta3).
>
> b) rebuild locally to verify everything still works w/ the updated
> parent pom + target platform
>
> c) read the build log to verify that the TP used is Beta1, and pulls
> Kepler R bits (rather than an Alpha TP with pre-release Kepler bits)
>
> d) create a branch in their project called jbosstools-4.1.x, which will
> be used to build CR1, CRx, GA, and future maintenance.
>
> e) reply to this thread confirming that you're branched and ready for
> CR1 builds to begin this weekend.
>
> ---
>
> Since we are frozen for CR1 today, please keep your changes in the 4.1.x
> branch to a MINIMUM. CRITICAL / BLOCKER issues only, vetted by at least
> 1 other person via JIRA + PR review. Other issues still open against
> your component should be triaged out to the next release (4.1.1 or
> 4.2.x, as fitting).
>
> ---
>
> After branching, master branch will be open for 4.2.x development
> against Eclipse 4.4 (Luna), but we will not have a Luna-based target
> platform for some time. You can also work on 4.1.x / 7.0.x bugfixes
> there, but please track which ones will need to be backported to 4.1.x /
> 7.0.x maintenance releases.
>
> After we release 4.1.0.Final / 7.0.0.GA, the 4.1.x branch will reopen
> for MAINTENANCE FIXES ONLY, and any approved bugfixes done in master
> which need to be backported to the .x branch can be done AT THAT TIME.
>
> ---
>
> Any questions or concerns with this plan, please don't hesitate to ping
> me, Mickael, Max, or Denis, or reply to this thread.
>
> Cheers,
>
> Nick
>
>
> On 06/27/2013 10:57 AM, Max Rydahl Andersen wrote:
> > The branch to use for cr1 is: jbosstools-4.1.x
> >
> > Thats where we will cut cr and final releases from.
> >
> > /max (sent from my phone)
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20130627/5874f381/attachment-0001.html