[rules-dev] 6.0.0.CR1 tagged - procedure for commits from now on

Edson Tirelli ed.tirelli at gmail.com
Thu Jul 25 17:00:51 EDT 2013


   All,

   As you probably know, 6.0.0.CR1 was tagged yesterday and the
corresponding branch (6.0.x) was created last Tuesday.

   As a reminder, since the creation of the branch and until we release
6.0.0.Final:

(1) please cherry-pick all commits you make for master into the 6.0.x
branch. Do not wait to cherry-pick, because this might end up creating
conflicts if commits are cherry-picked out of order. Also don't forget to
cherry-pick.

(2) if there is a BZ and/or JIRA for your work (there should be), add the
BZ/JIRA numbers to your commit message

(3) add the link to your commit as a comment on the corresponding BZ

   Item (3) above is temporary until they fix the BZ/GitHub integration,
but important.

   After we release 6.0.0.Final, you should only cherry-pick commits into
6.0.x branch if they have a corresponding BZ and the 3 acks set.

   Let us know if you have any questions.

   Thanks,
       Edson

-- 
  Edson Tirelli
  Principal Software Engineer
  Red Hat Business Systems and Intelligence Group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20130725/99e25b4e/attachment.html 


More information about the rules-dev mailing list