WineReleaseCriteria

Wine Release Plan

Wine 1.2 will come out some time in the future. Alexandre has said he would like to start the stabilization process after at least one of the following major features is done:

Of these, the one with the most progress recently is 64-bit support.

Branching

Wine now uses a stable/unstable branch model. Even-numbered releases (eg 1.0.x) will be stable, with only minimal changes merged in. Development will continue on the 1.1.x branch until we stabilize it for the 1.2.0 release, after which 1.3 will become the new development branch. When asked whether the 1.1.x branch can be considered "alpha" or "beta", Alexandre responded that it is the "development branch" -- for end user purposes, this means alpha (and thus prone to regressions) until we freeze for 1.2.

Wine 1.2 Release Criteria

Although we can aspire to finish one of Alexandre's five major goals above, we also need some well defined criteria for making a stable 1.2 release.

This is still a work in progress, so please help contribute

Nominating bugs: It is important that we keep the Wine 1.2 bug targets reasonable. The primary goal of a stable release is to have:

  • No regressions since 1.0.1
  • No regressions since relatively recent Wine betas
  • No small but embarrassing bugs still open

  • At least one major new app we can support and brag about (although many apps are already working better)

You can add your own bugs to the nomination list by giving them the 1.2 release target, however please be conservative. In particular, we don't want bugs that are a major amount of work, as otherwise the release will not come out in a reasonable amount of time.

Application focus:

  • We should repeat the 1.0 Platinum Regression Hunt

  • We should still support all Wine 1.0.1 targeted applications (see below)
  • Consider supporting newer versions of these same apps
  • Discussion is needed about what the new "big app" to add should be

Documentation and UI:

  • Much of Wine's user interface is done at the packaging level, and we should standardize some best practices for packagers so Wine is consistent across distributions
  • The user and winelib documentation should be given a once over before finalizing the release as well

Old Wine 1.0 Release Criteria

Wine 1.0.0 is scheduled to be released sometime around Wine's 15th birthday (see WineReleasePlan). That means that the number of things we can fix before release is limited.

A small set of popular, useful, and freely downloadable applications already run well, and must continue to run well as we prepare for the 1.0.0 release:

Applications that ran well as of about wine-0.9.50 or later should continue to run well. If you find any new bugs in these applications, please file issues for them in Bugzilla, and target them for 1.0.0. See also PlatinumRegressionHunt.

Here's the current list:

As of May 5th, there are 43 bugs on this list.

Bugs targeted for 1.0.0 are very likely be deferred to 1.2.0 if it's clear they cannot be fixed quickly, e.g. if they were created 90 days ago and have not had any progress in 30 days. e.g. Here's a canned search for bugs with target_milestone=1.0.0, with creation date less than e.g. 20080205 and modified date less than e.g. 20080405. (Bugs with really good analysis and/or patches might be kept open even if there hasn't been any motion in 30 days.)

The wine-1.0 release will happen once "few enough" new regression reports are trickling in, and we have fixed "enough" of the known 1.0 bugs. (This is a judgement call to be made by the maintainer with some help from the release manager.)

Press Mentions

OK, this one made me smile:

WineReleaseCriteria (last edited 2009-09-22 07:59:14 by PieterDeBruijn)