Re: [jbosstools-dev] ACTION REQUIRED: Tagging of jbosstools-4.1.1.Beta1

No need to retag xulrunner since we haven't rebuilt it since 4.1.0. No new code since last release == no need to tag. All other components have changed since 4.1.0 so they'll be tagging for Beta1, branching for CR1 and tagging for .Final (once we get there). On 11/11/2013 02:16 PM, Yahor wrote: > Do we need to create tags in not changed components (i.e. xulrunner)? > > On the one hand it will be easier to build a particular version of the > JBoss Tools in the future. > On the other hand we did not even create the "jbosstools-4.1.1.Beta1x" > branch and did not rebuild xulrunner since jbosstools-4.1.0.Final. > > > On Mon, Nov 11, 2013 at 12:18 PM, Max Rydahl Andersen > <manderse(a)redhat.com <mailto:manderse@redhat.com>> wrote: > > Nick added this add the end of the announce mail, marking it as > ACTION required to let you all know. > > > >Project leads, please tag your projects! > > > > co jbosstools-4.1.1.Beta1x > > git tag jbosstools-4.1.1.Beta1 > > git push origin jbosstools-4.1.1.Beta1 > > Note: Really would be nice if jenkins could just make such tags in > its own repository and > we could move the exact commit over from the "build" repository to > the master repository. > > /max > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > >