Versions updated. On Tue, Dec 22, 2015 at 12:36 PM, Anton Vinogradov <avinogra...@gridgain.com > wrote:
> Seems everything is ok, > > https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-b1 > https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-final > > I'll update versions. > > On Tue, Dec 22, 2015 at 12:28 PM, Anton Vinogradov < > avinogra...@gridgain.com> wrote: > >> Dmitriy, >> >> that's not a big change, but we have to check it will not break something >> else. >> I'll check it today. >> >> Raul, >> >> Could you please check this solution is suitable for OSGi? >> >> On Tue, Dec 22, 2015 at 10:04 AM, Dmitriy Setrakyan < >> dsetrak...@apache.org> wrote: >> >>> I filed the ticket: >>> https://issues.apache.org/jira/browse/IGNITE-2226 >>> >>> I think we should change dash to dot for now. >>> >>> Anton, can you explain why this is a big change? >>> >>> D. >>> >>> On Mon, Dec 21, 2015 at 10:28 PM, Konstantin Boudnik <c...@apache.org> >>> wrote: >>> >>> > 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, >>> > > >>> > > 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. >>> > > >>> > > Raul & Sergi, >>> > > >>> > > Could you please check that usage of "." instead of "-" is a good >>> case? >>> > > >>> > > On Fri, Dec 18, 2015 at 10:19 AM, Anton Vinogradov < >>> > avinogra...@gridgain.com >>> > > > wrote: >>> > > >>> > > > Yakov, >>> > > > >>> > > > ignite-1.5.0-b1-rc1 >>> > > > < >>> > >>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3 >>> > >>> > was >>> > > > correct. >>> > > > 1.5.0-b1 >>> > > > < >>> > >>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=f51c051d1e588855c37774efb22cd3536f512aa3 >>> > >>> > - >>> > > > now correct too, was fixed. >>> > > > Both (now) points to the same commit. >>> > > > >>> > > > On Fri, Dec 18, 2015 at 7:40 AM, Yakov Zhdanov < >>> yzhda...@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" <c...@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 < >>> > yzhda...@apache.org> >>> > > >> > wrote: >>> > > >> > > >>> > > >> > > > osgi has been pushed to 1.5 after b1 has been built. You can >>> > build >>> > > >> > 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 >>> > included >>> > > >> > OSGi. >>> > > >> > > >>> > > >> > > Could you please fix the tag to point to the commit you >>> actually >>> > built >>> > > >> > the >>> > > >> > > release from? >>> > > >> > > >>> > > >> > > Thanks, >>> > > >> > > >>> > > >> > > *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 >>> > > >> > >>> > > >> >>> > > > >>> > > > >>> > >>> >> >> >
