Topics

Release sequence to JMRI 4.18

Bob Jacobsen
 

The current release plan has build dates of:

4.17.6 - Sunday Nov 17th (this weekend) from HEAD of master; PG&E might delay it by a day or two

4.17.7 - Sunday Nov 25th from HEAD of master

4.17.8 - Monday Dec 2nd with only limited changes - regression fixes, help pages and decoder updates

(4.17.9 as/if needed fo regressions _only_; everything else waits for 4.19.1 et al.)

4.18 - Roughly Dec 18th

4.19.1 - The day after 4.18 from HEAD of master

if you have new development that you want in 4.18, _please_ plan on having it in a PR and passing CI testing in the next 10 days. (It would be particularly good for people to go through their WIP PRs and either release them for merging or close them; your branch will still be available for local work!) If that’s not possible, please reply to this note so we can have a discussion about how to handle it. Special handling is certainly possible, but it works better if it’s arranged in advance.

Are these dates OK for people? Testing will be particularly important.

All of the (limited) changes for inclusion in 4.17.8, .9 et al will have to be on branches rooted in 4.17.7 or before. Lesson learned, _no_ exceptions. If you need help setting that up, please just ask.

Bob
--
Bob Jacobsen
rgj1927@... +1-510-708-5988 AIM, Skype JacobsenRG






--
Bob Jacobsen
@BobJacobsen

danielb987
 

Fine for me.

PR #6463, WIP Make AbstractNamedBean.toString() final, should NOT go into 4.18 since it removes depricated methods.
https://github.com/JMRI/JMRI/pull/6463

Daniel

2019-11-15 16:39 skrev Bob Jacobsen:

The current release plan has build dates of:
4.17.6 - Sunday Nov 17th (this weekend) from HEAD of master; PG&E
might delay it by a day or two
4.17.7 - Sunday Nov 25th from HEAD of master
4.17.8 - Monday Dec 2nd with only limited changes - regression fixes,
help pages and decoder updates
(4.17.9 as/if needed fo regressions _only_; everything else waits for
4.19.1 et al.)
4.18 - Roughly Dec 18th
4.19.1 - The day after 4.18 from HEAD of master
if you have new development that you want in 4.18, _please_ plan on
having it in a PR and passing CI testing in the next 10 days. (It
would be particularly good for people to go through their WIP PRs and
either release them for merging or close them; your branch will still
be available for local work!) If that’s not possible, please reply to
this note so we can have a discussion about how to handle it. Special
handling is certainly possible, but it works better if it’s arranged
in advance.
Are these dates OK for people? Testing will be particularly important.
All of the (limited) changes for inclusion in 4.17.8, .9 et al will
have to be on branches rooted in 4.17.7 or before. Lesson learned,
_no_ exceptions. If you need help setting that up, please just ask.
Bob
--
Bob Jacobsen
rgj1927@... +1-510-708-5988 AIM, Skype JacobsenRG