[dmm]

> Release every 2 weeks like clockwork.

Which means exciting new regressions every two weeks! When I used wine it was definitely the case that certain applications(games) worked better with specific wine versions so a continuous release cycle could result in breaking a working application. That's something users of stable are trying to avoid.

If a user wants the latest version of a package you can always install it manually.

[coldpie]

I don't disagree with anything you said, but I would like to add that if you become aware of a program that used to work, but no longer does, PLEASE file a bug! We take regressions very seriously[1]. There are often reasons they can't be fixed immediately, but more often we can fix it quickly. But we have to know about it first!

[1] We even have an explicit regression tracker that places blame and shame on whoever broke it! http://source.winehq.org/regressions

[voltagex_]

I'd love to report more stuff in Wine but isn't there a requirement to be running the latest/dev branch? This is tricky to do in Debian (because I prefer to build debs of whatever and then install those).

[coldpie]

You will be asked to test it in the latest release, yes, but perhaps someone else can test it for you, or at least get developer eyes on the issue. In any case, it's unlikely to be just closed invalid without any consideration. We would rather know about it than not.

[zanny]

Parent is actually wrong - Wine releases with the Gnome cycle, where even releases are stable and odd ones are unstable. Debian should technically be shipping both versions according to upstream release cadences - people who want stable use 1.8 right now, and people who want latest features use 1.9.

[scrollaway]

In what way am I wrong? Wine releases are in fact every two weeks with a stable release once in a while. How is it relevant that stable are even and unstable are odd?

[zanny]

Because Wine (and Gnome) maintain them in parallel. With Chrome you have the one release version that gets constantly updated every two weeks, but unlike Firefox's ESR / Linux's LTS kernels Google doesn't want to maintain an "LTS" version of Chrome.

Yes, its semantics whether you just pin arbitrary releases and call them LTS vs having dedicated versioning schema to support it, but you called it a Chrome like cycle, when its just a more general constant iteration with occasional LTS cycle. Not many products actually use the full blown constant iteration for everyone model Google uses on Chrome.