World Wine News

This week, 180 posts consumed 162 K. There were 42 different contributors. 21 (50%) posted more than once. 21 (50%) posted last week too.

The top 5 posters of the week were:

1. 6 posts in 7K by piotr.caban at gmail.com (Piotr Caban)
2. 5 posts in 11K by ken at codeweavers.com (Ken Thomases)
3. 5 posts in 14K by sebastian at fds-team.de (Sebastian Lackner)
4. 4 posts in 6K by bunglehead at gmail.com (Nikolay Sivov)
5. 4 posts in 5K by dmitry at baikal.ru (Dmitry Timoshkov)

As you might already have heard we want to integrate wine-staging into the Wine development process. Here is the official mail which also includes other changes.

Alexandre Julliard wrote in:

Over the last few months there have been a lot of discussions about how
to improve our development process. I've been gathering feedback, and
last week at WineConf I summarized the suggestions in my keynote
presentation; the slides can be viewed at
https://wiki.winehq.org/WineConf2015?action=AttachFile&do=get&target=wineconf-2015.pdf

We've then had a lot of constructive discussions about the various
points. The major decisions we've agreed on are:

- Wine-staging is now considered an integral part of the Wine
  development process, and will be used as a mechanism to enable more
  patches to meet the requirements for inclusion in the main tree. We
  will all be working together as a team.

- Bugs reported against wine-staging will be accepted in the WineHQ bug
  tracker; there will be a way to distinguish bugs specific to Staging,
  and bugs that are fixed in Staging but not yet in main Wine. The
  Staging bug tracker will be retired. Austin English is in charge of
  implementing the necessary changes in Bugzilla.

- We will switch to a time-based stable release, on a yearly
  schedule. The code freeze will start every year in the fall. Michael
  Stefaniuc will be maintaining the stable branch starting with 1.8.

- We will start enforcing a Signed-Off-By header on patches, to make it
  possible to better distribute reviewing responsibility, and to allow
  multiple authors to cooperate on a patch.

- We will keep a list of maintainer contact information for the various
  submodules; developers will be encouraged to go through the respective
  maintainer before submitting to wine-patches.

- There will be a group of people who volunteer to be assigned patches
  to review, to make sure that no patch goes unreviewed. Going through
  Staging first will also be encouraged for unfinished or risky patches.

- The patch tracker will send automated emails when a patch status
  changes; this will also serve to encourage discussion rather than
  despair when a patch is not approved.

- We will start building and distributing binary packages for all
  distros that don't have readily available packages. The packaging
  scripts and control files will be maintained in git, so that people
  can review them and submit improvements.

These changes will be implemented over the next few weeks.

I'm hoping that this will make the development process more pleasant for
everybody, and enable us to better respond to users' needs.

Once these changes are in place, I'll also encourage everybody who had
given up in disgust to give us another chance; and if things are still
not satisfactory, please send us feedback. This is a work in progress,
and we will continue to listen and work on making things better.

One of the steps to achive the integration is to adjust our Bugzilla settings.

Austin English wrote in:

Howdy all,

As Alexandre mentioned [1], at WineConf we made several decisions to
modify bugzilla in a few ways. I've now implemented those changes,
which are outlined below:

* New wine-staging product: This should be used for bugs caused by
patches that are in wine-staging, but that do not occur in
wine-development (i.e., wine-staging patch regressions)

* New STAGED resolution: This is to differentiate bugs that are FIXED
(in wine-development) from bugs that are not present in wine-staging
because of one or more patches. The anticipated workflow is:
UNCONFIRMED > bug confirmed, NEW > patch written and sent to
wine-patches, if it's accepted, FIXED. If not, and the patch is
integrated into wine-staging, then the bug is STAGED. When the patch
is revised and eventually integrated into wine-development, the bug
should move to FIXED.

* New NEEDINFO resolution: There's a lot of confusion and different
handling by triagers for what to do with bug reports that are
incomplete (i.e., leaving it open versus closing invalid). To mitigate
this, I've added a NEEDINFO resolution. If a bug report lacks needed
information, set it to this status. Bug that have been open NEEDINFO
for more than 1 year can be closed.

* Renamed UPSTREAM to NOTOURBUG: This is more in line with what other
projects do, and eliminates confusion about the upstream/downstream
distinction.

For now some things are still not implemented, for example a patch flow for staging-only patches, patch tracker adjustments/improvements, providing binary packages and maybe a Git mirror of the staging tree at WineHQ

In the meantime you might want to view the Videos of some presentations:

• Keynote presentation – Alexandre Julliard
• Brief update on CodeWeavers - Jeremy White
• Wine Staging Introduction - Michael Stefaniuc

To be continued...

Tom Wickline wrote an article about figuring out the monetary value of Wine:

The glass of wine thats worth 350 million dollars

*Disclaimer: These lists of changes are automatically generated by information entered into the AppDB. These results are subject to the opinions of the users submitting application reviews. The Wine community does not guarantee that even though an application may be upgraded to 'Gold' or 'Platinum' in this list, that you will have the same experience and would provide a similar rating.