Re: [h5md-user] git branch 1.0

[Felix Höfling]

Good idea, please go ahead.

Just a little thing: I would like to ensure that the finally published  
manuscript (the first "official" version) corresponds to version 1.0 (and  
not 1.0.2 or so). So I would tag it still as a RC or similar. Also not  
sure whether there is really a need for 3-level version numbers. (Fixing  
typos does not deserve a separate version number IMHO).

Felix


Am 01.09.2013, 17:19 Uhr, schrieb Peter Colberg  
<address@hidden>:

> Hi all,
>
> We recently submitted a manuscript introducing H5MD to the scientific
> community, which will take a few months until publication. Since the
> specification part of that article and the specification on Savannah
> are to be identical, this means that the 1.0.0 tag will not be pushed
> until the end of the year.
>
> I suggest we add a git branch 1.0 for the current version of the
> specification, and collect minor fixes (e.g., spelling corrections) in
> this stable branch. This allows the development of the specification
> to progress in the master branch.
>
> I would setup the build server to consider tags and branches, e.g.,
>
> current       -> http://nongnu.org/h5md/
> branch 1.0    -> http://nongnu.org/h5md/1.0/
> version 1.0.0 -> http://nongnu.org/h5md/1.0.0/
>
> Peter