The other question I have is: How often will there be updates to the core vs. updates to the plugins? I'd think the core would be fairly stable, with very few new features (really just hooks for plugins after it's stable, though maybe SSD or some new kind of memory will change that). ie, maybe a new version every 6 months or so?
Plugins would change frequently, though...... -Sheeri On Wed, Feb 25, 2009 at 9:29 AM, Erik Jacobson <[email protected]>wrote: > It may not be that important this early on for tarballs, but one of the > large benefits of using a major.minor version are for end users (even devs). > What gives a non bzr-commiter more useful information (even if you > understand how versioning systems number): > v2.4 -> v3.1 > r2635 -> r2784 > > This of course assumes that whoever is in charge is reasonably sane about > what constitutes a major versus minor release (I'd say feature > changes/additions are major, bug fixes minor at this point in development is > good enough) > This is also with the knowledge that it's relatively easy to see what the > repository version is even on a manually numbered release. > > Another point to make would be that bzr revisions are not indicative of the > size of the change. You can make a dozen small comment changes and bump the > revision way up, or one person can rewrite a whole module in one night with > half the commits (or even just one commit). > > Stewart Smith wrote: > > On Tue, Feb 24, 2009 at 09:08:42PM -0500, Jay Pipes wrote: > > > We're planning on releasing the first tarballs of Drizzle in less than a > week. We'd like to get input on whether our ideas on release number are > hair-brained or not... > > Our plan is to release tarballs and releases that are simply named for > the Bazaar revision, whatever the rev is when we tag up the release. So, > for instance, the release might be just called "r914"... > > > One side of me goes on date based numbers for tarballs: 20090228 etc. > > How this translates into X.Y.Z numbers.... > > MAJOR.MINOR.DATE > > Odd Minor = dev > > even minor = stable. > > i.e. for stable releases: 7.2.1 is a bug fix > > for dev release: 7.1.20090228 is a release. > > > Which would mean it's possible to distinguish between stable and dev > tarballs quite easily (which pure date based versions don't allow). > > > thoughts? > > > > > > -- > Erik Jacobson > Server Administrator > Themis Media ( http://www.themis-media.com/ ) > The Escapist ( http://www.escapistmagazine.com/ ) > ( Vim, Tabs, BSD Braces, Debian, and Perl ) > > > _______________________________________________ > Mailing list: > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > More help : https://help.launchpad.net/ListHelp > > -- - Sheeri K. Cabral http://tinyurl.com/mysqlbook will take you to the Amazon.com page for my upcoming book, "MySQL Administrator's Bible".
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
