I've noticed the 'Suggests for improving the SQLite website' e-mail and point number (4) that drh made was the frequent releases of the sqlite library make the library look bad.
I'm quite happy at the release rate and believe as one of the respondents to the thread mentioned that 'release early, release often' is the way to go. But every time a release comes out, I notice that the release contains both features and bug fixes which concerns me since new features could potentially bring about new bugs. A suggestion is to branch sqlite where the third version number (ie. 3.5.x) could be used to identify strictly bug fixes to the library and incrementing the major.minor numbers for major and minor features/improvements. ie. major.minor.patch (3.5.3 could be a bug fix release and 3.6.0 a feature release). This makes for more work since fixes would have to be back-ported to maybe one or two previous releases (as you see fit). This method could be used to release often for those that would like to see bug fixes and improve sqlite's image as a continually improving robust library. At the same time, improvements/features could be introduced at a slower pace without the push to release because of bug-fixes in the same branch of development. I don't have anything in particular about sqlite to complain about. I've been watching the list for about 1/2 a year and like the little library myself. But point #4 prompted me to scratch an itch and suggest an improvement to workflow. filipe ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
