-Re: Version of future alpha release of Sqoop2
Arvind Prabhakar 2012-10-23, 16:38
Thanks for the suggestion, and apologies for the late response. I too feel
that having version number is better than label qualifiers such as alpha.
Overall, I like this proposal and think it will be useful for our
community. I have a couple of optional suggestions to go with it:
1. We create a page on our Wiki that details this scheme so that users can
understand what state a release is in, and
2. Have a criteria established for switching over to the 2.0.0 version
Of course, we can address these independent of adopting the version scheme,
so it does not have to be blocked on anything.
On Fri, Oct 19, 2012 at 10:16 AM, Cheolsoo Park <[EMAIL PROTECTED]>wrote:
> Hi Jarcec,
> I like your suggestion of 1.99.x. That seems intuitive and clear what it's
> supposed to mean to me.
> On Fri, Oct 12, 2012 at 1:42 PM, Jarek Jarcec Cecho <[EMAIL PROTECTED]
> > Hi Sqoop(2) developers,
> > we're making very good progress in Sqoop 2 land. Current code base still
> > can't move any data around, but I'm sure that we're very close to have
> > something usable and testable soon. With this regard, I would like to
> > propose doing some
> > pre/alpha/beta/unstable/preview/pick-your-own-word-for-unstable-code
> > release as soon as possible to provide early adopters first testable
> > My motivation to provide early bits is to get feedback from actual users
> > soon as possible, so that we can incorporate good ideas before it will
> > become too expensive.
> > However releasing such early state raises question what version should we
> > release. I would say that most simple idea is to release version "2.0.0",
> > however due to unstable nature, I believe that it's very bad idea. Hadoop
> > seems to be adding "-alpha" to the version names, for example
> > "2.0.1-alpha". I don't quite like this solution as I would personally
> > expect that there will be 2.0.1 stable (without "alpha" suffix) that
> > have any new features but will be stable soon. As this won't be the case
> > for Sqoop, I would like to propose slightly different solution that I've
> > seen in some other projects. I would like to propose doing release
> > I believe that the version number implies that it's very far from current
> > stable 1.4 version and very very near to 2.0, but it's not 2.0 yet. I
> > like to see other opinions about using 1.99.1 version for first cut of
> > Sqoop 2 branch.
> > I actually did not invent this idea - I've seen in before. For example
> > project  is using very similar approach for quite some time by now as
> > you can see on their archive . Versions like 4.8.90 or 4.8.95 are
> > "pre-releases" for 4.9. Another example would be Ubuntu one client .
> > Jarcec
> > Links:
> > 1: http://mirror.nexcess.net/apache/hadoop/common/hadoop-2.0.1-alpha/
> > 2: http://kde.org/
> > 3: http://download.kde.org/unstable/
> > 4: https://launchpad.net/ubuntuone-client/stable-4-0