Release schedule

Pekka Paalanen ppaalanen at gmail.com
Mon Jun 4 11:29:33 UTC 2018


On Sun, 3 Jun 2018 10:52:49 +0100
Daniel Stone <daniel at fooishbar.org> wrote:

> Hi,
> 
> On 1 June 2018 at 17:52, Derek Foreman <derekf at osg.samsung.com> wrote:
> > Our last release for wayland and weston was April 9th, and there has
> > been some talk on IRC about release schedules, so maybe it's time to
> > start planning for the next one.
> >
> > Previously it looks like we've been on a 6 month cycle with releases in
> > February and August.  Following that duration we'd be looking at an
> > October release.  It feels like there's already a lot of significant
> > change, so I'm not sure waiting til October makes sense?
> >
> > Are we moving fast enough to do releases every 4 months instead of 6?  
> 
> Maybe? There's certainly a ton of change in the tree now, and a few
> more which look like they could land (IVI/XDG, the last bits of
> atomic, etc). It'd be a pretty hefty release whenever we released it.
> I don't have a strong opinion on when we get it out the door, to be
> honest.

Hi,

for a project I'm working on, it would be very nice to get the current
Weston master released ASAP. OTOH, I'm on vacation from July 12 to
Aug 1, so I definitely won't be around at that time.

We have been in the development cycle for two months now. How would you
feel about trying to get, say, rc1 out around July 10?

That would mean rc1 at five weeks from now. I could be around during the
alpha and beta time, hoping there wouldn't be much regressions to fix
after rc1.

Is it too soon? How soon could we do it?

Does it clash with the GitLab migration?

What do we want to have in the 5.0.0 release?

How long do we need for the alpha and beta stages?

> > I think we also no longer need to rigidly release wayland and weston at
> > the same time, as wayland itself is quite mature and may not receive
> > many significant patches during a weston cycle.  I'm wondering if
> > libwayland releases should break from timed cycles entirely?  
> 
> That sounds good to me. libwayland is so quiet that I don't think we
> need to force it out the door every so often; I think moving it out of
> forced major releases could get us actually doing patch releases as
> well, which would be nice.

Sounds fine to me!

Even for Weston, not the least because it would be oh so very convenient
for me right now, maybe it would be nice to let people request an early
release cycle if there are specific things they would like to have in a
release. In case nothing such comes up, our release manager could
decide to do a time-based release so that we get at least two
releases a year. How would that sound?

Obviously, when requesting an early release, the community needs to
agree on the schedule so that the feature freeze doesn't come at an
awkward time.


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20180604/1b1e33a2/attachment.sig>


More information about the wayland-devel mailing list