Do you think we didn't cover that appropriately in the ANNOUNCE email
and/or the release notes?
I wouldn't have expected anything more from Hadoop Weekly than "apache
foo x.y.z, 1-2 high-level changes, read more _here_"
Sean Busbey wrote:
I think we also need a formal announcement that the branch is EOM and may
only be resuscitated for critical security issues (and may not at that).
To illustrate the need, I noticed the 1.5.3 release made Hadoop Weekly but
there was no mention that it is the last expected 1.5.z release.
On Tue, Jul 7, 2015 at 3:46 PM, Christopher<[email protected]> wrote:
Good point.
On Tue, Jul 7, 2015, 15:36 Josh Elser<[email protected]> wrote:
Upgrade testing out of 1.5.x to 1.6 or 1.7?
Christopher wrote:
What else is there to do for 1.5 EOL? We've indicated this already in
the 1.5.3 release announcement and we've removed the 1.5 development
branch. As far as I'm concerned, I think the last remaining thing to
do is to archive the 1.5 parts of the website... and I see no
particular rush for that. We can do it along with the next minor or
major release.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, Jul 7, 2015 at 11:58 AM, Sean Busbey<[email protected]>
wrote:
I'd like to see the 1.5 EOL happen.
On Mon, Jul 6, 2015 at 3:04 PM, Josh Elser<[email protected]>
wrote:
Thanks to the efforts spearheaded by Christopher and verified by
everyone
else, we now have 1.5.3 and 1.6.3 releases!
To keep the ball rolling, what's next? High level questions that come
to
mind...
* When do we do 1.7.1 and/or 1.8.0?
* What bug-fixes do we have outstanding for 1.7.1?
* What other minor improvements do people want for 1.8.0?
* Where does 2.0.0 stand? Should we make a bigger effort to getting
the
new client API stuff Christopher had started into Apache?
Feel free to brainstorm here and/or on JIRA (tagging relevant issues
to
the desired fixVersion)
- Josh
--
Sean
