On 30 Apr 2015, at 22:30, Denis Golovin wrote:
Done for freemarker.
thanks!
script still finds these missing though.
jbosstools-freemarker missing 11 tags:
jbosstools-4.1.0.Beta1,
jbosstools-4.1.1.Beta1,
jbosstools-4.1.1.CR1,
jbosstools-4.1.1.Final,
jbosstools-4.1.2.Final,
jbosstools-4.2.0.Alpha1,
jbosstools-4.2.0.Beta1,
jbosstools-4.2.0.Beta2,
jbosstools-4.2.3.Beta1,
jbosstools-4.2.3.CR1,
jbosstools-4.3.0.Alpha1
so I assume you just did it for alpha2, right ?
Should we run tagging verification script after release is declared and it
would keep pinging component leads until tag is created?
yeah - but I think I got a script now that can do this via github api meaning I need no
git clones etc. just the list of repos and sha1's that our builds should have.
see other mail.
/max/max
On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen <manderse@redhat.com>
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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
http://about.me/maxandersen