jbosstools-4.2.3.Final tag created for jbosstools-build (even though we
still have
https://issues.jboss.org/browse/JBIDE-19744 open pending a fix).
For these 2 projects below, branches don't exist for 4.3.0.Alpha2x so I
could not create tags. Will create branches for Beta1x and tag next time.
* jbosstools-build-ci
*
jbosstools-download.jboss.org
Do you need me to compute which old SHAs map to old tags like
4.0.0.Final or 4.1.0.Beta1? Since those releases are done and we will
only ever be building forward from 4.2.x (after 4.2.3.Final) and 4.3.x
(after 4.3.0.Alpha2), do we need to go back into the past to create old
tags?
Nick
On 04/30/2015 07:21 AM, Max Rydahl Andersen wrote:
Done for livereload and webservices - xcoulon is on PTO so I did it for him.
posted here since getting these tags recorded are important.
Things the tags are used for:
* build of jbosstools at fedora
* checking what went into a release when debugging
* knowing which components got into a relase
Still missing:
jbosstools-portlet
jbosstools-freemarker
jbosstools-hibernate
jbosstools-aerogear
jbosstools-arquillian
jbosstools-download.jboss.org
jbosstools-build-ci
jbosstools-birt
/max
> Done for forge
>
> On 04/27/2015 07:22 PM, 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
>>
>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com