hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Wang <andrew.w...@cloudera.com>
Subject Re: Setting JIRA fix versions for 3.0.0 releases
Date Thu, 21 Jul 2016 19:33:12 GMT
I really, really want a 3.0.0-alpha1 ASAP, since it's basically impossible
for downstreams to test incompat changes and new features without a release
artifact. I've been doing test builds, and branch-3.0.0-alpha1 is ready for
an RC besides possibly this fix version issue.

I'm not too worried about splitting community bandwidth, for the following

* 3.0.0-alpha1 is very explicitly an alpha, which means no quality or
compatibility guarantees. It needs less vetting than a 2.x release.
* Given that 3.0.0 is still in alpha, there aren't many true showstopper
bugs. Most blockers I see are also apply to both 2.x as well as 3.0.0.
* Community bandwidth isn't zero-sum. This particularly applies to people
working on features that are only present in trunk, like EC, shell script
rewrite, etc.

Longer-term, I assume the 2.x line is not ending with 2.8. So we'd still
have the issue of things committed for 2.9.0 that will be appearing for the
first time in 3.0.0-alpha1. Assuming a script exists to fix up 2.9 JIRAs,
it's only incrementally more work to also fix up 2.8 and other unreleased
versions too.


On Thu, Jul 21, 2016 at 11:53 AM, Vinod Kumar Vavilapalli <
vinodkv@apache.org> wrote:

> The L & N fixes just went out, I’m working to push out 2.7.3 - running
> into a Nexus issue. Once that goes out, I’ll immediately do a 2.8.0.
> Like I requested before in one of the 3.x threads, can we just line up
> 3.0.0-alpha1 right behind 2.8.0?
> That simplifies most of this confusion, we can avoid splitting the
> bandwidth from the community on fixing blockers / vetting these concurrent
> releases. Waiting a little more for 3.0.0 alpha to avoid most of this is
> worth it, IMO.
> Thanks
> +Vinod
> > On Jul 21, 2016, at 11:34 AM, Andrew Wang <andrew.wang@cloudera.com>
> wrote:
> >
> > Hi all,
> >
> > Since we're planning to spin releases off of both branch-2 and trunk, the
> > changelog for 3.0.0-alpha1 based on JIRA information isn't accurate. This
> > is because historically, we've only set 2.x fix versions, and 2.8.0 and
> > 2.9.0 and etc have not been released. So there's a whole bunch of changes
> > which will show up for the first time in 3.0.0-alpha1.
> >
> > I think I can write a script to (carefully) add 3.0.0-alpha1 to these
> > JIRAs, but I figured I'd give a heads up here in case anyone felt
> > differently. I can also update the HowToCommit page to match.
> >
> > Thanks,
> > Andrew

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message