[Be-devel] Bugs affecting previous state

[Andrew Sayman]

Seems like the focus of bugs everywhere is to track bug resolutions,
not necessarily bug beginnings. It feels almost incompatible with the
idea to what to attach it with something already in the repository
like that.

With most software development, it's usually advised to be developing
against the latest sources. What would be a reasonable work-flow where
the late reporting of the bug *really* affects you? It seems like it
would come up if you were going to make a branch off of the earlier to
try some experimental development before a critical decision was made.

A - B - C - D
 \-Y   \- X

It seems like to resolve this situation to track meaningful bugs there
would need to be a tool to pull all of the reports from the furthest
head and compare it. When you branch for Y, you want the bug report on
C to follow you because you might fix it.
-- 
Andrew Sayman
Jabber: lorien420 at jabber.org