Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Mon, 21 Dec 2015 22:28:13 -0800
From: Konstantin Boudnik <cos@apache.org>
To: dev@ignite.apache.org
Subject: Re: 1.5 GA
Message-ID: <20151222062813.GG10680@tpx>
Mail-Followup-To: dev@ignite.apache.org
References: 
 <CA+0=VoW9UrdFStcJSU3-UkUhiPRGz+W=53D8PvfxNfE58CTmtg@mail.gmail.com>
 <CAHG4OXtSQPW7EDyRbg12UTYOmjH8wPoSZihENJGhwPjVsDtVPA@mail.gmail.com>
 <CAGcMBHgDFBLBN2s3Vb48zBBKf=asOt4QS4LRHBdaLsMM5Re1SA@mail.gmail.com>
 <CAKoNANvT67PEDN2+dyXkb=n-gLUgQth_1FuP6fsyeizO=QsBVw@mail.gmail.com>
 <20151218043012.GE5478@tpx>
 <CAGcMBHi6hDWE+WmzAsA4byDekwzmtB8MzBA+nk10EmWY7-q8xA@mail.gmail.com>
 <CAOKDqC-wowP=Rx=d4R2o-XWJQ5Wp0qttfZ90PAFAY405TZhxcg@mail.gmail.com>
 <CAOKDqC90s+j4Ats6WCjJznt-GZ=dzyjmLdB4mVx-EMa=tP4KXg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="7lMq7vMTJT4tNk0a"
Content-Disposition: inline
In-Reply-To: 
 <CAOKDqC90s+j4Ats6WCjJznt-GZ=dzyjmLdB4mVx-EMa=tP4KXg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--7lMq7vMTJT4tNk0a
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Well, being too close to the release doesn't mean that we need to rush and
produce yet another one that will be causing troubles downstream.

There's nothing to research really. Just dump the string suffixes in the
versions and be happy. They are solving nothing, but create confusion and
incompatibilities.

Cos

On Fri, Dec 18, 2015 at 12:32PM, Anton Vinogradov wrote:
> Cos,
>=20
> I'm affraid that we already too close to release that we have no chances
> for one more delay.
> Also we should research how to fix this issue in correct way.
> Possible we have to replace "-" with "." and gain 1.x.0.b1 & 1.x.0.final =
as
> a result, but I'm not sure it will not break compatibility with some other
> case.
>=20
> Raul & Sergi,
>=20
> Could you please check that usage of "." instead of "-" is a good case?
>=20
> On Fri, Dec 18, 2015 at 10:19 AM, Anton Vinogradov <avinogradov@gridgain.=
com
> > wrote:
>=20
> > Yakov,
> >
> > ignite-1.5.0-b1-rc1
> > <https://git-wip-us.apache.org/repos/asf?p=3Dignite.git;a=3Dcommit;h=3D=
f51c051d1e588855c37774efb22cd3536f512aa3> was
> > correct.
> > 1.5.0-b1
> > <https://git-wip-us.apache.org/repos/asf?p=3Dignite.git;a=3Dcommit;h=3D=
f51c051d1e588855c37774efb22cd3536f512aa3> -
> > now correct too, was fixed.
> > Both (now) points to the same commit.
> >
> > On Fri, Dec 18, 2015 at 7:40 AM, Yakov Zhdanov <yzhdanov@apache.org>
> > wrote:
> >
> >> Cos, rc tag was fine. Problem was with release one. Anton V. is that
> >> correct?
> >>
> >> Yakov
> >> On Dec 18, 2015 10:32, "Konstantin Boudnik" <cos@apache.org> wrote:
> >>
> >> > Was VOTE done against the tag pointed to the incorrect commit?
> >> >
> >> > Cos
> >> >
> >> > On Mon, Dec 14, 2015 at 12:59PM, Raul Kripalani wrote:
> >> > > On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov <yzhdanov@apache.o=
rg>
> >> > wrote:
> >> > >
> >> > > > osgi has been pushed to 1.5 after b1 has been built. You can bui=
ld
> >> > ignite
> >> > > > binaries from ignite-1.5 branch to test the functionality.
> >> > > >
> >> > >
> >> > > Then the 1.5.0-b1 tag is incorrect. It points
> >> > > to 9a14d6432932fc1a1fdf2ddd77dea920382efe8c which would have inclu=
ded
> >> > OSGi.
> >> > >
> >> > > Could you please fix the tag to point to the commit you actually b=
uilt
> >> > the
> >> > > release from?
> >> > >
> >> > > Thanks,
> >> > >
> >> > > *Ra=C3=BAl Kripalani*
> >> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big D=
ata
> >> and
> >> > > Messaging Engineer
> >> > > http://about.me/raulkripalani |
> >> http://www.linkedin.com/in/raulkripalani
> >> > > http://blog.raulkr.net | twitter: @raulvk
> >> >
> >>
> >
> >

--7lMq7vMTJT4tNk0a
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iF4EAREIAAYFAlZ47XwACgkQenyFlstYjhIoEwD/UXu9ycAvw6UBK/lkFec8OCgl
rBy33GJXEkR96wZpASkBANfs4nal9X2YwmieGteOfrzHhPyXpvuOhgKpDv62k4eG
=q72w
-----END PGP SIGNATURE-----

--7lMq7vMTJT4tNk0a--