Re: Do we release SC or not?
"Aaron J. Seigo" <[email protected]>
| Newsgroups | gmane.comp.kde.events |
|---|---|
| Message-ID | <[email protected]> |
On Monday, September 6, 2010, Sebastian Kügler wrote: > On Friday, September 03, 2010 19:41:06 Aaron J. Seigo wrote: > > On Thursday, September 2, 2010, Sebastian Kügler wrote: > > > Everything I've heard until now (and that includes the whole "SC" idea) > > > sounds just clumsy and doesn't feel practical. It's doable in > > > paragraphs of text, but it's pretty much impractical for producing > > > headlines. > > > > http://lists.kde.org/?l=kde-promo&m=128043108730686&w=2 > > The idea sounds sound, but in practise to make it work, I find it sounding > silly. Not so much for the x.y.0 releases, but for bugfix updates, it's > almost Microsoft-ish. (Patchday, anyone?) in addition to what Carl said, if we end up releasing more things in tandem it starts to get awkward no matter what we do. imagine making a beta of 4.6 available on the same day we release a 4.5.x, if nothing else to try and get more people aware of the beta cycles; or releasing bug fix updates of koffice in tandem with SC updates. these are more likely to happen as we progress, i think, and we'd be better off having a way of talking about release days in terms of benefit rather than version #s. from a purely marketing POV, version #s are jargon that is almost meaningless for anyone but the well-informed. our headlines should not be touting a version number (that can appear in the body of the text) but _why_ someone should care about this new release. of course, unless our releases are simply uninteresting and only there so that those who have older versions can install a newer one ;) -- 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) iEYEABECAAYFAkyFmlUACgkQ1rcusafx20NafwCfYE2h6eV7ZKNsnfCyWOKpAi05 +iYAn3Ns0vfms+BSTeI4DPAXsRYr7eb+ =uSXU -----END PGP SIGNATURE-----