[jbosstools-dev] ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?

[Max Rydahl Andersen]

Seems noone spotted this email - could everyone who are part of the core builds report back on the 5 items ?

"1) tested your component works on M5
> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise it)
> 3) issues marked with N&N so you can get them documented
> 4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we still have to do this "too high jump" in our current setup -hopefully can fix before next big version)
> 5) Branched your component with jbosstools-4.1.Alpha1x "


Please note the branch is jbosstools-4.1.Alpha1x  (note the x)

/max

Begin forwarded message:

> From: Max Rydahl Andersen <max.andersen at redhat.com>
> Subject: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
> Date: 31 Jan 2013 12:25:43 EST
> To: jbosstools-dev jbosstools-dev <jbosstools-dev at lists.jboss.org>
> 
> Hey,
> 
> If we branched for JBT 4.1 Alpha next week would you be ok ?
> 
> Koen and Denis did an awesome job of at least getting Hibernate JPA/Dali integration compiling this week.
> 
> And as Nick announced our simplest plan moving forward is to compile JBT 4.1 which will be basis for JBDS 7 against Kepler (theoretically we could have something working 
> on both but it would be a massive QE effort).
> 
> Eclipse Kepler M5 is coming out Friday so we might still have some issues but Nick/Mistria will be setting up a M5 based target platform as soon as possible.
> 
> It would be great if we could get out an early Alpha to get some traction and figure out what issues we got to fight when it all comes together.
> 
> Could you let me know ASAP if you have any issues/concerns with doing a branch next week for an Alpha build ? Would you be ready ?
> 
> Being ready for this means: 
> 1) tested your component works on M5
> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise it)
> 3) issues marked with N&N so you can get them documented
> 4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we still have to do this "too high jump" in our current setup -hopefully can fix before next big version)
> 5) Branched your component with jbosstools-4.1.Alpha1x 
> 
> Please let me know if you are ready for that or have questions/concerns.
> 
> Thanks,
> Max
> 
>