You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Simon Quigley
bb440b7d9b
|
5 years ago | |
---|---|---|
LICENSE | 6 years ago | |
README.md | 5 years ago | |
repo-list | 5 years ago | |
setup-phab | 5 years ago |
README.md
Two weeks before release day:
- Announce internally that any last minute changes should be done as soon as possible.
- File the megatask for the upcoming release's blockers.
- Go through the release blocker list for this cycle and punt non-RC tasks to next cycle.
- Inform the Calamares upstream contact that we plan on doing a release in two weeks. Discuss whether any important patches should be cherry-picked, and get those uploaded as soon as possible. Ask them nicely to ping you in the next two weeks if anything important comes up.
- Talk to the Lubuntu Documentation Team about what needs to be wrapped up for next release. Nicely remind them that the release is in two weeks.
A week before release day:
- Update the downloads page and the homepage for the new release in a draft, so they can be published on release day.
- Do one final check of the testing checklist and send out a call for testers.
- Start drafting a blog post for the release.
- Gather known bugs (possibly automate this) to put on the blog post from:
- bugs associated with the Lubuntu Packages Team;
- packages in the Lubuntu packageset which the Lubuntu Packages Team might not have been subscribed to, especially Lubuntu specific ones like
lubuntu-meta
andlubuntu-artwork
; - known issues from previous release notes; and
- open defects report on the ISO QA tracker for both the upcoming release as well as previous releases to ensure nothing has been missed.
After ISOs have been released:
- Publish the blog post and the downloads/homepage drafts.
- Post on social media:
- Twitter or Mastodon (publishing to one published to the other).
- r/Lubuntu and r/Ubuntu.
- Facebook page and Facebook group.
- IRC topics for #lubuntu, #lubuntu-devel, and #lubuntu-offtopic on freenode.
- Announce on the lubuntu-users and lubuntu-devel mailing lists.
- Scan social media and see if anyone is pointing out any reproducible bugs that we can file.
After the codename is announced and base-files
is uploaded:
- File a task about a new wallpaper and slideshow for the upcoming release.
- Change
update.cfg
in lubuntu-meta and the branding as well as the desktop file incalamares-settings-ubuntu
. - Make sure
repo-list
is up-to-date and runsetup-phab
in this repo. The production values can be found in the internal setup document. - Someone with access to GitHub should update the default branches for the mirrored repositories.
- Update the CI to enable builds for the new release:
- In ci.conf:
- Add the new codename to the
releases
list, and remove old releases if necessary. - Change
default_branch
to the branch you just created above. - Evaluate overrides for the aforementioned variables and season to taste.
- Add the new codename to the
- Run jobgenerator and then look over the builds triggered. Did you miss a step?
- Add the new release to the Britney job so builds can migrate.
- In ci.conf:
- If
lintian
anddevscripts
have not been updated, cherry-pick thelintian
patch adding the new release as known if there is one, and no-change rebuilddevscripts
.- Lintian needs a patch because all of the Ubuntu releases are hardcoded in
vendors/ubuntu/main/data/changes-file/known-dists
. devscripts
needs a no-change rebuild because it gets the value grabbed bydch -r
on build time. This is in line 47 ofscripts/Makefile
.
- Lintian needs a patch because all of the Ubuntu releases are hardcoded in
- Evaluate our packages. What needs to be updated to the latest upstream release? What did we carry over to this release?