On Tuesday 23 March 2010 08:30:31 am Dr. Robert Marmorstein wrote: > We should call it 2.0-beta. > > The move to Qt 4/KDE 4 is a major change and we should make that clear by > changing the major version number. We can make it clear that this is not a > production release by appending the "beta" to the end. I think that is > much less confusing than creating a "1.8" version (which sounds like it's > merely a point release of the previous KDE 3 version). > > Robert > > On Tuesday 23 March 2010 3:28:08 am Scott Stubbs wrote: > > On 3/22/10, Piotr Legiecki <piot...@sci.pam.szczecin.pl> wrote: > > > Dr. Robert Marmorstein pisze: > > >> Here's what I have so far. What do you guys think? > > >> > > >> ---------------------------------------------------------------------- > > >> -- -------- > > >> > > >> The BasKet project is proud to announce the release of version 2.0 > > >> beta 2. > > >> > > >> This version serves as a pre-release version for developers and > > >> distributors > > >> and should not be considered suitable for a production system. > > > > > > So finally which version it is? 1.8 or 2.0? Calling it 1.8 and 2.0beta > > > is strange. > > > > Finally it will be 2.0, but currently it is 1.8. I wouldn't call it > > that strange, I think a lot of people do that (including KDE). > > > > For any one using Gentoo I've made an ebuild for this release at > > http://bugs.gentoo.org/show_bug.cgi?id=310827 > > > > And I'll add the other versions to that bug as they are tagged on > > gitorious. > > > > Scott > > > > > P. > > >
It's version 1.80 (the last zero is important!). This versioning scheme has long been a standard in the KDE community for meaning a prerelease for the next major version of software (in this case 2.0). However, I see no problem referring to it as 2.0 Beta 1 in our announcements, P.R., etc. Text looks good. I'll create the announcement from that. :) -- Matt
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Basket-devel mailing list Basket-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/basket-devel
