On 5/4/10 3:44 PM, Ed Leafe wrote: > On May 4, 2010, at 12:15 AM, Paul McNett ☆ wrote: > >>> Yes, there have been a lot of commits, but no new significant >>> functionality has been added, and no new capabilities exist. IOW, you could >>> create pretty much the same app then as you can now, with a few bugs fixed >>> in newer versions. >> >> Which makes for a pretty decent argument that it may be mature enough to >> warrant 1.0 >> status. > > > Not really - it means that nobody has had sufficient time to invest > into adding whatever was missing back then. A 1.0 release (vs. a 0.x release) > doesn't mean stable; it means feature-complete. All releases should have some > notion of stability before being released, and minor point releases are > usually additional stability.
I wasn't really talking about stability, which has different meanings in different contexts. Nothing's ever really feature-complete. Portions of Dabo certainly aren't complete[1], but the API has been fairly stable and mature since probably 2008 or so. I'm +1 on rolling a new release. I'm +0 on making it 1.0. [1] Database support beyond MySQL, PostgreSQL, SQLite, and Firebird; the report writer; localization; setup.py come to mind, but I think even these are feature-complete and mature in their own ways to be part of an overall 1.0 Dabo. > Oh, and what's with the star in your name? Did you sign a movie deal or > something? ;-) Just seeing if anyone notices. :) Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
