Hi Chris,
My rantings are only about the
semantic/terminology of the whole "stable" / "unstable" thingy.
Especially for non-native English speakers (like me) and in many
languages (and I can only speak of the ones derived from Latin/Greek -
a big chunk of them), "unstable" has many meanings, all of them bad to
very bad.
to native english speakers, too -- truly, the concept of "unstable"
software often specifically means software that crashes.
So we do need a new term:
"in flux"
"development" - kind of implies not ready for production, also.
or do we need a word at all -- it's just "version 2.9" IN the docs, we
can use works like the above:
"The 2.8 series has a fixed API -- future changes will be bug-fixes
only, with no API changes"
"In the 2.9 series, there may be some small alterations to the API
from point release to point release"
Am I the only one who reads this discussion and comes to the conclusion that wxWidgets just has figure out a way to put out a new stable release version more than once a decade or so? 
You can debate what unstable should mean or how to word it, but regardless, the 2.9 release cycle signifies that "we're not just fixing bugs, we're changing APIs around and adding/removing functionality", which is just another way of saying "the 3.0 release is still under construction." So the simple question becomes, exactly when is 3.0 done? A lot of people out there prefer to wait until the project is done with a stable release and commits to just bug fixes. It's totally a reasonable position to take from my viewpoint, and I think they're not going to take kindly to persuasion like "you know, you don't REALLY need to wait for the stable version," no matter how you try to finesse the terms stable and unstable. 
TBH, I really feel that wxWidgets is kind of wandering in the woods at this point, from a project management standpoint. No one's steering the ship. There aren't clear future goals nor any real plan for any practical purpose, there's too much hesitance to do new and cool or disruptive things for fear of 'failure', and if you do contribute, you'll have to deal with things like VC6 compatibility, pre-STL data types, mucking with bakefiles, and a lot of other overhead you don't see with other projects. Plus, who knows when your contribution will even make it into an actual release. (Even dev releases average about once a year.)
To outsiders at least, I think the project looks like it's starting to slow to a crawl, and when you add all the hassles of contributing to that, I think it really makes it hard to get excited about contributing to the project. wxPython and its work on things like Phoenix is the only thing that keeps me excited about the project doing new and cool things. 
Regards,
Kevin
···
On Dec 14, 2012, at 10:10 AM, Chris Barker - NOAA Federal wrote:
On Fri, Dec 14, 2012 at 12:15 AM, Andrea Gavana <andrea.gavana@gmail.com> wrote:
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
--
To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en