From: Vampire <Vam...@gm...> - 2008-11-19 23:28:45
|
Matthieu Casanova schrieb: > Hi, I'm late but I'll try to explain this because I wrote this list. > It was the ideas I had about the code, but in fact most of those tasks > are not so important. > I'll comment them inline > > > On Sat, Nov 15, 2008 at 10:14 PM, Dale Anson <da...@gr... > <mailto:da...@gr...>> wrote: > > Alan's list is on the SF wiki: > > > http://jedit.wiki.sourceforge.net/Core+development > > > roadmap to 4.3 final > > Legend: > [X] Item rejected / will not be done (append explanation) > [+] Item is done (implemented and closed) > > * [+] Remove "simplified keyboard handling", since the > standard keyboard handling works fine now (danson) > * Test framework with 10 basic smoke tests in FEST > <http://code.google.com/p/fest/> or Abbott and Costello > <http://abbot.sourceforge.net/doc/overview.shtml> or > Marathon <http://www.marathontesting.com/Marathon.html> > Vampire: No matter which gets used, I suggest and wish that > the JUnit variant is used. AFIAK they have both at least > JUnit as an option. > > > Matthieu: This one is from Alan, of course it would be good to have > such tests but I don't think we can wait for them to release 4.3final > > > * > > > * Remove deprecated code (preferably without binary breakage) > Vampire: I wouldn't remove the deprecated code before 5.0 > final. I know the common behaviour of only doing not > backward compatible changes on change of major version if > possible. I suggest doing this for jEdit also. > > > Matthieu: I agree with Vampire, let's do this in the next major release > > * > > > * Remove JVM workaround for java version < 1.4 > Q: Could someone expand on this here? > > > Matthieu: there was some tests agains the JVM version but I'm not sure > they still exists > > > * > > > * Fix javadoc warnings, there are still some around > > > Matthieu: of course it would be better with a perfect javadoc but we > should not delay a release for this too > > * BufferList - option to show view-local or editpane-local > buffer sets > * Remove the usage or overriding of deprecated APIs and the > usage of unchecked or unsafe operations. There are more than > 100 compiler warnings about this if you compile jEdit. The > compiler stops showing them after 100 warnings, so I don't > know how many there actually are. > > Matthieu: like fixing javadoc we can fix those warnings but should not > block the release for this I guess there are good reasons why these APIs are deprecated or marked as unchecked or unsafe. As we decided to require at least Java 5 we should also remove these warnings and replace the usages by appropriate new way of usage. In my opinion this IS a hard requirement for the final release. > > * Reduce the amount of open bugs to an at most two digit > number and no bug older than two months, or maybe 6 months, > except if there is a really good reason. Currently there are > 215 open bugs. And with this requirement I mean fixing > almost all these bugs and not closing them as "Wont Fix" or > something like that. ;-) Additionally the final release > should be released as pre release already and more or less > NO new bugs have to be found against it. > * STOP implementing new features, icons, whatever and thus > introducing new bugs, instead concentrate on reproducing and > fixing existing bugs. This is the ONLY way how to get to a > final release in a senseful manner. As long as people keep > implement new features, we never get to a final release. At > least not to a one that I am happy with. > > > Matthieu: I agree with those too, except for microfeatures. > But I also think we should not wait to have no remaining bugs to > release jEdit 4.3final otherwise we will never release it You will never get a software bug-free and I also didn't write this as you can read above. ;-) Maybe my bad english is not saying exactly what I meant. > > Matthieu > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ |