Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Sun, 27 Sep 2015 02:30:37 -0700
From: Konstantin Boudnik <cos@apache.org>
To: dev@ignite.apache.org
Subject: Re: version names
Message-ID: <20150927093037.GW19314@boudnik.org>
Mail-Followup-To: dev@ignite.apache.org
References: <20150926161659.GN19314@boudnik.org>
 <CAKoNANt9vDD3JDoBE_U1tA9kkK+udUzs8gRKWnZAz1cLqXG8nw@mail.gmail.com>
 <20150927092022.GU19314@boudnik.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20150927092022.GU19314@boudnik.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Sun, Sep 27, 2015 at 02:20AM, Konstantin Boudnik wrote:
> On Sat, Sep 26, 2015 at 09:23PM, Raul Kripalani wrote:
> > Agree. And we should also normalise tag names and branch names in Git if
> > they aren't (cannot check now).
> 
> Tag names aren't much of the concern IMO, but it won't hurt either. Version
> numbers are more visible, and their mishandling might have dire consequences.
> 
> > What do you think about creating a new branch per release like it's being
> > done now?
> > 
> > In other projects (OSS and non-OSS) we tend to create and leave open a
> > maintenance branch once per minor version (e.g. ignite-1.4) rather can
> > creating and deleting branches for every particular version. We do this
> > once the first release in that maintenance line is cut from master.

One more thing (should re-read my own emails before sending them ;) - why
creating a maintenance branch if there's no plans (yet?!) to release a minor
update? And once the release is tagged it is save to drop the branch without
fear of confusing the release tip with anything else. 

Thanks

> We have this lengthy discussion a few months back
>     http://apache-ignite-developers.2346864.n4.nabble.com/Git-branches-and-development-process-tp889p945.html
> 
> and it got settled. 
> 
> Cos
> 
> > On 26 Sep 2015 17:16, "Konstantin Boudnik" <cos@apache.org> wrote:
> > 
> > > On a somewhat similar note: I just noticed that our versions have prefix
> > > "ignite-". Do we really need it? It is sorta obvious that these are
> > > Ignite's
> > > versions, not httpd's :) It seems a bit confusing that JIRA versions still
> > > aren't the same as the release ones.
> > >
> > > Shall we move to just numerical versions like 1.5 and so on and do it
> > > starting from 1.5?
> > >
> > > Cos
> > >
> > > ----- Forwarded message from Dmitriy Setrakyan <dsetrakyan@apache.org>
> > > -----
> > >
> > > Date: Sat, 26 Sep 2015 10:50:08 -0500
> > > From: Dmitriy Setrakyan <dsetrakyan@apache.org>
> > > To: dev@ignite.apache.org
> > > Subject: Re: Need Project Admin rights on JIRA
> > >
> > > Done.
> > >
> > > On Sat, Sep 26, 2015 at 5:27 AM, Raul Kripalani <raulk@apache.org> wrote:
> > >
> > > > Hi guys,
> > > >
> > > > I need project admin rights for Ignite in JIRA so I can add a new release
> > > > ignite-1.4.1.
> > > >
> > > > For future releases, it would be great if the release manager adds the
> > > next
> > > > micro [and minor [and major]] versions in JIRA when cutting the first RC.
> > > >
> > > > 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
> > > >
> > >
> > > ----- End forwarded message -----
> > >