Gianluca Montecchi <[email protected]> writes: > Probably a good idea is to set what we want to have in a first release > and then go on to make it happen, something like a feature release. > > My list is: > - a stable core > - a web interface (cfbe)
My list, for a first release whatever its version string, is: * a stable core * confidence that bug reports against that version will for some significant period of time be met with patch releases and not “just use a later revision and hopefully it will work” I don't care whether the first version is “0.7” or “0.1” or “0.0.001” or whatever. Name it however you want to indicate how incomplete you consider it to be. Note that the second criterion is not made based on any specific events in the history of Bugs Everywhere, but rather general experience with not-many-versions-released projects. In other words, attempting to stave off an easily anticipated problem common to software projects everywhere. -- \ “Ubi dubium, ibi libertas.” (“Where there is doubt, there is | `\ freedom.”) | _o__) | Ben Finney _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
