If my counting is correct, it should have been released yesterday - what's the delay? Thanks in advance for the info.
See http://www.winehq.org/pipermail/wine-devel/2009-November/080038.html
On Sat, Nov 28, 2009 at 2:38 PM, Thunderbird <wineforum-user at winehq.org> wrote:> See http://www.winehq.org/pipermail/wine-devel/2009- > November/080038.htmlThanks for the info - however, it would be really nice if in the future, somebody could announce something like this on main page of www.winehq.com (I guess that not so many users read wine-devel mailing list...). Again thanks for the info. Best regards.
James Huk wrote:> what's the delay?What, you didn't know that whole US has a 1/2 week off? And since CV is US company AJ has the same 1/2 week off too.
2 to 3 week cycle for development branch has done wine well. 2 weeks when aj in in office for the 2 weeks. 3 weeks when he had a holiday. A long time ago it was longer Jim Hall. Everyone sees the regression rate if wine its not that nice at times. When it was long it was more regressions at once. Kinda fixed time frame is to keep regressions under control. Yes on average 3 week releases are slightly worse for regressions due to more patches stacking up. I have done support around wine for a long time. I would really hate to see 3 month+ releases again on the development branch they were painful. Stable release wine don't have many of are very much audited and a slow long and time taking project
I think there is a mixture of good points in this thread. Coming back to the OP's point, you can see that potentially many casual users may only visit WineHQ and of recent times would have got used to seeing a new release every two weeks. While those closer and more involved to wine (via the forums or IRC) know better. In the absence of a regular WWN (didn't one of the W's stand for weekly?) a casual Wine observer or user does not know better. A more regular (even if brief) WWN on WineHQ may avoid such confusion and give the casual visitor a better impression of the activity and vibrancy of the wonderful welcoming wine community. For instance in previous years wineconf has been more prominent on WineHQ. Maybe while a only release when something worthy and ready to release is a better development philosophy maybe a regular release pattern is easier for others, say testers. If wine remains vibrant (any reason why it should not) and since the release has been largely biweekly for a good while maybe it would be good to keep that as a target, which can always deferred or skipped when reasons apply, but a visible note on the front door that lets not so involved participants know? If it's an agreed target maybe have a next release "1.x.yz" due "dd mmm yy" which can always be updated? NB I'm only talking about the development branch. Maybe a WWN could be auto generated in some way that incorporates stats on number of postings and patches in last week, a reminder to visit the forum (with link) if you want to know more about the polite and proactive interaction going on in the wine community.