Just to be clear (since I can see a few started committing CR3/3.1.1 fix-for issues) the .x branch is still locked down until we get CR2 build out.
That CR2 build is happening right now so it shouldn't be long before we can get CR3 fixes committed.
While we crunch through the issues being found in various parts of the system both branch and trunk are in codefreeze.
Thus don't do commits that are not directly marked as fix for CR2 in jira. If you find a critical/blocker/indoubt issue raise it with me, Dennis or Brian before
committing - if you can't reach any of us then raise the jira and post on the mailing list so we become aware of any new blocker issue.
If you do not have jira's assigned to you for the CR2 release, now is the time to try out our builds (as opposed to use them directly from Eclipse PDE which
doesn't always give the right picture) and see if things works as you expect them to and explore the other new features we got now.
I expect the codefreeze for trunk to be lifted early next week - but for now we are locking down to ensure minimum impact.
Relaying from Nick concerning branching:
> JBoss Tools is branched (rev 20257):
> Existing CR2 builds will now pull from the branches.
> New CR3 builds will pull from trunk; however, there should really be
> new development in trunk at this point since the CR3 builds are really
> just GA.
> JBoss Tools Schedule reminder:
> JBT 31 CodeFreeze 2010-02-10 (delayed for Maven 0.10
> Eclipse/WTP RC4 avail* 2010-02-17
> JBT 31 CR2 2010-02-17
> Galileo SR2 GA avail 2010-02-25
> JBT 31 GA 2010-03-02
> * The last two Eclipse M builds failed to compile so there will
> definitely be an RC4 tomorrow or next week which we'll need to adopt