nitter
L. David Baron @dbaron@w3c.social
@davidbaron
30 Jan 2013
New blog entry: Moving bug history out of the primary display of a bug report
dbaron.org/log/20130129-bugz…
Jan 30, 2013 · 5:28 AM UTC
4
1
4
Mark Finkle
@mfinkle
30 Jan 2013
Replying to
@dougturner
@dougturner
@davidbaron
Maybe a way to set comments as "obsolete". Then you're only looking at the relevant information.
1
L. David Baron @dbaron@w3c.social
@davidbaron
30 Jan 2013
@mfinkle
@dougturner
Except I really think revising rather than appending will put the focus on what's important.
1
Matthew Paul Thomas :: @mpt@mastodon.nz
@mpt
30 Jan 2013
Replying to
@davidbaron
@davidbaron
Launchpad has had editable bug descriptions for 8 years. Now even reporting at Bugzilla feels arcane. Much worse for assignees!
1
L. David Baron @dbaron@w3c.social
@davidbaron
30 Jan 2013
@mpt
Though a lot happens in launchpad's stream of comments, at least on bugs I've seen; I want to get rid of the stream of comments.
1
more replies
FremyCompany@mastodon.social (François REMY)
@FremyCompany
30 Jan 2013
Replying to
@davidbaron
@davidbaron
I've the same complaints about making proposals on www-style and many mailing lists.
FremyCompany@mastodon.social (François REMY)
@FremyCompany
30 Jan 2013
Replying to
@davidbaron
@davidbaron
fremycompany.com/BG/2012/Sta…
skip to 'The need for an unified proposal repository' (ie: state != discussion)
1
Robin Stocker
@niborst
30 Jan 2013
Replying to
@davidbaron
@davidbaron
Jira has an editable description (and comments), it works well. Editing of description should probably be restricted.