Thank you for working on this, Ay, I appreciate it. -- Michael
On 02/05/2017 11:56 AM, Aleksey Yeschenko wrote: > A handy filter to see if you’ve got any JIRAs as assignee/reviewer > that need correction: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20Cassandra%20and%20fixVersion%20%3D%203.x%20and%20statusCategory%20%3D%20Complete%20and%20((reviewer%20%3D%20currentUser())%20or%20(assignee%20%3D%20currentUser())) > > -- AY > > On 5 February 2017 at 17:47:33, Aleksey Yeschenko > (alek...@apache.org) wrote: > > HI all. > > Now that 3.10 has finally been released, I’ve cleaned up several > things, as promised: > > 1. Cherry-picked bug fixes from cassandra-3.X branch into > cassandra-3.11 branch 2. Fixed up CHANGES.txt in both cassandra-3.11 > branch and trunk 3. Dropped cassandra-3.X branch altogether 4. Added > 3.11.x version placeholder, got rid of 3.12 version > > What remains to be done: > > 1. Get rid of 3.x version in JIRA, by relabelling all affected > issues > > For uncommitted future 3.11 bug fixes, please use the new 3.11.x > fixver on JIRA. > > Current merge order: 2.1 -> 2.2 -> 3.0 -> 3.11 -> trunk. > > P.S. While cleaning things up, I’ve noticed a lot of resolved JIRA > issues with .x version placeholders. To committers: please, set the > fixver to a concrete version when resolving the JIRA. Don’t make > others dig through git log to determine where the patch went into > eventually. > > Also, when resolving as Duplicate or Won’t Fix or Not a Problem, > please remove the version in fixversion field altogether. > > Thank you. > > -- AY >
