Re: Defining a Release Target before development cycle starts
"Aaron J. Seigo" <[email protected]>
| Newsgroups | gmane.comp.kde.events |
|---|---|
| Message-ID | <201009151430.28400.aseigo__5633.53081602163$1284586293$gmane$org@kde.org> |
On Wednesday, September 15, 2010, Carl Symons wrote: > It appears that Project Elegance can provide possible release high > points. i hope so; at first it will start small, with easily achievable things so that we can start with a near guarantee of initial success, allowing us to build the mechanics as well as trust in relative safety. > And while there may be other aspects of a release that are > more newsworthy at the time, featuring Project Elegance outcomes will > support its long term audacity and maintain its momentum. that is exactly my hope as well ... > The Project Elegance spirit goes beyond "improving specific aspects of > the software". Why not kde-promo too? indeed, why not :) -- 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) iEYEABECAAYFAkyROvQACgkQ1rcusafx20MPFQCeNasAQPqxYYOEhgx1hPF7z7j1 G/kAoIt82cvKKGPcJh5GDDY4+PWzlr3o =zoOI -----END PGP SIGNATURE-----