What is this "bug sticky" thing?

[Postman]

Dr. Sound has requested that we either add a "+1" to his poll or stay away. I'm hoping to see useful discussion about it here since it is not welcomed in the other thread.

Please explain to me how a "bug sticky" would work, exactly. My knee jerk reaction is, "hey great, I'd like to see a compilation of all the bad things so I can avoid them". But, how to maintain it in a useful form?

Bugs and features are constantly changing with each new version and cs update. Add to that some human nature and public access and I think a "bug sticky" would quickly become a very long string of bugs-of-the-moment, "bugs" that are actually design features, opinions, misinformation, and lots and lots of feature requests and other stuff that could have been avoided by reading the manual. And then the meanderings of off topic posts. I think it would become a big, long, unsearchable series of complaints. Just like most of the rest of the DUC.

That's my take on it, but maybe I'm not seeing it in a proper light? Maybe there is a different approach that IS manageable?

[dr sound]

Postman,
Here it is...
You wanted to discuss it and this is the right place. I was ONLY looking for a + or a - because all to often the topic makes a left turn and the next thing your talking about how the weather effects you mixes( not really but you get the idea).
I am very open about discussing it but just wanted to see if there is even enough backing for "a bug sticky". Right now there are 734 views and ONLY
43 votes.
To me that is dissapointing. People would rather stay on the sidelines than vote. Let's hope your topic gets lot's of traffic and comments because my
"a bug sticky' is not getting the reaction I had hoped.
Now let's do some discussion on your comments.

[reichman]

Wait, isn't the whole concept that the "bug sticky" would be READ-ONLY by all of us, and that Avid Audio Support would be the only entity updating it?

I think that's the cleanest way to do it. Endless complaining and duplicate posting on this list would be reduced greatly if we could see what Avid was working on and fixing for us.

Good idea Dr. Sound!

[dr sound]

Originally Posted by reichman

Wait, isn't the whole concept that the "bug sticky" would be READ-ONLY by all of us, and that Avid Audio Support would be the only entity updating it?

I think that's the cleanest way to do it. Endless complaining and duplicate posting on this list would be reduced greatly if we could see what Avid was working on and fixing for us.

Good idea Dr. Sound!

Yes, That is EXACTLY the way I envisioned it.
Right now we need to show "Avid" that we are concerned.
START VOTING on "a bug sticky" and start discussing here !

[minister]

+1

[CD Productions]

Sorry Minister, This is for discussions, voting is in the "Bug Sticky" post. Arguments are in the next office, this is getting hit over the head lessons.
Back on topic, I think there has to be some user input. Sometimes, there are multiple complaints about a "bug" but it's not being addressed by Avid. Maybe, when a complaint post reaches a certain number of posts, that bug is added to the sticky. Then it becomes like a "to do" list as well as a "we're looking into it" list.

[Stuart P.]

Originally Posted by minister

+1

Don't worry, I got it.

[tomlowd]

-1

y'all are dreaming

[CLee]

Are you thinking of a "This is a list of the bugs we will fix in the next CS release" thread?

I'm not sure how it would work because you need to have many things going on at once.

1. here is a list of all known bugs.
2. here is a list of the bugs we will fix in the next CS
3. here is a list of the bugs we are working on but don't have a fix for
4. here is a list of the bugs that will never get fixed (everything not in 2 & 3)

Then it all has to be somehow carried forward with each release.

It seems like a great idea, but it requires a forthcoming attitude by DIGI on the bug list. Plus it needs to be maintained for HD and LE on both the Mac and Windows systems.

All that said, I would go for it.

[danijel]

Originally Posted by dr sound

To me that is dissapointing. People would rather stay on the sidelines than vote. Let's hope your topic gets lot's of traffic and comments because my
"a bug sticky' is not getting the reaction I had hoped.

Don't loose your faith in humankind just yet! I don't think anyone wants NOT to have "an up-to-date bug-base", but I guess a lot of people (including me) didn't vote it because I don't see how it would work in a forum sticky format. So it's great that we have this thread to further discuss.
A bug database report is (IMHO) a slightly complicated matter, and as CLee put it, a multiple-moving target, and as such is not appropriate to maintain in plain txt format.
If Digi had a good web-based interface for us to access the bug-base (by entering ones platform, software version etc), then it would be a simple matter of making an automated script that would read the database and update the sticky (or whatever) daily.
So, a "bug sticky", or another report location are an end, but does Digi have the will to do it? They certainly have their internal bug-base, so I think the vote topic should be re-formulated as:

Dear Digi, please open up your bug database to public, if you are willing and able. +1

And perhaps put it in "General Discussion" forum to get more feedback, because this is not just a post thing.