[development] Re: fixed project releases

Gabor Hojtsy gabor at hojtsy.hu
Fri Jan 27 15:01:24 UTC 2006

> One related issue: any issue  that says "cvs" now and does not get
> fixed, remains as cvs even if we release 4.7, then 4.8 then 5.0, then
> 5.1, ...etc. Later someone has to go thru and mark some of them as
> no longer applicable, ...etc.
> Is there a better way of doing this? For example, all current issues
> are marked either "4.6" or "pre-4.7". Future ones become  "4.7" if
> they are against that live branch, or "pre-4.8".
> Would this ease tracking of old issue and give a sense of how long
> they have been around  (since how many releases, not number of
> days).

It does not work this way. One bug filed against cvs in the 4.5 days
could still perfectly be applicable against current days CVS. The fact
that a new release is out, does not mean every bug against the
prereleease code is now fixed, or should be fixed in that release cycle.


More information about the development mailing list