Hi list, I actually don't care about this number issues (it's ok for me if we go to PLplot 5.146), but wouldn't it be time to step to 6.0 any time soon? This time we could really branch PLplot and e.g. remove all drivers/code which are(is unmaintained. If someone wants to use these drivers/this code, he/she should either volunteer to maintain the driver or use the 5.x branch, which we could maintain for some time. My considerations are the following:
* PLplot improved/changed a lot over the last years and it's time to show the users the the code changed considerably and isn't just "only maintained" * we could use this opportunity to remove code, which is not maintained anymore (Alan did already remove some code already) * we also should use this opportunity to streamline our efforts to raise the quality of the project overall. - e.g. documentation - for a 6.0 version we could try to improve the documentation - implement/fix bugs/features/requests on our trackers (also Alan started this already) - .... * we could also do some API changes, since it's a new version, so this might be the right time to do that. What I mean is, we could try to agree on a roadmap to a 6.0 version - if we implement everything (most of it) 6.0 is released. The timeframe wouldn't be anytime soon, but first we could discuss what should be on the roadmap and then try to streamline our efforts, i.e. a "bug hunting month" or a "documentation month" where all who have time, work mostly on one task. Normally these are "bug hunting days", but hey let's stay realistic ;). I don't propose that we should do a lot of code changes, since I think, that PLplot now already "deserves" a major version number change. My proposal is just, that we bring everything on par with the code and the make the 6.0 release. We could also (as Alan also already started) streamline our testing efforts, so that we identify platforms which we support. E.g. nobody of the developers here has access to Mac OS X 10.6 obviously so this wouldn't be a supported platform. Supported platforms should be tested regularily. If we identify all these tasks it would also be easier to apply for GSOC. Last year we were really to late to apply for anything. What do you think? Actually, most of that was already started/ discussed by Alan, I just want to streamline the efforts and the result should be PLplot 6.0. Regards, Werner -- Dr. Werner Smekal Institut fuer Allgemeine Physik Technische Universitaet Wien Wiedner Hauptstr 8-10 A-1040 Wien Austria email: sme...@iap.tuwien.ac.at web: http://www.iap.tuwien.ac.at/~smekal phone: +43-(0)1-58801-13463 (office), +43-(0)1-58801-13469 (laboratory) fax: +43-(0)1-58801-13499 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
