[jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag jbosstools-4.3.0.Alpha2 ]

[Max Rydahl Andersen]

I'll write the script. Having the tags has been and will be useful in past despite you thinking it is just icing. 

/max
http://about.me/maxandersen


> On 28 Apr 2015, at 22:55, Nick Boldt <nboldt at redhat.com> wrote:
> 
> No, but I have a script that checks if everyone has branched & if root poms are updated, because...
> 
> * Wrong root pom: prevents builds & blocks releases.
> 
> * Branching: prevents builds & blocks releases.
> 
> * Tagging: until we move to a model where tags drive builds, tagging after the release is just icing sugar.
> 
> You may now commence arguing. :D
> 
> Nick
> 
>> On 04/28/2015 02:01 PM, Max Rydahl Andersen wrote:
>>> On 28 Apr 2015, at 15:41, Nick Boldt wrote:
>>> 
>>> Just FYI, you don't need to reply to these emails to confirm the work's
>>> done.
>> 
>> Nick, do you have a script that checks if all done ?
>> 
>> /max
>> 
>>> Thanks,
>>> 
>>> Nick
>>> 
>>>> On 04/28/2015 05:53 AM, André Dietisheim wrote:
>>>> done for OpenShift
>>>> 
>>>>> On 04/28/2015 12:22 AM, Nick Boldt wrote:
>>>>> Component leads, please tag your repositories!
>>>>> 
>>>>>  git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>>>> called jbosstools, also often called origin
>>>>>  git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>>>  git push jbosstools jbosstools-4.3.0.Alpha2
>>> 
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> /max
>> http://about.me/maxandersen
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com