Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.11.0 release checklist #1199

Closed
16 of 21 tasks
alerque opened this issue Sep 1, 2021 · 4 comments
Closed
16 of 21 tasks

v0.11.0 release checklist #1199

alerque opened this issue Sep 1, 2021 · 4 comments
Assignees
Labels
todo tooling Build tooling, release management, and packaging processes
Milestone

Comments

@alerque
Copy link
Member

alerque commented Sep 1, 2021

See full release checklist for howto, this is just a checklist version:

  • Pass all tests
  • Spring clean
  • Re-fetch tooling
  • Configure
  • Cut release
  • Push tag to master
  • Update website
    • Copy changelog and prefix with a summary as a blog post
    • Copy and post manual, update 'latest' symlink and menu links
    • Tweak summary and edit into GitHub release notes
  • Update distro packages
  • Bump downstream projects
    • FontProof (Docker image base plus CI matrix)
  • Shuffle milestones
  • Eat cake
@alerque alerque added todo tooling Build tooling, release management, and packaging processes labels Sep 1, 2021
@alerque alerque added this to the v0.11.0 milestone Sep 1, 2021
@alerque
Copy link
Member Author

alerque commented Sep 1, 2021

And ... it seems with this release Docker Hub has gone the way of Travis CI and left open source in the lurch. Automated builds now require a subscription.

We already build Docker images that end up in GitHub Package Repository anyway for use in running GitHub actions. We can also build them using Cirrus. I'll look into how to just push prebuilt images from elsewhere to Docker Hub for the convenience of anybody downloading it from there.

@alerque alerque self-assigned this Sep 1, 2021
@ctrlcctrlv
Copy link
Member

@alerque Can you apply the patch in #1197? (That is, update NanoSVG dependency?)

@alerque
Copy link
Member Author

alerque commented Sep 2, 2021

@ctrlcctrlv Sure, but it missed this release cycle. I kind of drove this one through for the bugfixes it already had sitting around and I wanted to pin a production project on a stable SILE version before it went to press. There is no reason we can't get out patch releases more frequently though if anything becomes a hold for folks. The release process is relatively streamlined at this point and I don't mind putting things through if they help anybody downstream.

@alerque alerque mentioned this issue Sep 3, 2021
21 tasks
@alerque
Copy link
Member Author

alerque commented Sep 3, 2021

Abort, abort, abort!

Closing in favor of #1204. Downstream packaging turned up a couple issues that we can fix easier with a patch release than make distro packagers work around downstream.

@alerque alerque closed this as completed Sep 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
todo tooling Build tooling, release management, and packaging processes
Projects
None yet
Development

No branches or pull requests

2 participants