[mb-users] "Edit All" - Is it problematic to understand?
Rod Begbie
rodbegbie at gmail.com
Mon Jul 17 16:52:02 UTC 2006
On 7/17/06, Stefan Kestenholz <keschte at gmail.com> wrote:
> In lots of parts of the site, it has bettered. Are you my paying
> customer, what makes you think that you tell what i have to do?
Stefan --
We're a community. We all want to see MB get better. Steve & I (and
others) have concerns about some of the things that were implemented.
We raised them as bugs. A lot of them got shot down by you as "Works
for Me".
We still think they need to be worked on.
> the testing phase was long enough to fix things that were reported
> during that phase. If people either aren't interested and don't test,
> or if they are scared and therefore don't test, then we had no other
> option to just release it and collect feedback afterwards
If I may...
I looked at the server round about June 8th, when the testing was
announced on the blog
(http://blog.musicbrainz.org/archives/2006/06/new_server_rele_1.html).
Entered a bunch of tickets.
There was no "Hey, come test again" message. No "We're planning on
releasing this next Sunday." message. Just silence.
When I inferred last Sunday that a release was planned *that day*, I
took the time to go test, and found a bunch of stuff that I was
unhappy with.
As a suggestion for next time round: Have "release candidates". Say
"Hey, there's a new beta. We've added these features: a.,b,c. Come
test it again!". Or 'Hey, this is now feature complete: Come
nitpick."
Because people will come poke at the server for a few hours when told
to, post some bugs, then *never touch it again unless reminded*.
Happens with every beta I've ever seen.
Rod.
--
:: Rod Begbie :: http://groovymother.com/ ::
More information about the MusicBrainz-users
mailing list