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 V, can you please do it?
--Yakov
2015-09-03 12:05 GMT+03:00 Sergey Kozlov <skoz...@gridgain.com>:
> Hi
>
> Now we've branch ignite-1.4 for release thus make sense to update for
> version for master to 1.5?
>
> --
> Sergey Kozlov
>
in.com>:
> >
> > > Hi
> > >
> > > Now we've branch ignite-1.4 for release thus make sense to update for
> > > version for master to 1.5?
> > >
> > > --
> > > Sergey Kozlov
> > >
> >
>
t; --Yakov
> >
> > 2015-09-03 12:05 GMT+03:00 Sergey Kozlov <skoz...@gridgain.com>:
> >
> > > Hi
> > >
> > > Now we've branch ignite-1.4 for release thus make sense to update for
> > > version for master to 1.5?
> > >
> > > --
> > > Sergey Kozlov
> > >
> >
>
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
ve branch ignite-1.4 for release thus make sense to update for
> > version for master to 1.5?
> >
> > --
> > Sergey Kozlov
> >
>
On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej 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?
On 03.09.2015 14:29, Raul Kripalani wrote:
> On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej 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
Version Updated
On Thu, Sep 3, 2015 at 3:29 PM, Raul Kripalani wrote:
> On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej 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