v21.12 service pack 3
The usual service pack discussion issue, suggestions welcome.
-
mmsd-tng 1.9drop tmp/mmsd-tng from release branch- I made an executive decision to just upgrade mmsd-tng in alpine aports 3.15, since that version is a lot more usable than the version in aports. -clayton
- see: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/31398
-
squeekboard 1.16
-
phosh: automounting disks (!2905 (closed))
- portfolio 0.9.13
-
dino 0.3
-
upgrade N900 kernel to latest (18046f68)
-
postmarketos-ui-phosh: enable waked by default (!2963 (closed))
-
linux-postmarketos-qcom-msm8996 upgrade to 5.16.12 (!2979)
-
linux-postmarketos-qcom-sdm845 upgrade to 5.16.12
-
build pinephone keyboard as module (https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/2966)
ETA: calendar week 10
Activity
added release-v21.12 service-pack-discussion labels
mentioned in issue #1408 (closed)
By clayton craft on 2022-02-11T19:22:26
I would suggest squeekboard 1.16 as according to the changelog for Phosh 0.15, it's mandatory for Phosh 0.15 or later: https://gitlab.gnome.org/World/Phosh/phosh/-/tags/v0.15.0#required-versions-of-related-projects
But Phosh 0.15 seems to work just fine with squeekboard 1.14, so I don't think it's urgent.
By Newbyte on 2022-03-14T07:38:28
Edited by Ghost User-
unfortunately it fails to build, details in pmbootstrap#2110. Since it was a nice-to-have upgrade, I'll revert it to unblock publishing all other packages that were built for the service pack and mention this in the blog post.
By Oliver Smith on 2022-03-14T07:38:27
-
TODO list for the release (from the wiki), we'll add this to the new service pack issues in the future. The rest of the issue can of course still be used to make suggestions for the service pack and to discuss them.
- create a branch for it (like v21.03.1)
-
create a discussion issue, where we can write down if something is missing or if something in that branch is debatable
- add the ETA calendar week (e.g. CW 10, usually 2nd CW of the month, when in doubt ask ollie)
-
add the following labels:
- release-vYY.MM
- service-pack-discussion
- paste the current version of this todo list from the wiki into this new issue, as separate comment
- add it to the releases wiki page (under Service Packs / planned)
- after merging patches into pmaports master or aports master, that we want to have in the service pack: either just immediately cherry-pick it to the branch (no merge request and not much code review, we'll review before releasing it), or add it as TODO checkbox to the service pack discussion issue
- update the version number in the rootfs-etc-os-release file in the postmarketos-base package to add/update the service pack number after the regular branch version
-
shortly (~1 week) before releasing the service pack, create the merge request
-
add the following labels:
- release-vYY.MM
- backport
- enable the checkbox to delete the branch after merge after merging the service pack:
-
homepage:
-
publish a blog post with a short overview of changes
- add one good photo at the top (when in doubt ask Martijn)
- for updated components, add new version numbers and links to upstream release notes
- as usually, create a merge request, make sure the team sees and reviews it
- (do not change latest_release/latest_release_title in config/download.py!)
-
publish a blog post with a short overview of changes
-
add the following labels:
- close the related issue
- create a new issue for the next service pack
- leave a comment in the current service pack discussion issue that points to the next one
- update releases wiki page
By Oliver Smith on 2022-03-13T16:54:34
Edited by Administrator mentioned in issue #1390 (closed)
By Oliver Smith on 2022-02-21T20:52:41
-
Can we add dino 0.3 to the service pack? It has significant improvements.
By Anjandev Momi on 2022-02-28T08:06:04
Edited by Ghost User -
technically the dino in pmaports is not 0.3, but based on their libhandy branch that is periodically rebased. IIRC it was last rebased in december, so it's very close to "dino 0.3". picking that upgrade to stable is a good idea!
just wanted to mention that in case you actually meant dino 0.3 and not the dino that we package in pmaports.
By clayton craft on 2022-02-28T08:06:04
assigned to @craftyguy
By clayton craft on 2022-02-28T08:04:33
marked the checklist item phosh: automounting disks (!2905 (closed)) as completed
By clayton craft on 2022-02-28T08:14:50
created branch
1423-v21-12-service-pack-3to address this issueBy clayton craft on 2022-02-28T08:19:44
mentioned in merge request !2967 (closed)
By clayton craft on 2022-02-28T08:21:55
-
For linux-nokia-n900, I would suggest adding 18046f68
By Sicelo on 2022-02-28T09:57:08
Edited by Ghost User marked the checklist item upgrade N900 kernel to latest (18046f68) as completed
By clayton craft on 2022-02-28T09:59:46
-
Would it be possible to include !2979?
By Yassine Oudjana on 2022-03-05T07:05:16
Edited by Ghost User
-
Just mentioning here that I'm testing the keyboard kernel module change on stable. It does indeed build, install, run, and function just fine on the stable 5.15.13 kernel.
By Adam Thiede on 2022-03-05T22:05:47
Edited by Ghost User -
Ok, I tested the current kernel from edge on my stable install. I also rebuilt the stable kernel with the modification. On both, I can remove/re-add the kb151 module without issue. It doesn't load it in decryption screen, but that requires an update device package, and I tried to install edge's on stable, but it had dependency issues. I'm confident this change will work.
By Adam Thiede on 2022-03-05T22:49:34
marked the checklist item build pinephone keyboard as module (https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/2966) as completed
By clayton craft on 2022-03-05T22:05:11
-
Service pack is out! Next discussion issue: #1459 (closed)
https://postmarketos.org/blog/2022/03/13/v21.12.3-release/
By Oliver Smith on 2022-03-13T16:55:05
Edited by Administrator