Re: Stance on patch releases

2014-11-08 Thread Jason van Zyl
+1 On Nov 8, 2014, at 9:52 AM, Kristian Rosenvold wrote: > We had a lot of trolling about not deleting git tags; but I think they > all left us. Personally it seems to me like it does not really matter > all that much; and I'm still here :) > > if you rewrite a tag it will be updated once you

Re: Stance on patch releases

2014-11-08 Thread Kristian Rosenvold
We had a lot of trolling about not deleting git tags; but I think they all left us. Personally it seems to me like it does not really matter all that much; and I'm still here :) if you rewrite a tag it will be updated once you refresh from the remote. There is a danger some replication settings ma

RE: Stance on patch releases

2014-11-08 Thread Gary Gregory
IMO you never delete a tag that has a VOTE associated with it.  Gary Original message From: Mirko Friedenhagen Date:11/08/2014 07:15 (GMT-05:00) To: Maven Developers List Subject: Stance on patch releases Hello, now that I canceled the vote on maven-pmd-plugin 3.3

Re: Stance on patch releases

2014-11-08 Thread Hervé BOUTEMY
I'm not a git expert, then my explanations are to be confirmed >From what I understood, there is no problem on canonical ASF repo not github mirror. The problem is for people who cloned the repo or updated their clone with initial tag: they don't get the tag update unless they manually delete t

Re: Stance on patch releases

2014-11-08 Thread Igor Fedorenko
If you haven't pushed the tag, it is perfectly safe to delete and recreate it. If you did push, however, the new tag will have to be propagated manually in each and every clone. You can find more details in [1], look for "On Re-tagging" section. Even without git, I find artifacts with the same ve

Re: Stance on patch releases

2014-11-08 Thread Karl Heinz Marbaise
Hi, On 11/8/14 1:21 PM, Hervé BOUTEMY wrote: for svn, in the past, we've deleted and reused the tag but the release manager decides if he wants to create a new tag: it doesn't hurt for git, we've seen deleting a tag is not really possible in a safe way, so there is only one solution Hmare t

Re: Stance on patch releases

2014-11-08 Thread Andreas Gudian
I would just respin the release with version 3.3. With Subversion it's not that big a deal to delete a tag (with a proper comment) and recreate it for the re-spin. With git it would be a big no-no to replace an already pushed tag, that's why I create the final tag only after the vote completed and

Re: Stance on patch releases

2014-11-08 Thread Karl Heinz Marbaise
Hi Mirco, I i had to cancel a vote i have deleted the tag, cause it does not made it to the real public and recreated after fixing the problem... Based on staging you have the choice of going back Kind regards Karl Heinz Marbaise -

Re: Stance on patch releases

2014-11-08 Thread Hervé BOUTEMY
for svn, in the past, we've deleted and reused the tag but the release manager decides if he wants to create a new tag: it doesn't hurt for git, we've seen deleting a tag is not really possible in a safe way, so there is only one solution Regards, Hervé Le samedi 8 novembre 2014 13:15:21 Mirk

Stance on patch releases

2014-11-08 Thread Mirko Friedenhagen
Hello, now that I canceled the vote on maven-pmd-plugin 3.3 should I go for 3.3.1 or _delete_ and _reuse_ the tag. Or may the release responsible decide this on his own? I am always in favor of creating a new tag. Regards Mirko -- Sent from my mobile