[rules-dev] Quite a few commits on master that look like bug fixes are not on the 5.2.x branch and are not in CR1 (and final)

[Geoffrey De Smet]

Hi guys,

Since the branch was made on Friday morning, there have been quite a few 
commits on master.
Some of these are refactorings/features/improvements, which we don't 
want on the 5.2.x as they will jeopardize the stability of the release.

But quite a few of those commits are bug fixes and many of those bug 
fixes haven't been cherry-picked to the 5.2.x,
so *those commits will not be in CR1 (and final).*



Here's an easy way to compare the commits on master and the branch:
   https://github.com/droolsjbpm/drools/commits/master
   https://github.com/droolsjbpm/drools/commits/5.2.x

The dev mail about the creation fo the 5.2.x branch:
http://drools.46999.n3.nabble.com/Branch-date-for-5-2-x-CR-1-and-final-Thursday-28-APR-8-00-GMT-tp2847477p2878719.html 

   "If you want any of your not-yet-pushed commits to be included in the 
5.2.0 release,
   you 'll have to cherry pick those commits from master to the release 
branch."

To learn how to cherry pick:
http://drools.46999.n3.nabble.com/Cherry-picking-with-git-from-master-to-5-2-x-branch-tp2882486p2882486.html 


-- 
With kind regards,
Geoffrey De Smet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20110501/9ec86073/attachment.html