Instead of just tossing a release out there, why don't we pick a target release date to spread the word a little in advance, give packagers of various distributions a little warning, and polish up the code a little bit?
If we can do that, I will personally make an effort to set some extra time aside for bug hunting this month and to help with preparing release documentation. Before we release, it would be good to resolve the issue of the current bug reporting site. The mantis site is getting so much spam it has become unusuable for me. If we want to continue using mantis, we should at least enable a captcha or something there. Also, what is the current status of the web site? Did anyone actually step up to get it in shape? I saw that Kelvie had made a project for it on gitorious, but it doesn't look like anyone's committed anything to it. KDE SC 4.4 (ick, how I hate the new, unwieldy, acronym) will be released on February 9th. That might be a good date to aim for. On the other hand, if we could release a week earlier (the 2nd or 3rd?) or a week later (Feb. 16th?), we might get a little more attention in the blog world, etc. I wish we could say that we'd gotten rid of all the K3 and Qt3 support classes, but the graphicsview port has been much more diffcult than I'd anticipated (and I've had far less time to spend on basKet due to teaching and other open source commitments). Sorry about that, all. If I have time over spring break this semester, I will try to look at it some more and hopefully get it working. On the upside, I've been doing a LOT of Akonadi work recently and feel pretty comfortable starting to add Akonadi integration to basKet. The trick, as we've discussed before, is in figuring out what information to store. Since we are considering a release, I will hold off making any major changes to my master branch for now and focus on bug killing. After the release, maybe we can work together on both of these. Thanks, Robert On Sunday 17 January 2010 15:15:27 Kelvie Wong wrote: > ---------- Forwarded message ---------- > From: Kelvie Wong <kel...@ieee.org> > Date: 2010/1/17 > Subject: Re: [Basket-devel] Releasing? > To: Matt Rogers <ma...@kde.org> > > 2010/1/17 Matt Rogers <ma...@kde.org>: > > On Saturday 16 January 2010 04:02:32 pm you wrote: > >> 2010/1/16 Matt Rogers <ma...@kde.org>: > >> > Hi, > >> > > >> > A little bit more than a month ago, we discussed doing a release. I'm > >> > assuming that we still want to roll one. I can handle the work for > >> > that, if we're ready for a release. What version number do we want? > >> > :) > >> > > >> > -- > >> > Matt > >> > >> 2.0 seems like the most logical choice. Any objections/other ideas to > >> that? > > > > Nope, 2.0 seems fine to me. Do we want/need anything like release notes, > > dot story, freshmeat submission, etc? > > -- > > Matt > > That would be great if you could make that all happen, of course :) > > As for release notes, this is more or less a direct port, nothing new > was really added. Unless we want to call all of our new bugs > features, that is... > > > -- > Kelvie Wong
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________ Basket-devel mailing list Basket-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/basket-devel
