~mil/sxmo-tickets#605: 
Tracking next release for postmarketos v24.12

I'm adding this meta-ticket to track things that need to happen (mainly in packaging) for the next release. I would be nice if we can manage a new release in time for postmarketos v24.12:

  • Switch to wofi instead of bemenu by default?
  • release latest wvkbd
  • include latest dwm-6.5 changes into sxmo-dwm?

New dependencies for sxmo-utils:

  • wofi
  • iio-sensor-proxy

New configuration:

Status
RESOLVED IMPLEMENTED
Submitter
~proycon
Assigned to
No-one
Submitted
a month ago
Updated
16 days ago
Labels
No labels applied.

~proycon a month ago

Would also be nice if we can ensure full calling support on the pixel 3a (google-sargo) for this upcoming release, fdelamotte already figured out almost all the details.

Peter Thomason a month ago ยท edit

What would the benefits be to changing to wofi?

For 6.5 dwm we need to resolve this ticket: https://lists.sr.ht/~mil/sxmo-devel/%3CZkU7RtrKSv4xb95o@pppp.gateway%3Ed

~proycon a month ago

On Sat Oct 26, 2024 at 9:59 AM CEST, ~Peter Thomason wrote:

What would the benefits be to changing to wofi?

  • It has a smooth scrolling experience that is a lot more intuitive and convenient than bemenu's pagination.
  • It supports multiline items

For 6.5 dwm we need to resolve this ticket: https://lists.sr.ht/~mil/sxmo-devel/%3CZkU7RtrKSv4xb95o@pppp.gateway%3Ed

Right

~aren a month ago

I'd prefer to have the polkit rule in sxmo-utils, that's much easier to keep track of than making sure every distro gets the right one.

I don't know what alpine packaging is like, but if we were to make a pre-release (e.g. v1.17-rc1) could that be packaged in alpine edge to get some wider testing?

~proycon a month ago

On Sat Oct 26, 2024 at 4:30 PM CEST, ~aren wrote:

I'd prefer to have the polkit rule in sxmo-utils, that's much easier to keep track of than making sure every distro gets the right one.

Right, agreed, I just submitted a patch for that.

I don't know what alpine packaging is like, but if we were to make a pre-release (e.g. v1.17-rc1) could that be packaged in alpine edge to get some wider testing?

Yes, that sounds quite feasible and a good idea. (I don't think the rc suffix is common in Alpine but we can just do a less advertised v1.17 and a final v1.18)

--

Maarten van Gompel (proycon)

web: https://proycon.anaproy.nl gpg: 0x39FE11201A31555C

~aren a month ago

Yes, that sounds quite feasible and a good idea. (I don't think the rc suffix is common in Alpine but we can just do a less advertised v1.17 and a final v1.18)

We basically do this already, there always seem to be a few bugs that turn up after making a release, which tend to get fixed in 1.X.1 or 1.X.2. So perhaps the thing to do is to make a 1.17 release sooner rather than later, and plan on a couple of point releases to clean up the loose ends?

~stacyharper a month ago

I'm also a bit against making wofi the default, without strong argument. Just they are different, with different pros and cons.

~proycon a month ago

On Sun Oct 27, 2024 at 7:33 AM CET, ~stacyharper wrote:

I'm also a bit against making wofi the default, without strong argument. Just they are different, with different pros and cons.

Yes, but for the out-of-the-box experience I think wofi now provides the most intuitive/comfortable experience. I guess we should just let more people try and weigh in on what they prefer as default.

~proycon a month ago

One more for the release todo-list:

  • ensure latest svkbd is released (at suckless) and packaged (in aports)

~proycon a month ago

One more for the list:

  • ensure lswt is added as a dependency for sxmo-utils

~proycon a month ago

On Sat Oct 26, 2024 at 7:48 PM CEST, ~aren wrote:

Yes, that sounds quite feasible and a good idea. (I don't think the rc suffix is common in Alpine but we can just do a less advertised v1.17 and a final v1.18)

We basically do this already, there always seem to be a few bugs that turn up after making a release, which tend to get fixed in 1.X.1 or 1.X.2. So perhaps the thing to do is to make a 1.17 release sooner rather than later, and plan on a couple of point releases to clean up the loose ends?

Agreed, would be good to really something soonish once all the important parts we want in are in place (e.g. peanutbutter).

~proycon 18 days ago

Another dependency to add:

  • ensure colordiff is installed because doing migrations with plain diff without colours is not pleasant

~proycon 17 days ago

  • sxmo-utils 1.17.0 has been git tagged
  • svkbd release has been requested to suckless, will have to package it when done
  • lswt dependency not yet needed because we reverted that patch
  • colordiff dependency not required because we don't want the heavy perl/delta dependency and implemented a fallback solution that adds colour with plain sed.
  • wvkbd has been released this week
  • peanutbutter has been released earlier already
  • dwm-6.5 still open

~proycon REPORTED IMPLEMENTED 16 days ago

Register here or Log in to comment, or comment via email.