On Sunday 17 January 2010 04:31:43 pm Dominic Lyons wrote: > Hello, > > > till now I'm not a developers but I'm interested in this project. That's > why I subscribed this mailing list. > > I've planed to take a closer look to basked after my examinations in the > next few weeks. To prepare a bit I've already packaged some of the current > versions and tested them. > I guess basked could be a good project to start with as it's not to > bloated. > > > On Sun, Jan 17, 2010 at 22:47, Dr. Robert Marmorstein < > > rob...@narnia.homeunix.com> wrote: > > 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? > > That's what I've thought before, too. But as I'm currently not a developer > I didn't wanted to complain about that ;-) >
It doesn't matter whether you're a developer or not. Speak up anyways. :) > In my view there are two options we have: One of them if is to release the > 2.0 version as the next one. The other one is to make a 1.9 or something > like that. > I prefer the second option as it implies that maybe some things aren't > working properly yet but it still makes clear that basket is still alive. > (But on the other hand, KDE users normally should know that a Point 0 > release isn't always too solid...) > Right. That's why I wrote the first release that I would do would be a beta, not 2.0 final. > I think 2.0 should have complete feature parity with the last KDE 3 version > and upon that as a sloid ground we can build new features. Maybe we can get > it in KDE 4.5 (although it probably will land in extra gear). > honestly, having had software as part of the KDE release cycle for more than 5 years now, it's a major pain in the ass. It's so easy to roll a release that it's just not worth it, at least from my POV. But that's usually because I end up being able to work on stuff during freezes. > > 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. > > Yes, that's very annoying and the cause why I didn't write bug reports. > Maybe it would be the best to cange to an other bug tracker. For example > Launchpad is far les confusing and has some really good features. > As this is a KDE application bugs.lkde.org may be another option. > > > 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. > > Depending on what it needs I maybe could take a look after it but soonest > in 3 weeks. I'm quite familiar with HTML+CSS. > > > Regards, > Dominic Lyons -- Matt
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
