I renamed it instead of deleting, just in case.

On Thu, Jan 19, 2012 at 9:07 PM, Les Hazlewood <[email protected]> wrote:
> Correction, it will affect our existing tag - I have to delete it so
> the re-release can use that same name.
>
> On Thu, Jan 19, 2012 at 9:05 PM, Les Hazlewood <[email protected]> wrote:
>> (P.S. I'll be doing this from the 1.2.x branch, so it won't affect
>> trunk or our existing tag and shouldn't conflict/interrupt anyone)
>>
>> On Thu, Jan 19, 2012 at 9:04 PM, Les Hazlewood <[email protected]> wrote:
>>> This seems to be devolving instead of improving.
>>>
>>> I'm going to just delete the openid4j module entirely (it is in the
>>> trunk, we won't 'lose' it), re-run the full release, use the
>>> 'shiro-root-1.2.0' tag name and start a new VOTE thread.
>>>
>>> If there are any objections, we don't have to start a VOTE, but it
>>> seems as if this will make everyone happy and it seems to be the
>>> fastest option available.
>>>
>>> On Thu, Jan 19, 2012 at 8:55 PM, Les Hazlewood <[email protected]> 
>>> wrote:
>>>> I'm looking at
>>>>
>>>> https://svn.apache.org/repos/asf/shiro/tags/shiro-root-1.2.0/pom.xml
>>>> right now.  Here is its <scm> section:
>>>>
>>>> <scm>
>>>>  <connection>scm:svn:http://svn.apache.org/repos/asf/shiro/tags/1.2.0</connection>
>>>>  <developerConnection>scm:svn:https://svn.apache.org/repos/asf/shiro/tags/1.2.0</developerConnection>
>>>>  <url>http://svn.apache.org/repos/asf/shiro/tags/1.2.0</url>
>>>> </scm>
>>>>
>>>> This does not match the current tag url.
>>>>
>>>>
>>>> On Thu, Jan 19, 2012 at 8:52 PM, Kalle Korhonen
>>>> <[email protected]> wrote:
>>>>> On Thu, Jan 19, 2012 at 7:57 PM, Jared Bunting
>>>>> <[email protected]> wrote:
>>>>>> The svn info in the pom file is incorrect now.  Should we update it to
>>>>>> reflect the new tag?
>>>>>
>>>>> Which svn info?
>>>>>
>>>>> From shiro-root-1.2.0.pom:
>>>>>    <scm>
>>>>>        
>>>>> <connection>scm:svn:http://svn.apache.org/repos/asf/shiro/tags/shiro-root-1.2.0</connection>
>>>>>        
>>>>> <developerConnection>scm:svn:https://svn.apache.org/repos/asf/shiro/tags/shiro-root-1.2.0</developerConnection>
>>>>>        
>>>>> <url>http://svn.apache.org/repos/asf/shiro/tags/shiro-root-1.2.0</url>
>>>>>    </scm>
>>>>>
>>>>> From the shiro-core manifest:
>>>>>
>>>>> SCM-Revision: ${buildNumber}
>>>>> SCM-url: http://svn.apache.org/repos/asf/shiro/tags/1.2.0/shiro-core
>>>>> Bundle-Version: 1.2.0
>>>>> Build-Jdk: 1.6.0_29
>>>>>
>>>>> Kalle
>>>>>
>>>>>
>>>>>> On Jan 19, 2012 9:24 PM, "Kalle Korhonen" <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>> On Thu, Jan 19, 2012 at 6:20 PM, Les Hazlewood <[email protected]> 
>>>>>> wrote:
>>>>>>> On Thu, Jan 19, 2012 at ...
>>>>>>
>>>>>>>> In general, if we cannot release any given module by running mvn -B
>>>>>>>> release:prepare release:pe...
>>>>>> I've renamed the existing 1.2.0 tag to
>>>>>> http://svn.apache.org/repos/asf/shiro/tags/shiro-root-1.2.0/. We can
>>>>>> by all means continue to use the same voting thread as long as it's
>>>>>> clear what we are voting on. There are no changes to the sources and
>>>>>> the binaries are the same.
>>>>>>
>>>>>> Kalle



-- 
Les Hazlewood
CTO, Katasoft | http://www.katasoft.com | 888.391.5282
twitter: @lhazlewood | http://twitter.com/lhazlewood
katasoft blog: http://www.katasoft.com/blogs/lhazlewood
personal blog: http://leshazlewood.com

Reply via email to