If Sean doesn't have the time, I probably need to circle around and
accrue some more "positive release karma" for myself. Seems like there's
nothing explicitly marked as required now.
Any "wants" that people have in the pipeline? Explicit (JIRA id) or
exploratory (wanted to look at $x before a release).
On 6/13/17 2:22 PM, Christopher wrote:
Usually such discussions are in the context of an anticipated release. Are
you planning to champion a release soon? I'd be in favor of a maintenance
release or two.
On Tue, Jun 13, 2017 at 4:57 PM Sean Busbey <[email protected]> wrote:
Right, I believe we'd be pushing out any non-completed issues to a
future release. Presumably if any of those TODOs required waiting for
a release they'd be marked blocker, or someone here would have them in
mind?
On Tue, Jun 13, 2017 at 12:45 PM, Christopher <[email protected]> wrote:
Link to issues, by release branch:
https://issues.apache.org/jira/projects/ACCUMULO?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
On Tue, Jun 13, 2017 at 3:09 PM Sean Busbey <[email protected]> wrote:
Here's how we're doing on lag for releases:
* branch-1.7, last maintenance release March 25th 2017, 9 issues marked
done, no blockers
* branch-1.8, last maintenance release Feb 26th 2017, 14 issues marked
done, no blockers
* master, last minor release September 6th 2016, last major release May
2014, 80 issues marked done, 3 things marked blocker
Anyone know of any other blockers on releases right now?
Folks have time for a discussion about wether or not we should keep
things
currently marked blocker as blocker?
--
busbey
