Maniphest T197669

Formalise and Announce REL1_29 EOL
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Reedy
	Jun 19 2018, 10:47 AM

Description

So, according to mw.org, REL1_29 is due to become EOL this month. No specific date, or trigger, just June 2018. So we don't know if it's the start, the end, or when we released 1.31

As such, we should formalise a date to do this, send emails to wikitech-l, mediawiki-l and possibly mediawiki-announce for blanket coverage, and then make sure the mediawiki.org is updated as such.

Then we can start cleaning up CI jobs and other stuff we don't need to run anymore, and it also means I stop bothering Antoine and Zeljko with filing tasks like T197608: Selenium tests broken on REL1_29 :)

There is also the question whether we should (answer is probably) do a 1.29.3 release for maintenance reasons - https://github.com/wikimedia/mediawiki/compare/1.29.2...REL1_29 (37 commits), and possibly any pending security patches

Related Objects

Mentioned In: T197601: Failed to invoke Pygments: /usr/bin/env: python: No such file or directory
T182851: SyntaxHighlight should run Pygments with Python 3
T199023: Write and send pre-release Announcements for MediaWiki 1.27.5/1.29.3/1.30.1/1.31.1
T181665: Tracking bug for 1.27.5/1.29.3/1.30.1/1.31.1 security release
T197608: Selenium tests broken on REL1_29
Mentioned Here: T197608: Selenium tests broken on REL1_29

Event Timeline

Reedy created this task.Jun 19 2018, 10:47 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 19 2018, 10:47 AM

There is also the question whether we should (answer is probably) do a 1.29.3 release for maintenance reasons - https://github.com/wikimedia/mediawiki/compare/1.29.2...REL1_29 (37 commits), and possibly any pending security patches

I guess so since effort was put into them being back-ported. Moreover I think a last maintenance release together with a farewell announcement sounds like a good idea.

• Vvjjkkii renamed this task from Formalise and Announce REL1_29 EOL to ioaaaaaaaa.Jul 1 2018, 1:02 AM

• Vvjjkkii triaged this task as High priority.

• Vvjjkkii added projects: CheckUser, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), Tamil-Sites, Gamepress, Hashtags, Jade, KartoEditor, Language-2018-Apr-June, New-Editor-Experiences, Mail, TCB-Team (now WMDE-TechWish).

• Vvjjkkii updated the task description. (Show Details)

• Vvjjkkii removed a subscriber: Aklapper.

CommunityTechBot renamed this task from ioaaaaaaaa to Formalise and Announce REL1_29 EOL.Jul 2 2018, 1:32 PM

CommunityTechBot raised the priority of this task from High to Needs Triage.

CommunityTechBot updated the task description. (Show Details)

CommunityTechBot removed projects: TCB-Team (now WMDE-TechWish), Mail, New-Editor-Experiences, Language-2018-Apr-June, KartoEditor, Jade, Hashtags, Gamepress, Tamil-Sites, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), CheckUser.

CommunityTechBot added a subscriber: Aklapper.

Jdforrester-WMF subscribed.Jul 6 2018, 11:33 PM

Reedy mentioned this in T197608: Selenium tests broken on REL1_29.Jul 7 2018, 10:39 AM

Reedy mentioned this in T181665: Tracking bug for 1.27.5/1.29.3/1.30.1/1.31.1 security release.Jul 7 2018, 10:41 AM

Reedy mentioned this in T199023: Write and send pre-release Announcements for MediaWiki 1.27.5/1.29.3/1.30.1/1.31.1.Jul 7 2018, 4:55 PM

gerritbot mentioned this in T197601: Failed to invoke Pygments: /usr/bin/env: python: No such file or directory.Jul 11 2018, 2:46 AM

gerritbot mentioned this in T182851: SyntaxHighlight should run Pygments with Python 3.

Krinkle awarded a token.Jul 11 2018, 2:46 AM

+1 to what @Kghbln said. One last maintenance release and then declare it EOL?

In T197669#4417090, @Legoktm wrote:

+1 to what @Kghbln said. One last maintenance release and then declare it EOL?

That's vaguely what I've been working towards. Backporting security/hardening patches in gerrit to REL1_29 when doing the rest of them. Amount of extra work is minimal

I am under the impression that the release management team or what it was called is no longer active. Who is doing releases nowadays if at all? Does somebody happen to know?

@Kghbln: Release-Engineering-Team, as tagged in this very task.

Perhaps changing the priority makes this get attention. Apparently I have no idea about the inner workings of the group.

Restricted Application added subscribers: Liuxinyu970226, TerraCodes. · View Herald TranscriptAug 4 2018, 11:43 AM

@Kghbln: This is not UBN per definition.
Do not set the Priority field only in order to get attention. Thanks.

I am under the impression that the release management team or what it was called is no longer active. Who is doing releases nowadays if at all? Does somebody happen to know? The Release-Engineering-Team was pinged but did not respond yet. Is there somebody else involved?

In T197669#4496239, @Kghbln wrote:

Who is doing releases nowadays if at all?

https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team

Is there somebody else involved?

No.

Thanks for the info. Since the team does not convene to comment here even though they were pinged by you I will use the general mailing list to ask about the status of this task. Perhaps somebody is on the list who is in contact with them.

This is something Release-Engineering-Team generally does, but this is another in the long list of tasks @demon used to quietly take care of. We'll get to this but will need some help from folks familiar with this process (@Reedy :))

thcipriani moved this task from INBOX to Next on the Release-Engineering-Team board.Aug 13 2018, 4:48 PM

thcipriani edited projects, added Release-Engineering-Team (Next); removed Release-Engineering-Team.

In T197669#4499105, @thcipriani wrote:

This is something Release-Engineering-Team generally does, but this is another in the long list of tasks @demon used to quietly take care of. We'll get to this but will need some help from folks familiar with this process (@Reedy :))

Yeah... It's been on my TODO list, but I was hoping to do it at the same time as a security release... That hasn't happened yet, so this hasn't either. And unfortunately other tasks have taken a higher priority.

@Jdforrester-WMF pinged me about this on IRC... My response was that I'm limited with keyboard use atm, so struggling to do too much that involves a keyboard. Going to be the case for the rest of this week till stitches come out, then see how my mobility is then.

Question is whether to wait for the security release. Or just do this as a point release, and have the fixes released for REL1_29 out of sync with those on other branches... Or just do a maintenance release for them all in one go? Or just release the security fixes that are ready, and bump others still to be written/reviewed/reworked to the next release?

For your attention:

I think everyone is in agreement that there will be one more 1.29 release, which will contain some security fixes and a pile of bug fixes (42!). Given there's only a few days left in August, I'm not confident that the release will be done by then (still need to request CVEs, and write some more documentation/release notes), so any objections to saying EOL is September 2018? I'll update the wiki at the end of the week if no one objects.

Resolved: there will be one more 1.29 security+maintenance release that will happen in/by September 2018.

I updated the wiki, please update any other pages if I missed them :)

Liuxinyu970226 unsubscribed.Sep 4 2018, 2:14 PM

Formalise and Announce REL1_29 EOLClosed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Formalise and Announce REL1_29 EOL
Closed, ResolvedPublic
Actions