Il giorno gio 16 lug 2020 alle ore 10:11 Shawn Rutledge < shawn.rutle...@qt.io> ha scritto:
> > > On 2020 Jul 6, at 18:57, Pier Luigi Fiorini <pierluigi.fior...@gmail.com> > wrote: > > > > Hi, > > > > I noticed that some modules are going into the marketplace, for example > Qt Multimedia. > > Would you consider doing so for QtWayland Compositor? > > > > The compositor API would surely benefit from a faster release cycle. > > > > Getting new protocols and updates sooner instead of every 6 months would > be great. > > > > Thoughts? > > I’m dubious about whether the release cycle would really be faster that > way. Continuing to include it in the release every 6 months probably adds > more motivation to keep fixing things regularly, rather than slowing it > down. > > Otherwise, do you have examples of ongoing changes that really shouldn’t > wait until the next release? > > It’s currently possible to build from git. (And I hope it remains that > way.) “Releases” are artificial flag days, from one side; in practice, > Linux distros tend to wait for them, but it doesn’t have to be that way. > > Maybe you want to add an extra level of release numbering, and put those > intermediate releases into Marketplace, just to have the psychological > effect of the existence of more “releases”, and update distro packages more > often from there? I.e. after 5.15.1 comes 5.15.1.1, 5.15.1.2, etc. But > then I’d predict that it will not be so many after all, as long as > generating releases takes human time. > The main problem is that sometimes you wait even 12 months (or more) before a release hit the end users. 6 months of release cycle + the time needed by distros to pick up a new Qt version. Since updating Qt is not an easy task and affects so many users, some distros do not update right away and you can't expect to use a new protocol implementation 12/14 months after you made that change. -- https://liri.io An OS and apps built with modern design and features
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
