ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: Ignite-1.5 Release
Date Mon, 30 Nov 2015 17:23:20 GMT
Raul, I see your point. However

1. I see nothing wrong in having EA perpetually available. I would even
prefer all vendors to keep all EA versions available just for tracking and
history purposes.
2. Even if we choose not to do maven release we can still go with EA and
just leave staging repo unreleased.


2015-11-30 20:17 GMT+03:00 Raul Kripalani <raulk@apache.org>:

> On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov <yzhdanov@apache.org>
> wrote:
> > Raul, every build submitted for vote is RC (so, on first iteration this
> > will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
> > official release. My idea is to have EA available via maven and from the
> > website.
> >
> Aha, I see. I'm not sure I like the idea of pushing the EA to Maven Central
> and making it live there perpetually. After 3 years, we would still have an
> 1.5.0.EA there.
> Red Hat is a company that uses EAs quite often. They have a separate Maven
> repo for them, from which they prune the EAs once they become GA.
> I prefer that we publish a RC1 to a staging repo and inform our users via
> mailing list. All they'd have to do to take 1.5.0-RC1 for a spin is add the
> staging repo to their pom.xml.
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk

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