Next release (v0.17.0)

[caseyavila]

TODO

pre-release

• packdeps (bytestring 0.11, …)
• version numbers in xmonad-contrib.cabal
• version number and date in CHANGES.md
• regenerate xmonad-docs
• Next release (v0.17.0) xmonad#264 pre-release
  • Create issue for logo contest

release

• create release in GitHub UI, wait for CI
• check candidate on Hackage and its docs
• manually run the Haskell-CI workflow again to finalise the Hackage release
• continue with Next release (v0.17.0) xmonad#264

post-release

• reenable CI against released X11 and xmonad

Original issue body

Problem Description

Is there any information on when a new version is planned for xmonad-contrib? There have been some additions between v0.16 and the current branch and as an end user it would be nice to have them included in package managers.

My apologies if there is a release schedule I should have known about or if the answer to my question is obvious, but I wasn't able to find any information about it.

[pasja]

Hello,

Indeed, I just migrated to xmonad-git & xmonad-contrib-git to get the ewmh fullscreen support from #109
While xmonad is an exceptionally stable software (even in its git version) but on the long run I would prefer to go back to the distribution(in my case it is Debian) packages.

Regards,
János Pásztor

[byorgey]

There are still a few people (like me) who comment on & merge new PRs, but the problem is there is no longer anyone who is responsible for doing new releases. @aavogt and @pjones both did it for a while, but have moved on. If anyone is interested in helping out by packaging up a new release, by all means please do! I'm happy to help with permissions and such, and there's probably a checklist around somewhere...

[caseyavila]

I would be interested, though I'm beginner at best with regards to Haskell. Let me know if there is still stuff I can do or if "learning on the job" is fine.

[psibi]

@byorgey Does creating a release involve anything more than uploading it to Hackage ? I would be happy to offer any help in making a new release.

[pjones]

@psibi The MAINTAINERS.md file has a checklist for the release process. It's mostly housekeeping around the changelog and announcements.

[psibi]

@pjones Thanks! @caseyavila Do you want to collaborate for the new release ? I'm available in Matrix under the name psibi and also can answer any questions you have.

[elkowar]

a prior announcement would be nice btw, for contributors to have time to add finishing touches, or finish some modules they've been working on if necessary ;D

[caseyavila]

@psibi I would love to collaborate, though I will be somewhat busy until the end of this weekend.

[psibi]

Update: @caseyavila and I spoke about this and he is working on creating a new release by following the steps mentioned in the release procedure.

@elkowar Where do you think a prior announcement would be nice ? I think the plan is to put a new release in a week or so. So, I have no objections if you want to do the announcement somewhere. :-)

[liskin]

Hey everyone, #192 has just been merged and it introduces a breaking change that I believe is avoidable (#192 (comment)). It was already reverted once in 2017 (#161) for a similar reason, so it'd be good to not do the release before this is resolved (or decided not to resolve). Thanks!

[psibi]

Thanks @liskin for the update. Do we have a issue for that blocker ? If not, can you create a one so that we can easily track it ?

[liskin]

@psibi #396

[liskin]

I also added the v0.17 milestone to track stuff that we wish to happen before the release.
@elkowar please use this milestone for any issues that need finishing touches. :-)

[liskin]

I just noticed there's a bunch of open issues in the https://github.com/xmonad/xmonad-contrib/milestone/2 milestone. Do you folks want to do something with those?

[psibi]

@liskin Do you think any of them should be a blocker for v0.17 ? Some of the MR's there (eg #121) seems harmless and probably can be merged. But given that I don't use those functionalities, probably you or some one else would a better judge of it. Anyway, I feel if the issues/PR's there aren't blocker - we should go ahead with the release once #396 is fixed.

[liskin]

#121 indeed looks good, so I reviewed it and will be happy to merge once we deal with the nitpicks.
#180 was fixed already, so I closed it.
The rest… I'm not affected by either of them nor do I know enough about those parts of the code to be able to quickly step in. None seem urgent. So I guess just clearing the milestone is the best course of action.

[elkowar]

#402 should definitely be merged before the release, as it fixes incomplete documentation - which would otherwise be a missing piece of information for a long while.

[slotThe]

One thing that I've noticed: how about we remove all of the `defaultFooConfig` occurrences that are still in xmonad-contrib? The deprecation warnings to use `Data.Default` instead were added in 0f1b6fb, which was more than seven years ago now. EDIT: This became #404 (heh)

[TheMC47]

Even though xmonad/xmonad#248 is from the core package, I think it's important to take care of

[liskin]

Relevant here: xmonad/xmonad#308 (release automation via GitHub Actions).

[adityagupta1089]

I would really like to help with the 0.17 release and the issues in the milestone, so that it is available for package managers ASAP and we don't have to compile it everytime. I think it's been quite some time 0.16.

[TheMC47]

@adityagupta1089 thanks for wanting to help! We have a project board (https://github.com/orgs/xmonad/projects/2). I think it's best to focus on documentation tasks such as #592 or maybe searching for DynamicLog and updating the documentation so it works with X.H.StatusBar.

[liskin]

As the release inches closer, I repurposed this issue for tracking what needs to be done before, during and after the release. And I did the same with xmonad/xmonad#264

[liskin]

https://xmonad.org/news/2021/10/27/xmonad-0-17-0.html