[Scummvm-devel] ScummVM 1.1.0 has been tagged

[Arnaud Boutonné]

Hi everybody,

I pick (2) as postponing the release of 2 weeks (or 2 months) wouldn't
change the situation: a lots of high priority bugs are opened for ages, and
some recent are not even regressions (see the broken videos in Gob3 CD: they
were also present in v1.0. The bug was priority 2, but the final video was
completely destroyed...)

On the other hand, if a commercial release of a game uses ScummVM, it's
right that having bugs is really a problem. In the case of the recent Gob
release, we fixed almost the same day 2 problems present only in the CD
version which were unnoticed before.
Wouldn't it be interesting to think of a way to auto-detect that a new
stable version has been released? (I checked, it's not in the feature
request)

Best regards,
Arnaud / Strangerke

On Thu, Apr 1, 2010 at 1:16 PM, Kari Salminen <kari.salminen at gmail.com>wrote:

>  Hi,
>
> On Thu, Apr 1, 2010 at 11:49 AM, Max Horn <max at quendi.de> wrote:
> > I'd like to conduct a vote. Only ScummVM devs are allowed to vote
> >
> > Pick one:
> >  (1) We delay the release until "all open regressions" are resolved.
> >  (2) We proceed as planned and make a 1.1.0 release
>
>   I pick (2) as IMO waiting isn't changing anything.
>
> Kari Salminen / Buddha^
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Scummvm-devel mailing list
> Scummvm-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scummvm-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20100401/58ce8044/attachment.html>