2010/7/28 Kristof Coomans <[email protected]> > 2010/7/28 Björn Dieding <[email protected]>: > > I would say, they should be reopened. > Well, please do, and update the affected version (see below).
> Betreff: [Sdk-public] Valid enhancement requests / issues being closed in > the issue tracker > > > > Hi > > > > I am quite concerned that good and valid enhancement requests / issues > > (some examples: http://issues.ez.no/IssueView.php?Id=10489, > > http://issues.ez.no/IssueView.php?Id=14199) are currently being closed > > as won't fix or invalid because there was no feedback for a while. Is > > this the current policy? > > > > Best regards > > > > Kristof > > Now I see issues being closed with this message: > > "eZ Publish has undergone a > substantial rewrite in the transition from PHP4 to PHP5, which may > invalidate old issues." > > This is IMHO a big lie. There did not happen a rewrite > (http://en.wikipedia.org/wiki/Rewrite_%28programming%29) in the > transition from PHP 4 to PHP 5. > > I understand you might want to close certain issues because you simply > don't want to implement them, but please don't hide then behind such > statements which are not correct. > It's not really my role to answer that, but since we're facing an IssueGate affair here... We have 3 thousand open issues, including about 1000 that weren't updated since december 2007 (release date for 4.0). If we close all of these in an automated way, which is what we intend to do, we will be left with about 1400 issues to handle, and this is already more than we can handle. As said in the message, and that is the part I do believe you have removed when quoting us, we are perfectly okay with the authors, or anyone else, re-opening the issues if they are still considered valid. Now, we perfectly know that there hasn't been a big ass rewrite of eZ Publish since versions 3.x, but it still has undergone massive changes in many areas, and it is very likely that lots of issues are now invalid. I know some of them aren't, but if they are, just reopen them and update the affected versions. -- Bertrand
-- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
