[jbosstools-dev] Master branch open for business - but be sure to tag first!

[Nick Boldt]

Yes, BUILD_ALIAS = Final [0].

[0] https://github.com/jbosstools/jbosstools-build/commit/1a815e99b5577dab476c91cfad4442e4a1a6b5eb

And yes, parent pom version = 4.4.1.Final-SNAPSHOT  [1].

[1] https://github.com/jbosstools/jbosstools-build/commit/dc98fd6827de3d6e5b7c3d69515105dc3be06e97

For the other projects, we'll be doing it in an automated way instead
of making everyone do it by hand: this script [2] will suggest the
changes to root poms and perform the creation of the new 4.4.1.x
branches automatically.

[2] https://issues.jboss.org/browse/JBIDE-22728

I just need someone (eg., Martin, Mickael, Alexey, Jeff, Denis...?) to
review the PR & the generated output. Then I can merge it, wrap it in
a Jenkins job that will also create an email sent to Alexey/Jeff and
they can take the contents of that email, run it, and voila! ready for
Final / 4.4.1.x branch. Could also cc: all team leads if that's
valuable.

As of this week, there's no urgent need to create the branches until
we're ready for code freeze (in 10 days), UNLESS people want to start
working on 4.4.1 and 4.4.2 in parallel. If the code is the same for
both branches, creating the branch NOW would only create extra
developer overhead, as all fixes would need to be pushed to two
branches.

So... once the PR is approved, I'll create the email w/ the script,
and when Alexey/Jeff decide they want to declare the branches created
for 4.4.1.Final (and thus have master be open for 4.4.2 work), they
can run it. I would expect that to happen on Sept 1, but YMMV and you
could update your root pom then branch sooner, if you'd like.



On Thu, Aug 18, 2016 at 10:55 AM, Martin Malina <mmalina at redhat.com> wrote:
> Shouldn't the BUILD_ALIAS be set to Final now? [1]
> No pressure, just curious where this fits in the workflow.
> Do we also want to update the version from 4.4.1.Alpha1-SNAPSHOT to Final at
> some point or is it not necessary at all?
>
> -Martin
>
> [1] http://www.rockpoint.cz/stan-msr-elixir-3/pMSR21010037-2/
>
>
>
> On 18. 8. 2016, at 15:29, Nick Boldt <nboldt at redhat.com> wrote:
>
> Component leads = people in charge of the jbosstools-* github repos,
> or jbosstools components in JIRA.
>
> I only mentioned the need to create the tags in this email in case you
> hadn't had a chance to create the tags BEFORE someone saw my email and
> started pushing changes to master.
>
> If you have created all the tags, then there's nothing left to do
> except fix all the bugs in master branch. :D
>
>
>
> On Thu, Aug 18, 2016 at 4:59 AM, Jean-Francois Maury <jmaury at redhat.com>
> wrote:
>
> I'm not getting it. I created the tag on all repos through the Python script
> Nick sent me so what is to do at the component level.
>
> Jeff
>
> On Thu, Aug 18, 2016 at 10:15 AM, Xavier Coulon <xcoulon at redhat.com> wrote:
>
>
> hello,
>
> it's done on Web Services and LiveReload (thanks to Dmitry) components.
>
> Best regards,
> /Xavier.
>
> On 17 Aug 2016, at 23:46, Nick Boldt <nboldt at redhat.com> wrote:
>
> With the release of AM3, master branch is again open for business.
>
> Component leads, please be sure to tag your project from the master
> branch (tag: jbosstools-4.4.1.AM3) before committing any new changes
> toward the 4.4.1.Final release.
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at 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
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at 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