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

["Dan Stowell" <danstowell@xxxxxxxxx>]

Sciss, sorry to upset you. We all know that an extraordinary amount of
very good work has gone into swingOSC. None of us are getting paid of
course.

I'm trying hard at the moment to help co-ordinate the efforts of a
strongly unstructured dev community to produce a finished product,
which is taking a long time because it seems there's always at least
one more thing. In this case, the constant stream of one-more-things
has had a casualty: breaking SwingOSC interfacing, only a few days
before the supposed release date. This is why over the past weeks I've
been trying (and failing) to insist that we leave lots of space for
testing release-candidates while not fiddling with the code. Instead
we have multiple RCs in a short space of time, which is bound to
induce fatigue among users (let alone devs) and cause bugs to surface
at the last minute.

If the issue is important (I assume that it is, I'm not familiar with
the specifics) then ideally we'd put together a new RC perhaps some
time next week, put it out to test for a couple of weeks then settle
on it. The connection with the book-producing-process makes such a
long lag unacceptable, so it's up to those in the know (you, Ron,
others) to decide if it can be patched safely without breaking other
things.

So I'm sorry that my previous message was so curt; I'm kind of
exasperated at the gradual breakdown of the process that was meant to
ensure a lovely and stable 3.2, but that's not your fault.

Dan


2008/2/7, Sciss <contact@xxxxxxxx>:
> 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
> support.
>
> 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.
> >
> > Dan
> >
> >
> > 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
> >>> based.
> >>>
> >> _______________________________________________
> >> sc-users mailing list
> >> sc-users@xxxxxxxxxxxxxxx
> >> http://lists.create.ucsb.edu/mailman/listinfo/sc-users
> >>
> >
> >
> > --
> > http://www.mcld.co.uk
> > _______________________________________________
> > Sc-devel mailing list
> > Sc-devel@xxxxxxxxxxxxxxx
> > http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
>
> _______________________________________________
> Sc-devel mailing list
> Sc-devel@xxxxxxxxxxxxxxx
> http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
>


-- 
http://www.mcld.co.uk