aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sweeney <kevi...@apache.org>
Subject Re: [DISCUSS] Use $(git describe) output to bake version instead of .auroraversion
Date Wed, 09 Apr 2014 20:55:11 GMT
My thought is that if I want to build the source distributions that got
published for release 0.5.0 I should be able to clone the repo, run git
checkout 0.5.0, ./gradlew ...; ./pants ... and produce the same things we
publish to the apache mirrors. It's my understanding that ASF convention is
to have -rcN versions come before the unqualified release so we'd have
0.5.0-rc1, then 0.5.0-rc2, then finally 0.5.0. I guess the -snapshot could
be considered superfluous here.


On Wed, Apr 9, 2014 at 1:40 PM, Jay Buffington <me@jaybuff.com> wrote:

> On Mon, Apr 7, 2014 at 8:05 PM, Kevin Sweeney <kevints@apache.org> wrote:
>
> >
> > If I create a tag when .auroraversion is updated to a new -snapshot on
> > master like so (we haven't had a release yet but assume I did this during
> > the release of 0.4.0):
> >
> > % git tag -a -m 'Create 0.5.0-snapshot' 0.5.0-snapshot
> > 19e087509cfd6c86c9928ca6c8e8b40068a64f39
> >
>
> What is the point of the "-snapshot" in the tag name?
>
> The linux kernel does this:
>
>     $ git tag -l |grep 3.14
>     v3.14
>     v3.14-rc1
>     v3.14-rc2
>     v3.14-rc3
>     v3.14-rc4
>     v3.14-rc5
>     v3.14-rc6
>     v3.14-rc7
>     v3.14-rc8
>
>     $ git describe
>     v3.14-12236-g39de65a
>
> Git itself follows that same pattern:
>
>     $ git tag -l |grep 1.9
>     v1.9-rc0
>     v1.9-rc1
>     v1.9-rc2
>     v1.9.0
>     v1.9.0-rc3
>     v1.9.1
>
>     $ git describe
>     v1.9.1-506-g7bf272c
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message