Re: Defining a Release Target before development cycle starts
"Aaron J. Seigo" <[email protected]>
| Newsgroups | gmane.comp.kde.events |
|---|---|
| Message-ID | <[email protected]> |
On Wednesday, September 15, 2010, Bart Otten wrote: > While reading the proposal "Branding Terms for Releases" [0] it came > to my mind that it could be easier to think of an Release > Announcement-title when there is a Release Target for each of the > components. Maybe we should define and communicate (more, if already > done) our target before the development cycle starts. this would need to happen in consultation with the developers and the various development teams. i don't think it would be possible to drive this from an external group (even with the aura of authority) due to the social structure of KDE. and this is not a bad thing. a few of us have been, admittedly rather slowly, setting up such a thing: http://community.kde.org/Project_Elegance we are nearing the point of being ready to go public with it. feedback is welcome. -- 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 Qt Development Frameworks _______________________________________________ This message is from the kde-promo mailing list. Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkyRAg4ACgkQ1rcusafx20NrPgCcDYR03BlaJto61O144gTgwQHD Ev0AoI3mwncxDbzkZAsOxMMEQCCCmLCg =YkGv -----END PGP SIGNATURE-----