[Kde-imaging] releasing extragear

[Aaron J. Seigo]

On Tuesday 09 October 2007, Angelo Naselli wrote:
> I should have missed something I thought extragears should have per
> application releases and not following the same rules as kde-core & co.
> applications. I'm really confused

so here's the deal:

we'd like to allow developers in extragear opt in to having time coordinated 
releases with the core kde modules (dev platform + workspace + core apps). 
the apps that opt in will have their last stable release included as tarballs 
alongside the main kde releases.

why?

- to allow people to work on apps outside of the modules without being 
required to do their own release maintenance
- to give greater exposure for apps in extragear (outside of a few apps like 
amarok, most people pay orders of magnitude more attention to kde releases 
than extragear app releases)
- to emphasize the variety of apps written using the KDE dev platform
- to give extragear apps access to packaging on platforms they might otherwise 
not get (e.g. BSD, Solaris, MacOS, Win32...)

this does not mean:

- that the apps have to coordinate their release cycle with the KDE dev 
platform releases (we simply ship the last stable release of the extragear 
app, whenever that was ... the maintainers get to pick what that means by use 
of a tag)
- that an app in extragear MUST be released in this fashion (it's opt in)
- that an app in extragear can not do its own releases as well (in fact, that 
is encouraged for a faster devel cycle that more naturally fits your needs)

make sense?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20071009/d16c6fb4/attachment.pgp