Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-29 Thread Stian Soiland-Reyes
On 28 September 2016 at 16:40, Mark Struberg wrote: > But otoh if a project decides to use -RC1..17 it's also fine. > BUT: they pollute their branches and tags and they actually would need to do > a 2nd VOTE afterwards on the .Final release. So it is much more work and thus > not recommended. Bu

Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-28 Thread David Nalley
On Mon, Sep 26, 2016 at 4:09 PM, Ate Douma wrote: > Hi Mark, > > On 2016-09-26 17:22, Mark Struberg wrote: >> >> Stian, this is established practice in the ASF since the very early days >> of playing with GIT. >> It is used e.g. in the following TLPs: >> TomEE >> DeltaSpike >> Johnzon >> CouchDB >

Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-28 Thread Mark Struberg
Hi Jochen! The discussion was about whether a local release build (GIT runs locally and a 'commit' doesn't push to the canonical ASF repo) should immediately get pushed to the ASF repo or just to a PMC owned 'other' GIT repo (e.g. on github). In various projects we prefer pushing to github b

Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-28 Thread Jochen Wiedmann
On Mon, Sep 26, 2016 at 10:09 PM, Ate Douma wrote: >> Stian, this is established practice in the ASF since the very early days Could someone please enlighten me, what "this" is about? Thanks, Jochen -- The next time you hear: "Don't reinvent the wheel!" http://www.keystonedevelopment.co.uk

Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-27 Thread Mark Struberg
Hi Ate! Note that the proposed handling is only a 'best practice' tip. It is _not_ mandated. No need to veto the release just because they do it different. If a project does -RCx then it's legally also fine for the ASF. It is just much more work and possibly confusing to users (which browse th

Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-27 Thread Ate Douma
Hi Mark, On 2016-09-27 09:44, Mark Struberg wrote: Hi Ate! It's quite natural that many other projects just point to DeltaSpike. DS was in 2011 amongst the very first projects using GIT at the ASF. One of the results of this effort (together with the CouchDB community) was following document

Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-27 Thread Mark Struberg
PS: back then I also summed up information about the difference between SVN and GIT regarding handling from a user pov http://wiki.apache.org/couchdb/SVNvsGIT Most of it is nowadays common knowledge I hope, but some might still find it useful. LieGrue, strub > On Tuesday, 27 September 2016

Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-27 Thread Mark Struberg
Hi Ate! It's quite natural that many other projects just point to DeltaSpike. DS was in 2011 amongst the very first projects using GIT at the ASF. One of the results of this effort (together with the CouchDB community) was following document http://wiki.apache.org/couchdb/Git_At_Apache_Guide No

Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]

2016-09-26 Thread Ate Douma
Hi Mark, On 2016-09-26 17:22, Mark Struberg wrote: Stian, this is established practice in the ASF since the very early days of playing with GIT. It is used e.g. in the following TLPs: TomEE DeltaSpike Johnzon CouchDB Maven and many, many more! It also got discussed on members, infra and even