PDA

View Full Version : quick summary of 6.0 changes?



Phillip Kerman
2005-01-04, 00:51
First... I was reacting to this:

>Now that this is in place,
> > expect a lot
> > of fast improvement!

...not so much just a chance to vent.



> If you want stability, use 5.4.1. write bug reports on that
> based on STABILITY
> ONLY. That is the focus of 5.4.1 and that stream. 6.0 is
> for speed of data
> handling. dropouts might be reduced, but they are really rather a
> streaming/network problem that may see some improvement as
> data handling speeds
> up.

Okay... but is 5.4.1 released yet? I'm not really into doing the nightly
builds any more.


I do think my questions are pointed at making the general suggestion that my
pet issues (and others) are given some priority. All I have is empirical
data that the 5.4 release changed performance slightly. It could easily be
something else... but I look at the sincerely valuable feature of RSS and
just have to wonder if that comes at the expense of issues that I would
consider more primary.

I really don't intend to sound like I'm harping on stuff... certainly don't
want to reduce anyone's enthusiasm. But... like I say, I was just asking
because of Dean's words above.

Thanks,
Phillip

kdf
2005-01-04, 01:14
Quoting Phillip Kerman <lists (AT) phillipkerman (DOT) com>:

> First... I was reacting to this:
>
> >Now that this is in place,
> > > expect a lot
> > > of fast improvement!
>
> ..not so much just a chance to vent.

of course. but of course, that statement was in reference to 6.0, which is
currently in alpha test (essentially) and most likely will not be an official
release for some time.

> > If you want stability, use 5.4.1. write bug reports on that
> > based on STABILITY
> > ONLY. That is the focus of 5.4.1 and that stream. 6.0 is
> > for speed of data
> > handling. dropouts might be reduced, but they are really rather a
> > streaming/network problem that may see some improvement as
> > data handling speeds
> > up.
>
> Okay... but is 5.4.1 released yet? I'm not really into doing the nightly
> builds any more.

no, it isn't. however, that too, is in response to other user feedback.
Releasing is met with harsh feedabck if its even slightly less than perfect.
The only way to get that even close is to make it available to all those who
can offer some help to make it as stable as possible. There are always a large
group of people who say nothing until the release, and then are loudly upset
that their particular problem hasnt' been solved. oddly, some of those
complaints are the first we hear of them, or as yet unreproducable by those who
are working on the code.

>
>
> I do think my questions are pointed at making the general suggestion that my
> pet issues (and others) are given some priority. All I have is empirical
> data that the 5.4 release changed performance slightly. It could easily be
> something else... but I look at the sincerely valuable feature of RSS and
> just have to wonder if that comes at the expense of issues that I would
> consider more primary.

you and I both. However, my feelings about fixing bugs are moderated by my
experience as an engineer. Every day I see situations where the needs of
several directions are priority. Whether it be marketing, or support or
investors, priorities change. Your issue is dropouts, but there are just as
many users who will 'hint' that they will return their squeezebox unless their
wife gets instant access to news and internet radio. that's just one example.
yes, its the squeeky wheel. I realise that, but I dont have to like it :) My
dislike for it, is something I'm free to voice, just as much as your
dissatisfaction over dropouts.
>
> I really don't intend to sound like I'm harping on stuff... certainly don't
> want to reduce anyone's enthusiasm. But... like I say, I was just asking
> because of Dean's words above.

Again, it wasnt' directed at you. In fact, it is more that you have offered a
more reasonable stance, that I bother to voice mine. I have no desire to take
part in religious flame wars. You will see fast improvement in 6.0, as Dean
said, but it will not be stable. In fact, as fo right now cvs will not
complete a rescan for me without going into an infinite loop. However, at the
same time, with my own tweaking to force a bypasss of the loop, I can see other
great gains, like the browsedb feature. Browse by year is added and the other
browse modes seem much faster. My 'fix', however, currently kills CUE sheets.

In summary...the definition of improvement is subjective when it comes to 6.0.
Lots of new fixes, but not all that stable for now. fast improvements, yes.
however, if your personal top priority is streaming....not so much.

-kdf

Marc Sherman
2005-01-04, 06:04
kdf wrote:
>
> In fact, as fo right now cvs will not complete a rescan for me
> without going into an infinite loop. However, at the same time, with
> my own tweaking to force a bypasss of the loop, I can see other great
> gains, like the browsedb feature. Browse by year is added and the
> other browse modes seem much faster. My 'fix', however, currently
> kills CUE sheets.
>
> In summary...the definition of improvement is subjective when it
> comes to 6.0. Lots of new fixes, but not all that stable for now.
> fast improvements, yes. however, if your personal top priority is
> streaming....not so much.

Thanks for the insight into the current state of the 6.0 branch, kdf.
Is there a public bug database where these issues can be browsed and
tracked by interested users (particularly ones with hacking skills who
might be motivated to help)?

BTW, how many Debian users are there here? I've been thinking about
picking up the Debian packaging. This'll be my first package, so if
anyone has more experience at it than I do, please step up. :) Bruno
(the current maitainer, who's got 4.2.6 in the archive as slimp3, and
5.2.1 on a private website waiting for sponsorship for 5 months now) has
OK'd me taking over the package.

- Marc

Marc Sherman
2005-01-04, 06:09
Marc Sherman wrote:
>
> Thanks for the insight into the current state of the 6.0 branch, kdf. Is
> there a public bug database where these issues can be browsed and
> tracked by interested users (particularly ones with hacking skills who
> might be motivated to help)?

Duh. bugs.slimdevices.com. Sorry, that'll teach me to post before a>
reading the entire thread, and b> finishing my morning coffee.

- Marc

Craig Eales
2005-01-04, 06:20
Marc,

I am a debian user (sarge - testing 2.6 kernel) - however I have no
experience of the package mechanism (apart from as a consumer). But I
am more than willing to be a tester - give me a shout when you have
somehting to try.

Craig

On Tue, 04 Jan 2005 08:04:32 -0500, Marc Sherman <msherman (AT) projectile (DOT) ca> wrote:
> kdf wrote:
> >
> > In fact, as fo right now cvs will not complete a rescan for me
> > without going into an infinite loop. However, at the same time, with
> > my own tweaking to force a bypasss of the loop, I can see other great
> > gains, like the browsedb feature. Browse by year is added and the
> > other browse modes seem much faster. My 'fix', however, currently
> > kills CUE sheets.
> >
> > In summary...the definition of improvement is subjective when it
> > comes to 6.0. Lots of new fixes, but not all that stable for now.
> > fast improvements, yes. however, if your personal top priority is
> > streaming....not so much.
>
> Thanks for the insight into the current state of the 6.0 branch, kdf.
> Is there a public bug database where these issues can be browsed and
> tracked by interested users (particularly ones with hacking skills who
> might be motivated to help)?
>
> BTW, how many Debian users are there here? I've been thinking about
> picking up the Debian packaging. This'll be my first package, so if
> anyone has more experience at it than I do, please step up. :) Bruno
> (the current maitainer, who's got 4.2.6 in the archive as slimp3, and
> 5.2.1 on a private website waiting for sponsorship for 5 months now) has
> OK'd me taking over the package.
>
> - Marc
>