[ James (Cox) can you please quote people correctly ... ] Sorry for the confusion. I was not implying in any way that _existing_ bugs be automatically marked as "Try Newer Version", I was suggesting that perhaphs _new_ bugs be marked that way if they are submitted with a (very) old release. That seems to be what happens now, but it is done by hand.
And as for _existing_ bugs ... There are many bugs that are reported in areas that have had signifigant changes since 4.0.6 (for example). I don't still have 4.0.6 running anywhere to test them. What, if any, policy is there for marking old bugs with "Try Newer Version"? For example, I could try to duplicate said bug, and if the problem is not exhibited on my current version it seems legitimate to mark it as "Try Newer Version". But in many cases the reported OS is Linux, and I run FreeBSD ... should I still force them to upgrade, since it might be a OS issue? -James (Flemer) On Sun, 28 Apr 2002, James Cox wrote: > Stig said: > > That would effectively be ignoring most bugs. I don't see how we can > > mark bugs as "try a newer version" without examining each bug. > > Right. > > what i am trying to get across is that perhaps we can make a move to look at > all the < 4.2 bugs, and see which can be closed off. > > james -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
