I'm curious about whether the team has a policy on closing bugs on older releases. I took the liberty of assigning one to myself this morning and closing it with fixed in next release. I felt ok about doing that because it was against 3.2.0-4 so 3.2.3-1 is the next 'rpm release'. That is, I didn't think it was a big deal to require an upgrade from one 3.2.x to a newer one to get a fix.
As I look back through the bugs database, there are lots of reports, some of them fairly recent, against 3.0.x and even 2.x. Many of them are issues that I know are moot or fixed with newer releases. I didn't touch those. Lots of them look like they were FINR and just left open. So, I'm curious about issues like: do we ever declare end-of-life on old releases? Is it OK to close a bug against a 3.0.1 release with instructions to upgrade to the newest release? Or, are you deliberately leaving the bug open because it isn't fixed in the release the bug is against? ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
