Core changelog maintenance

[Daniel Beck]

Hi everyone,

I will stop maintaining the core changelog (weekly and LTS) and upgrade guide at the end of October, except insofar as it concerns entries related to security fixes. This means that 2.202 is the last changelog I will write.

Regards,
Daniel

[Mark Waite]

Thanks for your maintaining of the changelog and the upgrade guides in the past.

I'd like to offer my time and effort to maintain the changelog and the upgrade guide.  Others may also want to offer their help so that we get deeper coverage of the changelog and the upgrade guide.

Would you be willing to let me record a session with you during the time that you prepare the upcoming changelogs and the upgrade guides?  I'll use the recording to guide my creation of the changelog and the upgrade guide on later releases.  We can invite other interested parties to attend the tutorial session if they would like and can archive an edited version of the session on YouTube in case we need it later.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C2942F39-0190-4B26-809A-6065B850332F%40beckweb.net.

--

Thanks!

Mark Waite

[Oleg Nenashev]

Hi all,

First of all, thanks a lot to Daniel for handling the changelog process for years! It is a hard job, and it is much appreciated

Just to add some context to this thread, I have already started working on the automatic YAML changelog gerenerator.

You can find the current drafts here: https://github.com/jenkinsci/jenkins/releases.

There are some bits to finish,but I am confident we can automate the majority of the process.

Upgrade guidelines are a bigger concern, but I believe we can request submitters to write them on their own as a part of the review process.

It will also help to make these guidelines available in Weekly releases which is an issue now

BR, Oleg

On Thursday, October 24, 2019 at 10:06:55 PM UTC+3, Mark Waite wrote:

Thanks for your maintaining of the changelog and the upgrade guides in the past.

I'd like to offer my time and effort to maintain the changelog and the upgrade guide.  Others may also want to offer their help so that we get deeper coverage of the changelog and the upgrade guide.

Would you be willing to let me record a session with you during the time that you prepare the upcoming changelogs and the upgrade guides?  I'll use the recording to guide my creation of the changelog and the upgrade guide on later releases.  We can invite other interested parties to attend the tutorial session if they would like and can archive an edited version of the session on YouTube in case we need it later.

On Thu, Oct 24, 2019 at 12:01 PM Daniel Beck <m...@beckweb.net> wrote:

Hi everyone,

I will stop maintaining the core changelog (weekly and LTS) and upgrade guide at the end of October, except insofar as it concerns entries related to security fixes. This means that 2.202 is the last changelog I will write.

Regards,
Daniel

--
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 jenkin...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C2942F39-0190-4B26-809A-6065B850332F%40beckweb.net.

--

Thanks!

Mark Waite

[Jesse Glick]

On Fri, Oct 25, 2019 at 9:23 AM Oleg Nenashev <o.v.ne...@gmail.com> wrote:
> You can find the current drafts here: https://github.com/jenkinsci/jenkins/releases.

Would it be feasible to use the native Release Drafter format, which
is human-readable as is in the GH Releases page, and modify jenkins.io
to consume that instead of YAML?

(Or simply have the jenkins.io *Changelog* link direct you to GH
Releases to begin with?)

[Oleg Nenashev]

Something to consider for the future. Personally I like Machine-readable changelogs, and Markdown changelogs barely qualify as ones.

Changelog format change is barely a top priority unless the current approach stops working. 

Too many fires in other areas

On Friday, October 25, 2019 at 5:06:04 PM UTC+3, Jesse Glick wrote:

[Mark Waite]

Daniel provided me some more detailed training on changelog and upgrade guide maintenance.  I'm planning to create the next weekly changelog and the LTS changelog when that time arrives.

Thanks,

Mark Waite

On Thursday, October 24, 2019 at 1:06:55 PM UTC-6, Mark Waite wrote:

Thanks for your maintaining of the changelog and the upgrade guides in the past.

I'd like to offer my time and effort to maintain the changelog and the upgrade guide.  Others may also want to offer their help so that we get deeper coverage of the changelog and the upgrade guide.

Would you be willing to let me record a session with you during the time that you prepare the upcoming changelogs and the upgrade guides?  I'll use the recording to guide my creation of the changelog and the upgrade guide on later releases.  We can invite other interested parties to attend the tutorial session if they would like and can archive an edited version of the session on YouTube in case we need it later.

On Thu, Oct 24, 2019 at 12:01 PM Daniel Beck wrote:

Hi everyone,

I will stop maintaining the core changelog (weekly and LTS) and upgrade guide at the end of October, except insofar as it concerns entries related to security fixes. This means that 2.202 is the last changelog I will write.

Regards,
Daniel

-- 

--

Thanks!

Mark Waite

[Oleg Nenashev]

I am happy to leave changelogs to someone else. My core changelog PRs usually get too many requests of changes, which does not make it a pleasant experience.

I will be doing changelog automation and tooling, but I will leave final changelogs to contributors who have time to carefully review all changes

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/kVjOddydLEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5a6f4f4a-9d90-46ae-a0d2-a7086cf6706a%40googlegroups.com.

[Oleg Nenashev]

So yes, thanks a lot to Mark for stepping up

[Oleg Nenashev]

Hi all,

Just to follow-up on this thread and to prevent collisions, I suggest the following:

• There is an automatically generated changelog with minimum copy-editing on GitHub Releases: https://github.com/jenkinsci/jenkins/releases . This changelog is maintained by Jenkins core maintainers and released shortly after the release is cut.
• Right now it is generated by Release Drafter, and there are some gaps. Later we can extend the Release Drafter or Daniel's changelog generator to automatically generate fancier changelogs which are closer to what we usually have in jenkins.io/changelog
• Once the automated Core releases flow is finished, we can add automatic changelog release as a Pipeline step so that there is no need in manual maintenance
• There is a Core PTR process which ensures quality of changelogs and upgrade guidelines before merging. Will make sure to document it
• There is an official changelog and upgrade guidelines in https://jenkins.io/changelog/ and https://jenkins.io/changelog-stable/ . It is maintained by the Jenkins Release Team, Mark Waite takes the leadership in the changelog management
• The ETA of the official changelogs is Monday, and it may take 24hrs since the Jenkins weekly release (hapens on Sunday ATM)
• IMHO we should change the release date to Monday or Tuesday once the releases are fully automated. It will allow managing releases without spending time on Sundays which is not a good community-life balance
• We setup regular Jenkins Core office hours to sync-up on the core pull requests, changelogs and LTS statuses. These meetings will largely replace the LTS releases status check we had during the governance meetings
• I suggest Mondays

What do you think?

Best regards,

Oleg

To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.

[Daniel Beck]

On Mon, Nov 11, 2019 at 11:35 AM Oleg Nenashev <o.v.ne...@gmail.com> wrote:

• The ETA of the official changelogs is Monday, and it may take 24hrs since the Jenkins weekly release (hapens on Sunday ATM)
• IMHO we should change the release date to Monday or Tuesday once the releases are fully automated. It will allow managing releases without spending time on Sundays which is not a good community-life balance

Or just finish merging Friday around noon UTC. Then the definitive changelog can be prepared Friday afternoon (or all of Friday for those in the US), including merging to master, since the site doesn't show changelogs for unreleased versions.

Not merging core changes on Saturdays would also improve "community-life balance" :-)