Folks,
Because of various travels and vacations (and just to keep you on your
toes ;-), during the month of July I'm planning to make releases on
Tuesdays instead of Fridays.
So 1.5.8 will be on July 3rd, and then I'll be out for the rest of that
week. Subsequent releases should happen on July 17
Folks,
The weekly rc schedule won't be quite weekly this week, I'll be out for
the next few days so there won't be a release this Friday. The weekly
schedule will resume with rc3 next Friday. Don't let that stop you,
there are still enough regressions for everybody...
--
Alexandre Julliard
julli
Ivan Leo Puoti <[EMAIL PROTECTED]> writes:
> How will the feature freeze/unfreeze work?
It's really a progressive process that has been going on for some time
now. As code matures I'm getting increasingly reluctant to accept
large changes to it, that's why I insist on small patches and test
cases
Alexandre Julliard wrote:
Apart from the version numbering, it won't change much. There will
still be regular CVS snapshots (I'm hoping to do them more frequently
than in the past, but don't hold me to that ;-), and binary packages
built from these snapshots. I have no plans to create stable/unst
Holly Bostick <[EMAIL PROTECTED]> writes:
> But the docs, of course, have to be valid for the future as well as (to
> a limited extent) the past. So how will one "Get Wine" after the
> release? Will there continue to be monthly public betas? Or will the
> release sche
Looking at the current user docs raised a question as to how to update
the 'Getting Wine' section.
I know from the past that many users don't know that Wine has been up to
this point on a monthly release schedule. Between this ignorance, and binary
distributions' stable and
