Re: [Gluster-devel] v3.5qa2 tag name on master is annoying
On 2014-07-09 22:39, Harshavardhana wrote: I thought pkg-version in build-aux should have fixed this properly? Well, it does generate correct ascending names, but since 'git describe' picks up the v3.5qa2 tag, new package names are based on that (and hence yum considers 3.5.1 newer than master). On Wed, Jul 9, 2014 at 1:33 PM, Justin Clift jus...@gluster.org 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.6something tag at feature freeze time or something? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.5qa2 tag name on master is annoying
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.6something 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@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.5qa2 tag name on master is annoying
This sounds perfect. On Thu, Jul 10, 2014 at 2:15 PM, Niels de Vos nde...@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.6something 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@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.5qa2 tag name on master is annoying
On 07/10/2014 02:23 PM, Justin Clift wrote: On 10/07/2014, at 9:45 AM, Niels de Vos 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.6something 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? Yeah, that sounds like a workable approach. Who wants to push the tag to master to make that happen? :) Since we are very close to branching release-3.6 (over this weekend), I will do the following: 1. Create the first release from release-3.6 branch as v3.6.0alpha1 2. Create a new v3.7dev tag in the master branch after release-3.6 is in place. Thanks, Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] v3.5qa2 tag name on master is annoying
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.6something tag at feature freeze time or something? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] v3.5qa2 tag name on master is annoying
I thought pkg-version in build-aux should have fixed this properly? On Wed, Jul 9, 2014 at 1:33 PM, Justin Clift jus...@gluster.org 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.6something tag at feature freeze time or something? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
