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

Done for freemarker.

Should we run tagging verification script after release is declared and it would keep pinging component leads until tag is created?

On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen <manderse(a)redhat.com&gt; 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 >