Update version for master

[Sergey Kozlov]

Hi

Now we've branch ignite-1.4 for release thus make sense to update for
version for master to 1.5?

--
Sergey Kozlov

[yzhdanov]

Anton V, can you please do it?

--Yakov

2015-09-03 12:05 GMT+03:00 Sergey Kozlov <[hidden email]>:

> Hi
>
> Now we've branch ignite-1.4 for release thus make sense to update for
> version for master to 1.5?
>
> --
> Sergey Kozlov
>

[Anton Vinogradov]

Should it be 1.5.0-SNAPSHOT?

On Thu, Sep 3, 2015 at 1:32 PM, Yakov Zhdanov <[hidden email]> wrote:

> Anton V, can you please do it?
>
> --Yakov
>
> 2015-09-03 12:05 GMT+03:00 Sergey Kozlov <[hidden email]>:
>
> > Hi
> >
> > Now we've branch ignite-1.4 for release thus make sense to update for
> > version for master to 1.5?
> >
> > --
> > Sergey Kozlov
> >
>

[yzhdanov]

Yes. Correct.
On Sep 3, 2015 14:16, "Anton Vinogradov" <[hidden email]> wrote:

> Should it be 1.5.0-SNAPSHOT?
>
> On Thu, Sep 3, 2015 at 1:32 PM, Yakov Zhdanov <[hidden email]> wrote:
>
> > Anton V, can you please do it?
> >
> > --Yakov
> >
> > 2015-09-03 12:05 GMT+03:00 Sergey Kozlov <[hidden email]>:
> >
> > > Hi
> > >
> > > Now we've branch ignite-1.4 for release thus make sense to update for
> > > version for master to 1.5?
> > >
> > > --
> > > Sergey Kozlov
> > >
> >
>

[Raul Kripalani]

If development of the 1.4.x release line will continue in the ignite-1.4
branch, the master/develop branch should carry 1.5.0-SNAPSHOT (or
2.0.0-SNAPSHOT, depending on the type of changes expected).

BTW - it seems the tag for ignite-1.4.0 is missing:

$ git fetch --tags
$ git tag -l
1.1.3
1.1.4
1.3.1
1.3.2
1.3.2-p2
1.3.3
1.3.3-p1
1.3.3-p2
1.3.3-p3
1.3.3-p4
1.3.3-p5
1.3.3-p6
1.3.3-rc1
ignite-1.0.0
ignite-1.0.1
ignite-1.0.2
ignite-1.0.6-incubating
ignite-1.1.0-incubating
ignite-1.1.0-incubating-rc1
ignite-1.1.0-incubating-rc2
ignite-1.1.0-incubating-rc3
ignite-1.1.0-incubating-rc4
ignite-1.1.0-incubating-rc5
ignite-1.1.0-incubating-rc6
ignite-1.1.0-incubating-rc7
ignite-1.2.0-incubating
ignite-1.2.0-incubating-rc1
ignite-1.2.0-incubating-rc2
ignite-1.3.0-incubating
ignite-1.3.0-incubating-rc1
ignite-1.3.0-incubating-rc2
release-1.0.0-RC1
release-1.0.0-RC2
release-1.0.0-RC3
$

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Sep 3, 2015 at 12:16 PM, Anton Vinogradov <[hidden email]>
wrote:

> Should it be 1.5.0-SNAPSHOT?
>
> On Thu, Sep 3, 2015 at 1:32 PM, Yakov Zhdanov <[hidden email]> wrote:
>
> > Anton V, can you please do it?
> >
> > --Yakov
> >
> > 2015-09-03 12:05 GMT+03:00 Sergey Kozlov <[hidden email]>:
> >
> > > Hi
> > >
> > > Now we've branch ignite-1.4 for release thus make sense to update for
> > > version for master to 1.5?
> > >
> > > --
> > > Sergey Kozlov
> > >
> >
>

[Branko Čibej]

On 03.09.2015 13:47, Raul Kripalani wrote:
> If development of the 1.4.x release line will continue in the ignite-1.4
> branch, the master/develop branch should carry 1.5.0-SNAPSHOT (or
> 2.0.0-SNAPSHOT, depending on the type of changes expected).
>
> BTW - it seems the tag for ignite-1.4.0 is missing:

There hasn't been a 1.4.0 release package yet, so of course no tag?

-- Brane

[Raul Kripalani-2]

On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej <[hidden email]> wrote:

> There hasn't been a 1.4.0 release package yet, so of course no tag?
>

Well, that would explain it ;-) But why is the POM version for both master
and ignite-1.4 branches already on 1.4.1-SNAPSHOT in that case?

https://github.com/apache/ignite/blob/master/pom.xml#L35
https://github.com/apache/ignite/blob/ignite-1.4/pom.xml#L35

Is the 1.4.0 release cut and under VOTE?

Regards,

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

[Branko Čibej]

On 03.09.2015 14:29, Raul Kripalani wrote:
> On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej <[hidden email]> wrote:
>
>> There hasn't been a 1.4.0 release package yet, so of course no tag?
>>
> Well, that would explain it ;-) But why is the POM version for both master
> and ignite-1.4 branches already on 1.4.1-SNAPSHOT in that case?
>
> https://github.com/apache/ignite/blob/master/pom.xml#L35
> https://github.com/apache/ignite/blob/ignite-1.4/pom.xml#L35

No idea ... possibly an oversight.


> Is the 1.4.0 release cut and under VOTE?

I don't see any vote mail, so my best guess is, nope.

-- Brane

[Anton Vinogradov]

Version Updated

On Thu, Sep 3, 2015 at 3:29 PM, Raul Kripalani <[hidden email]> wrote:

> On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej <[hidden email]> wrote:
>
> > There hasn't been a 1.4.0 release package yet, so of course no tag?
> >
>
> Well, that would explain it ;-) But why is the POM version for both master
> and ignite-1.4 branches already on 1.4.1-SNAPSHOT in that case?
>
> https://github.com/apache/ignite/blob/master/pom.xml#L35
> https://github.com/apache/ignite/blob/ignite-1.4/pom.xml#L35
>
> Is the 1.4.0 release cut and under VOTE?
>
> Regards,
>
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>