I think 2.10.x should be the last in the "2 stream", and that need 2.10.x is needed, instead of jumping to 3.0.x, since there are a lot of features in the CVS stream that should be provided to users before 3.0.x is released.
(My plan is for 3.0.x to have SVG output as the main new "3 stream" feature, and that will require a LOT of work and a LOT of testing, so 3.0.x won't be coming until perhaps the end of summer.)
Given this, now is the time to discuss whether the CVS version (see doc/Development_Version.html file) is ready for a 2.10 release, or whether some of the planned features (see doc/Plans.html file) should be implemented first.
Here are my initial thoughts:
1. The 'popt' work should wait for 3.x since it will be a change for the user, and since the work may be hard for me. It's hard because there are various versions of the popt library, and because I have to be careful not to break existing code (e.g. Ed's code uses commandline arguments a lot).
2. The plan to make 'set axes style' take word-based commands sounds great, but for the life of me I can't invent any simple (guessable) words for the items 0, 1, and 2. Any ideas on that?
Question: what do you think, about these particular issues, and the general plan for a release? ... how much [new features] is enough?
Thanks!!
Dan.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think 2.10.x should be the last in the "2 stream", and that need 2.10.x is needed, instead of jumping to 3.0.x, since there are a lot of features in the CVS stream that should be provided to users before 3.0.x is released.
(My plan is for 3.0.x to have SVG output as the main new "3 stream" feature, and that will require a LOT of work and a LOT of testing, so 3.0.x won't be coming until perhaps the end of summer.)
Given this, now is the time to discuss whether the CVS version (see doc/Development_Version.html file) is ready for a 2.10 release, or whether some of the planned features (see doc/Plans.html file) should be implemented first.
Here are my initial thoughts:
1. The 'popt' work should wait for 3.x since it will be a change for the user, and since the work may be hard for me. It's hard because there are various versions of the popt library, and because I have to be careful not to break existing code (e.g. Ed's code uses commandline arguments a lot).
2. The plan to make 'set axes style' take word-based commands sounds great, but for the life of me I can't invent any simple (guessable) words for the items 0, 1, and 2. Any ideas on that?
Question: what do you think, about these particular issues, and the general plan for a release? ... how much [new features] is enough?
Thanks!!
Dan.