Re: Handling 4.12
Kevin Krammer <[email protected]>
| Newsgroups | gmane.comp.kde.events |
|---|---|
| Organization | KDE |
| Message-ID | <201308231559.53413.krammer__44015.4104530395$1377266431$gmane$org@kde.org> |
On Friday, 2013-08-23, Jos Poortvliet wrote: > On Friday 23 August 2013 10:45:33 Kevin Krammer wrote: > > On Friday, 2013-08-23, Jos Poortvliet wrote: > > > On Friday 23 August 2013 00:33:27 Kevin Krammer wrote: > > > > On Friday, 2013-08-23, Markus wrote: > > > > > Am Donnerstag, 22. August 2013, 21:21:42 schrieb Torgny Nyblom: > > > > > > When we release KDE SC we release all part of KDE not only the > > > > > > Applications. So calling the release KDE SC is correct. It will > > > > > > change once the Frameworks, Workspaces and Applications have > > > > > > different releases but that is not the case right now. > > > > > > > > > > It's the case with 4.12. > > > > > > > > Really? > > > > I thought it was still a full release, with libraries, workspace and > > > > applications. > > > > > > > > With the only difference that additional to what libraries already > > > > did workspaces will ship no new features. > > > > > > > > Is there a thread on the release team's list that covers this? > > > > > > Yes, but you're correct, that is what will happen. Of course it will > > > have some impact on the releases as there will/should only be features > > > in the applications. But the workspaces should get minor features, at > > > least - so who knows how it ends up. > > > > > > I'm kind'a curious to see how the press picks it up :D > > > > I think we just leave it out, focus on the new things and improvements no > > matter where they are. > > > > Explicitly mentioning the feature development end of workspaces wasn't a > > good idea, it got weirdly interpreted a lot. > > It is an internal decision not really affecting anyone other than our > > developers, we need to learn to keep those bits out of the release > > annoucements. > > If it got mentioned in weird way, that is due to bad communication. Turning > Workspaces into LTS is not a bad message per-se, I would even argue that it > is good. I disagree, this type of information is too "precise". Even without that information they would have had their software update and would have gotten another major one a couple of months later, with bug fix updates in between. We didn't lose anything by not mentioning the maintenance mode for platform, because, again, it remained invisible to the end users. On the other hand including the IMHO unnecessary bits added a lot of room for misinterpretations, which, as we have observed, has had plenty of undesirable effect. > And it is seems sensible to communicate decisions like no longer > working on features in a series to the users and press. If we were to do that on all products maybe. But we are not at that point yet, we have plenty of features and improvements coming in during the next releases. Bascially we were announcing a non-issue. If we were do to that for application we would have a huge section on every release on applications that did not get new features, not adding anything of value, just opening the door for speculations on projects' health. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring _______________________________________________ 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, 190 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iD8DBQBSF2rZnKMhG6pzZJIRAkGrAJ9YUJCPORrSpYRH4p4pv6a/7n6o0gCePpI5 lxXqEF206OmABekNbCVlBuA= =oNly -----END PGP SIGNATURE-----