To come up with the commit list, I used "git log" to find all commits from
the time of the last release until now, on the master branch.  Then, I
literally reviewed each, looking at the following:

* commit comments
* Jira tickets, if any was identified in the commit comment
* actual code changes

I looked for commits that appear to be important bug fixes, or low-risk
updates.  And I avoided anything that is a pure enhancement (like new
features) or any dependency version changes as they could create
compatibility problems for users.

Honestly, I don't have a strict set of criteria.  And, the process I'm
following, which seems like a good one to me - is to publish the list as
done here and ask for input.

Wheh.

As for the AMQ-5709 fix, I will give Gary a little time in the hopes he will
give some input, and then follow up with you.

Looking at the total list of recent changes, I am considering to target a
May release of 5.12.0, and so I'm personally not too concerned about missing
some useful updates.  However, it would be good to make this release as
useful as possible.  The biggest risk here, with that said, is partial
updates from cherry-picked updates leading to failures - hopefully failures
caught by tests, but even so - with the amount of time it takes to run
tests, a long list of commits increases the chances the entire release will
delay for a significant amount of time.

Another wheh.

I am cherry-picking and looking at clashes.  Already fixed about 3 or 4;
they were minor.  Even one which I couldn't understand why it was a conflict
as the local side of the conflict was empty.  If the conflicts for a commit
are great and involved, I'll likely note it here and then drop it from the
release unless someone else wants to help on that front.

Finally, my branch plan - work directly off the 5.10.x branch locally.  Once
I have all the commits in the branch, run a full build.  If all passes, then
I'll push the branch and continue the release process.  Otherwise, I'll
resolve failures, rinse-and-repeat.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/HEADSUP-ActiveMQ-5-10-3-release-preparation-tp4695445p4695463.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Reply via email to