Lms 7.8?

[bobertuk]

Following a hint in another thread

Is LMS 7.8 just a continuation of 7.7 bug fixes or is there going to be anything new?

If there is something new going into 7.8 any news/hints about what it/they will be?

Bob

[mherger]

> Is LMS 7.8 just a continuation of 7.7 bug fixes or is there going to be
> anything new?

It will be a major update.

> If there is something new going into 7.8 any news/hints about what
> it/they will be?

Make the thing nicer to use. Eg. my first checkin to SP 7.8 is to loosen
the upgrade/downgrade mechanism: when 7.8.0 is being released, but you
prefer to stick with 7.7.7 for a while, you might no longer see the
firmware screen whenever you switch from LMS to mysb.com.

If LMS still has that name by then anyway :-).

--

Michael

[bobertuk]

Thank you Michael.

If LMS still has that name by then anyway :-).

Michael

Intriguing...


Bob

[MrSinatra]

i think it would make a lot of sense for you guys to implement some bugs that have a lot of votes, why not do that? do you guys care about votes or no?

also, the antique home>whatever method sucks, as does the "one master list" that doesn't allow to browse by artist, or AA, or whatever on the fly.

why not redesign that so that there are a couple of default sort methods and user made sort methods?

[mherger]

> i think it would make a lot of sense for you guys to implement some bugs
> that have a lot of votes, why not do that? do you guys care about votes
> or no?

We do. Probably not at the level some might want us to care, but still.
Keep in mind that even 100 votes only represent a very small fraction of
our users. Other important channels are eg. the questionnaire every new
customer is invited to fill in after he registers for a product.

--

Michael

[gharris999]

Michael: for those of us who like to follow along at home, would you be willing to give us your best guess as to when we'll see enough changes that it will be worth running the new svn code? A week? Two weeks? Or would you rather not have us peering over your shoulder quite yet?

I, for one, always find it gratifying to watch you guys try out new ideas.

[mherger]

> Michael: for those of us who like to follow along at home, would you be
> willing to give us your best guess as to when we'll see enough changes
> that it will be worth running the new svn code? A week? Two weeks?

I don't expect major changes in the next few weeks. We're only getting
started. The aforementioned change re. firmware downgrades might be the
biggest change for a while :-). But feel free to use it! We're thankful
for every early tester we get.

> Or would you rather not have us peering over your shoulder quite yet?

Nah, the code is publicly available. Don't expect to see the secret new
features in there :-P.

--

Michael

[Jeff Flowerday]

> i think it would make a lot of sense for you guys to implement some bugs
> that have a lot of votes, why not do that? do you guys care about votes
> or no?

We do. Probably not at the level some might want us to care, but still.
Keep in mind that even 100 votes only represent a very small fraction of
our users. Other important channels are eg. the questionnaire every new
customer is invited to fill in after he registers for a product.

--

Michael

And the larger fraction live with the bugs and or don't know how to file a bug report or vote on one.

[mherger]

> And the larger fraction live with the bugs and or don't know how to
> file a bug report or vote on one.

They can get in touch with support. Support probably can't help, but they
would raise issues if they got repeated complaints about the same problem.

--

Michael

[MrSinatra]

> i think it would make a lot of sense for you guys to implement some bugs
> that have a lot of votes, why not do that? do you guys care about votes
> or no?

We do. Probably not at the level some might want us to care, but still.
Keep in mind that even 100 votes only represent a very small fraction of
our users. Other important channels are eg. the questionnaire every new
customer is invited to fill in after he registers for a product.
--
Michael

i have to say, that while i appreciate your honesty, this is the worst possible response b/c it just goes to show you guys ignore feedback.

first of all, there is only one bug with 100 votes. so by your measure, no bug means anything, b/c no bug has enough votes to matter.

secondly, its nonsense to disregard votes. presidential polling that is ACCURATE is only a small fraction of the overall population, sometimes not even 1000 in the sample for a country of over 300 MILLION. bug votes are the same thing. and the barriers to bug voting need to be kept in mind.

your answer, to me, says: "we do NOT care about voting, b/c it isn't representative of anything statistically important."

that is a SAD state of affairs imo. and it means you guys aren't taking cues from users.

> And the larger fraction live with the bugs and or don't know how to
> file a bug report or vote on one.

They can get in touch with support. Support probably can't help, but they
would raise issues if they got repeated complaints about the same problem.
--
Michael

wow, wonderful. number 1, support has nothing to do with certain bugs or enhancements. people aren't going to call support over bug 142 for instance, which you call one of the oldest and most popular bugs.

support is for immediate showstopping issues. votes on bug tracker meanwhile should absolutely help guide the road map, as they are a good idea of whats important to the SB population. i'm not saying they should rule alone, but you guys need to stop IGNORING them, which is what has gone on for YEARS now.