I like the idea of dry-running the release procedure with no fixes
included. Also, thanks Mark and Olivier for working around you schedules
to get this implemented sooner rather than later.
Do I understand correctly that you suggest to otherwise continue with
2.235 line as it was planned, 2.235.4 RC on 29th of July and 2.235.4
Release on 12th of August?
Are there any objections to Mark's proposal?
On 22/07/2020 22.16, Vlad Silverman wrote:
Thank you Mark for issuing this proposal and clarifying the steps.
+1 from me as well.
Please don’t hesitate to ask if any help is needed.
Thx, Vlad
On Jul 22, 2020, at 12:58 PM, Tim Jacomb <[email protected]
<mailto:[email protected]>> wrote:
+1 would be great to do one release while Olivier is around.
Would be good to have at least one user facing change in it, but I
guess not required.
Thanks
Tim
On Wed, 22 Jul 2020 at 20:29, Mark Waite <[email protected]
<mailto:[email protected]>> wrote:
The core release automation process has been used to deliver
weekly releases since mid-April. It was used to deliver the
weekly security release recently. We are ready to deliver the
Long Term Support (LTS) releases with core release automation.
Olivier Vernin has been the lead implementer of core release
automation work. He'll be unavailable in August. We'd like to
deliver an LTS next week, while he is still available. We'll use
that delivery to train others and verify the release process
documentation. We'll then run future core releases entirely from
the core release automation.
*Proposal:*
Create Jenkins 2.235.3 LTS release the week of July 27 using core
release automation. We'll use the current tip of the stable-2.235
branch. build the same code as was used for Jenkins 2.235.2 with
a single . The changes between 2.235.2 and 2.235.3 would be:
* Increment the version number from 2.235.2 to 2.235.3
* Use the new repository signing key for the Debian/Ubuntu, Red
Hat/CentOS, and OpenSUSE repositories
* Use acceptance test harness version as committed on the
stable-2.235 branch
We've been using the new repository signing keys with weekly
builds for the last several months. It is now time to switch to
the new repository signing keys for the long term support releases.
*Proposed steps:*
* Oliver Gondza approve the plan (as release officer)
* Mark Waite prepare a blog post announcing the change of
repository signing keys and the steps administrators must take
to install the new repository keys
* Mark Waite prepare the changelog and upgrade guide for Jenkins
2.235.3 with instructions for administrators to install the
new repository keys
* Olivier Vernin and Mark Waite generate the 2.235.3 LTS build
July 27, 28, or 29 using the core release automation based on
the current contents of the stable-2.235 branch
Comments, concerns, questions?
Thanks,
Mark Waite
--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/53818c9b-b9b6-462a-9dcf-9a320fed192en%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-dev/53818c9b-b9b6-462a-9dcf-9a320fed192en%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BictR95ZGdaFh%2BmXjXq_P9Ofx6e08A-icPmO4hXdz6pnkw%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BictR95ZGdaFh%2BmXjXq_P9Ofx6e08A-icPmO4hXdz6pnkw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/E83C9321-9761-431C-8847-4E4715A9F32D%40gmail.com
<https://groups.google.com/d/msgid/jenkinsci-dev/E83C9321-9761-431C-8847-4E4715A9F32D%40gmail.com?utm_medium=email&utm_source=footer>.
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/7a1143ad-c09d-4278-8802-8eb161b327d6%40gmail.com.
