Re: [wtp-pmc] WTP release cadence and test impact

[Nick Boldt <nboldt@xxxxxxxxxx>]

Another anomaly is that in the past we have generally taken an extra step to copy/rename the last stable M or RC build to the traditional R-prefixed name, but that step was missed this time around. Given the step is simply a rename, there's no lost functionality. 

I second Nitin's comments that if you want to help w/ release process, we'd be happy to have a hand. These days my focus is far away from WTP and desktop Eclipse, so I'd love to pass the torch to someone with a vested interest in seeing WTP continue.

Nick

WTP's reluctant releng guy

On Tue, Sep 21, 2021 at 9:45 PM Nitin Dahyabhai <thatnitind@xxxxxxxxx> wrote:

Hi Billy,

This release was an anomaly. In this case, M3 was the last set of changes in the release so a RC1 would have been a bit superfluous, and we almost never have the need for a RC2. The full list of known release tasks is written down at https://wiki.eclipse.org/WTP_Release_Tasks if you and your team would like to contribute in tackling them every quarter.

--

Regards,

Nitin Dahyabhai

Eclipse WTP PMC

_______________________________________________
wtp-pmc mailing list
wtp-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/wtp-pmc

--

Nick Boldt (he/him/his)

Principal Software Engineer, RHCSA

Productization Lead :: CodeReady Workspaces 

IM: @nickboldt / @nboldt / https://divbyzero.neocities.org

TRIED. TESTED. TRUSTED.

@ @redhatnews      Red Hat

“The Only Thing That Is Constant Is Change” - Heraclitus