[Be-devel] Bugs affecting previous state

[Harald Hoyer]

> Is there anything in the works for Bugs Everywhere to put bugs in @
> points in history?  It seems problematic that bugs that affect
> something due to a past point is not reportable as such.....
> 
> Example:
> 
> A - B - C - D
>    \- X
> 
> Complicated case:
> 	Bug noticed @ C
> 	-- Reported in C
> 	Bug also noticed to affect X
> 	?copied to X?
> 	Bug finally noticed to be caused @ A
> 	-- Reports @ X and C optionally removed and A setup
> 
> Is this sort of workflow supported?
> 	

Exactly the problem, what I wanted to report here also.

Attaching a bug report to version A is not possible, because a version history already distributed cannot be 
altered.

So maybe the bug database cannot be tied to the VCS, because if you check out version A, you will never see 
the reported bug.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3645 bytes
Desc: S/MIME Cryptographic Signature
Url : http://void.printf.net/pipermail/be-devel/attachments/20080331/a11b733b/smime.bin