I think it would be fine to auto-close most remaining branch-1 issues
even if the branch is still formally considered alive. I don't expect us
to create a new 1.x release unless a security vulnerability or critical
bug forces it. Closing all non-critical issues would match with the
reality that
Closing out the JIRAs as Auto Closed or Closed due to Inactivity seems
reasonable to me. For branch-1, we can be more aggressive. We should
probably do the same less aggressively for other branches too.
On Fri, May 8, 2015 at 11:01 AM, Arun C Murthy acmur...@apache.org wrote:
+1
Arun
On May
+1
Arun
On May 8, 2015, at 10:41 AM, Allen Wittenauer a...@altiscale.com wrote:
May we declare this branch dead and just close bugs (but not
necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has
any intention of working on the 1.3 release, especially
I would be -1 to declaring the branch dead just yet. There have been 7
commits to that branch this year. I know this isn't comparable to trunk or
branch-2, but it is not negligible either.
I propose we come up with a policy for deprecating past major release
branches. May be, something along the
May we declare this branch dead and just close bugs (but not
necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any
intention of working on the 1.3 release, especially given that 1.2.1 was Aug
2013 ….
I guess we need a PMC member to declare a