[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sc-devel] UI.shutdown [from sc-users] SC3.2 rc4 now available

I think we're probably all on the same page here, just feeling the competing tensions of fixing bugs before 3.2 and getting 3.2 finished.

The point of an RC is to shake out bugs. This sounds like a significant bug to me, so I think it should be committed.

The strict RC process has been quite enlightening! Normally we won't have such a strict deadline, but I think it's been very useful and that we should continue to follow it in the future.


On 7 Feb 2008, at 15:33, Sciss wrote:

i don't need to persuade anyone. the last RC broke the shutdown of
swingOSC because of after three years of unchanged code in my
shutdown JSCWindow was placed after NetAddr to shutdown. if i'm too
late to fix that, than that's it, find someone else to develop
swingOSC, i don't get paid for doing swingOSC and i can do a lot
better with my time, then people help yourselves and create your own

sorry but that makes me really upset.

Am 07.02.2008 um 12:52 schrieb Dan Stowell:

Moving this to the dev list. You've missed the deadline. If you can
persuade the devs in general that it merits a new RC or a patch before
release, then that's up to you, but we're now in a phase where the
program should be frozen and only changes to helpfiles are made.
Otherwise, the user testing of rc4 will be worth a lot less than it
should be.


2008/2/7, Sciss <contact@xxxxxxxx>:
obviously i will want to solve the UI.shutdown problem

Am 07.02.2008 um 09:31 schrieb Dan Stowell:
If no important problems are revealed then this will be the official
3.2 release, the release on which the forthcoming book will be

sc-users mailing list

Sc-devel mailing list

Sc-devel mailing list