On Mon, 8 Apr 2019 at 05:54, Daniel Stone <[email protected]> wrote: > > Hi, > > On Mon, 8 Apr 2019 at 11:02, Pekka Paalanen <[email protected]> wrote: > > On Fri, 05 Apr 2019 18:01:45 +0000 Simon Ser <[email protected]> wrote: > > > Regarding the need for a new release manager for Wayland, I'd like to > > > step in and volunteer for this role. I'm willing to take the time > > > necessary to (1) learn the current release process and (2) apply it if > > > the community is interested. > > > > I would be happy to have you. Let's see till Friday if anyone else has > > anything to say. > > Yeah, I'd certainly be very happy with this as well.
As would I. Thanks, Derek > > We are currently in a transition phase with Weston's Meson build, > > autotools being just removed, so there are some tasks I think would be > > good to do: > > > > - Copy releasing.txt from Weston to Wayland, since it documents the > > autotools release process and Wayland still uses that. > > > > - Streamline Wayland's releasing.txt, there are bits that only ever > > applied to Weston. > > > > - Figure out the new releasing process with Meson and document in > > Weston's releasing.txt. We've never done a release from Meson before. > > It would also be awesome to revive the work on GitLab CI: moving > Wayland to the same CI templates that Weston/libinput/etc use, > enabling 32-bit builds as well as ASan/MSan/UBSan builds ... > > > We should also decide when the next releases will be, and check which > > things to prioritise for the next Wayland and Weston releases (this is > > where we/I have traditionally sucked). ISTR Derek already announced > > that Wayland and Weston do not necessarily release in sync anymore, > > Wayland having settled down while Weston having lots of on-going work. > > There is a lot of CI-related work on my and others' plates that is > > probably a first priority for both projects. > > > > The (acting) release manager has practically had a minor exempt from > > the "everything must be reviewed" rule in that he can push release > > related version bumps directly and update the web site with releases. > > Indeed. I think documenting the release process and schedule is > probably a good place to start though. :) Similarly we need to figure > out the same for Weston, but as noted, there's no reason to keep on > tying those two together anymore. > > Cheers, > Daniel _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
