On 07/25/2011 11:54 AM, lo...@museresearch.com wrote:
- Does the development branch of WINE go through a battery of tests before
it is posted? What kind of criteria has to be met before a development
release is made available on the main page?
Each applied patch have to compile and pass all conf
On Monday 25 July 2011 19:54:00 lo...@museresearch.com wrote:
> - Does the development branch of WINE go through a battery of tests before
> it is posted? What kind of criteria has to be met before a development
> release is made available on the main page?
Every git revision has to pass the wine
On Mon, Jul 25, 2011 at 6:54 PM, wrote:
> - It's my understanding that the stable branch only has select features
> and patches ported over (from the wiki: "..with only minimal changes
> merged in"). Would this mean that if I compared a stable release with a
> development release from around the
Hi,
I am a developer for a product which makes heavy use of WINE. Right
now, we're deciding which newer version of WINE to go to, and I thought
the wine-devel community might have some insight. I did read the
WineReleaseCriteria entry on the wiki, but still have some questions.
If anyone could
