Thorsten Haude wrote:
It sure is, that's why I wondered why you would bring these things up. I don't mind if additional bugs are closed before the release, but we should focus on the release-criticals.
Not to put too fine a point on it, but I think the selection of release-criticals is too overreaching.
If we want to get it out the door, we should focus on *regressions from the last release, and cut out absolutely everything else. At this point in the lame I would drop anything that doesn't cause nedit to crash and ship it.
I see too many bugs nominated for fixing, or just committed, that aren't regressions. Perhaps it causes some other bugs/regressions. The result is we get further away from a release instead closer to one.
We can't fix every bug, but we can certainly make the next release incrementally better than that previous one.
-- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
