Bug thread discussion

[Ben]

I really did not want to change the posting aside from adding additional attributes.

While I am at this dreaming thing...

The icons in the left hand column could be changed to reflect the catagory the frequent flyers assigned.

Ben

[Ben]

The state of the Bug Thread will be reviewed next week (16 March 2006).

Please post any thought suggestions or desires you have regarding same here so your voice can be heard.

If you prefer another forum to express your thoughts you can post to this thread on the LAVA forum

http://forums.lavag.org/index.php?showtopic=2817&hl=

Ben

[Ben]

Hi All,

I like the "Bug List" introduced by CC in this this thread.

http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=2033&jump=true

Anyone else have an opinion on this subject?

Ben

[chilly_charly]

Yeah ! I think also that's a great idea. Thanks CC !

However, I already found two bugs in the Bug List : Altenbach and Ben are reporting future bugs, in December 2006 !

I hope the next reporter, while ransacking the LAVA BL or going back in time to add more entries to TBL, will manage to correct this unacceptable mistake.


Some suggestions to allow for an efficient search : fill the first column with appropriate key words : PDA, graphs, App Builder are fine, but you could add Files, Arrays, Tables...

May be an additionnal column could provide a FP/Diagram/Exe info ?

I think that a reduced set of "official" key words could really help us. Could somebody, more fluent in english than the annoying frog, propose something ?


Some more ideas :

- impact index, from low to critical

- "workaround exists" column

- platform columns.


One issue is that any modification, for instance after a bug has been acknowledged by NI or also found on other versions or platforms, requires a new reply in the BP board. How could we find a way to edit this file, without being obliged to create new theads ?

[Ben]

Go CC!

I'll try to reply later.

Anyone else want to share their thought?

Ben

[daijoubu]

To start with, I like the bug list.  But the latest incarnation with the spreadsheet...   Why are you reinventing the wheel?  There are literally thousands of bugtracking applications on the web.  One of those must be adequate for this.  If nobody wants to manage it and host it offsite, how about creating a sub-forum.  Each thread in the sub-forum is one bug.  This might be a little more workable, and with the new features, we could subscribe to reported bugs that we're interested in.

[Ben]

Just to update this thread after a long time....

...well eventually we got the Bug List going and as indicated in this post, we have the full support of NI in this effort.

Ben

[Ben]

Chrstian closing the October and opening the November Bug Threads reminded me of an idea.

It would be nice if a link to the "Known Bug List" for the current version of LV (maintained by NI) should be included in the post that start the new lists.

That way people can first check if their issue is known before they add to the list.

BTW

Congratulations to all LabVIEW Bug Hunters and Trackers!

Your colaborative efforts have opened a wonderful time saving resource that can only make LabVIEW better.

Thank you!

Ben

[Ben]

I'd like to thank Partha for the work in keeping the Bug Thread active for March.

Came real close to a monopoly.

Thank you for the work required to keep us all updated!

Ben

[Ben]

Bump!

This thread is for discusions reagarding the various Bug Threads. Please post your comments re: the bug thread here.

Thank you,

Ben