[Gluster-devel] v3.5qa2 tag name on master is annoying

[Kaushal M]

This sounds perfect.

On Thu, Jul 10, 2014 at 2:15 PM, Niels de Vos <ndevos at redhat.com> wrote:
> On Wed, Jul 09, 2014 at 09:33:01PM +0100, Justin Clift wrote:
>> That v3.5qa2 tag name on master is annoying, due to the RPM
>> naming it causes when building on master.
>>
>> Did we figure out a solution?
>>
>> Maybe we should do a v3.6<something> tag at feature freeze
>> time or something?
>
> I think we can push a "v3.6dev" tag to master, it should reference
> a commit after the release-3.5 branch-point.
>
> The first 3.6 release would be something like "v3.6.0alpha", possibly
> adding "v3.6.0alpha1", and subsequent "v3.6.0beta" + "N".
>
> Comparing versions can be done in the RPM-way like this:
>
>     $ rpmdev-vercmp 3.6dev 3.6.0alpha1
>     0:3.6.0alpha1-None is newer
>
> When branching release-3.6, we'll need a tag for the master branch
> again, maybe "v3.7dev"?
>
> HTH,
> Niels
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-devel