I will be adding the grid stuff to the master today.
Most of the modifications are fixes and new commands implementations,
nothing to worry about. I will test everything and create the correspondent
jira issues during the day.
I will be online today and tomorrow to be sure that nothing wrongs happens
with that.
Greetings.
On Wed, Apr 20, 2011 at 10:34 AM, Geoffrey De Smet
<ge0ffrey.spam(a)gmail.com>wrote:
Nexus is down, so hudson is useless.
I 'll be running a last full build of the M2 release branches locally
tonight over dinner:
$ droolsjbpm-build-bootstrap/script/mvn-all.sh -Dfull clean install
If everything succeeds (and nexus is alive again), I* 'll release M2
tomorrow morning.*
Stop me if you need to stop the M2 release :)
Other please restrain yourself from sneaking in anything on M2 (or I 'll
have to start over):
CR1 will be branched from master soon and released soon too.
Op 19-04-11 16:41, Geoffrey De Smet schreef:
Hi guys,
The release branches are made.
These branches are called *5.2.0.M2.x* for all git repositories
(droolsjbpm-knowledge, drools, guvnor, ...),
except for jbpm, where the branch is called 5.1.0.M1.x instead.
*So now, anything you commit to master, will be for CR1, and will not be
included in the M2 release.*
If you need certain commits to be included in the M2 release, you 'll have
to git cherry pick them to the release branch from master.
Cherry pick with the Eclipse or IntelliJ plugin or use the git command
line:
http://progit.org/book/ch5-3.html
Switching to the release branch
====================
If you just have guvnor cloned:
$ cd guvnor
It's easy to switch your files to the branch:
$ git checkout 5.2.0.M2.x
And to go back to master:
$ git checkout master
But if you have all of droolsjbpm projects cloned, there's a script to help
you:
$ droolsjbpm-build-bootstrap/script/branches/git-checkout-all.sh
5.2.0.M2.x 5.1.0.M1.x
And to go back to master:
$ droolsjbpm-build-bootstrap/script/branches/git-checkout-all.sh master
master
Note: "droolsjbpm-build-bootstrap/script/git-all.sh checkout 5.2.0.M2.x"
doesn't work
because it tries to checkout the wrong branch on jbpm.
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-dev mailing
listrules-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/rules-dev
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev