[jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.3.CR1 ]

[Alexey Kazakov]

The commit with upgraded Forge 2.15.2 was not included in CR1 - 
https://github.com/jbosstools/jbosstools-forge/commit/431cc4839d8d38563e91f97432b460ee2ef0b54a
So, we should tag 4.2.x as CR1 w/o that commit.

On 03/19/2015 12:10 PM, George Gastaldi wrote:
> Done for forge.
>
> On 03/19/2015 03:11 PM, Nick Boldt wrote:
>> Component leads, please tag your repositories!
>>
>> (Note: if you changed nothing in this milestone, you don't have to tag.
>> Looking at you, Portlet & Freemarker.)
>>
>> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
>> jbosstools, also often called origin
>> $ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
>> $ git push jbosstools jbosstools-4.2.3.CR1
>>
>> Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY*
>> please bump your root pom to use the latest parent pom,
>> 4.2.3.Final-SNAPSHOT.
>>
>> I will send out the usual Task JIRA nags, too.
>>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev