Am 2018-05-15 um 21:44 schrieb Stephen Connolly:
On Tue 15 May 2018 at 19:32, Michael Osipov <[email protected]> wrote:
Am 2018-05-15 um 13:35 schrieb Stephen Connolly:
As Hervé has merged the JAnsi fix, we are now unblocked for cutting 3.5.4
I will give 72h for anyone to surface any issues they wish to claim
should
be included in 3.5.4 and have not already been merged.
As the person stepping up to be release manager* for 3.5.4, I get to
decide
if:
* your claim is valid and I will wait for your changes; or whether
* I will go ahead without your changes.
After all blocking changes are merged I will start shake-down to ensure
the
build is releasable. This may result in reverts of changes that are not
fully baked or it may mean that we surface a new blocking issue that we
need to wait for.
I have current a busload of change for SCM and Wagon in the pipeline I
really like to be in 3.5.4, some in SCM and Wagon are blocking.
It will like take another week from my side to get all done. If you
could wait that would be awesome.
I don't want you do to another RM for 3.5.5 just because of Wagon and SCM.
I don’t mind spinning a 3.5.5 after 3.5.4... though TBH depending on the
scope of the wagon and scm changes, it might be better to call it 3.6.0
A couple of quick releases in a row will help me automate the release
process better... so at this point, more smaller releases is better than
fewer bigger releases.
That would be fine with me.
We’d said we’d do the ansi fixes as soon as they were ready, so i’d rather
not hold back.
Can you provide details of the changes you want so I can make an assessment?
Yes, for Wagon it is:
WAGON-452, WAGON-496, WAGON-518, WAGON-513 + WAGON-514 fix MNG-6388.
For SCM it is:
SCM-797, SCM-763, SCM-818, SCM-866, SCM-875 and SCM-888.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
