Even if we release this as a "beta" (basket-1.9 or whatever), I'd prefer to have some time to put our best foot forward. Even if it's just a few weeks, it would be nice to have a little time to prepare. Coming up with a specific deadline would help ensure that we really do get something out the door, though (and it would greatly increase my motivation to get bugs fixed...)
> > 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. I have to agree. But isn't it true that extragear apps are not tied to the KDE release cycle? I may be wrong, but I don't think freezes apply to extragear. The extragear web page says: "All applications in the extragear modules can be released independently by their own maintainers or in the KDE release cycle in a special per-category tarball made by Extragear's current maintainer. The current proposition is have at least one package per-category which compiles against current KDE release and have the last stable or bugfix branch releases defined by apps maintainers." At any rate, we may not want to go this route at all. But if we do, extragear looks nice. The advantage of being part of extragear is that we would have a lot more visibility to the KDE community. Let's try to get a release out the door, get some more features implemented, and see where we want to go from there. I think Matt is right that we'd agreed to move back to bugs.kde.org. However, the mantis is still online, which could confuse users. We need to either get Lynoure to take it down or make it very clear that users are supposed to send bugs to the other site. --Robert
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
