Re: Releases in three months?
Marc Deop Argemí <[email protected]>
| Newsgroups | gmane.comp.kde.events |
|---|---|
| Message-ID | <2518556.0hWDq3tbRr__43839.1529875391$1373577000$gmane$org@i7_2600> |
On Thursday 11 July 2013 18:21:20 Jos Poortvliet wrote: > On Tuesday, July 09, 2013 10:21:18 Nuno Pinheiro wrote: > > A Terça, 9 de Julho de 2013 09:31:42 Jos Poortvliet escreveu: > > > On Tuesday 09 July 2013 07:56:25 Lydia Pintscher wrote: > > > > On Tue, Jul 9, 2013 at 1:38 AM, Àlex Fiestas <[email protected]> wrote: > > > > > Hi there, how is the promo team doing? > > > > > > > > > > Today I've sent a proposal to kde-core-devel about making a release > > > > > every > > > > > 3 months. While developers discuss on that list whether it works for > > > > > them > > > > > or not I'd like to ask you separately your PoV on the matter. > > > > > > > > > > It has been brought by Nuno in the kcd thread that kde-promo won't > > > > > be > > > > > able > > > > > to make a good job if we switch to a 3 month release cycle, so I > > > > > want > > > > > to > > > > > ask you what things (if any) we can do to make it happen. > > > > > > > > > > This is the thread I'm talking about: > > > > > http://lists.kde.org/?l=kde-core-devel&m=137331442528841&w=2 > > > > > > > > > > You can find original reply from Nuno here: > > > > > http://lists.kde.org/?l=kde-core-devel&m=137331586706259&w=2 > > > > > > > > > > So, what can we do to make a 3 month release work? > > > > > > > > Getting the release promotion done for 6-month releases is already > > > > challenging. I don't think 3-month is currently doable without > > > > considerably more help. > > > > > > It depends. Our limiting factor is, and always has been: getting a good > > > idea of what's new. > > > > > > Right now, that is a major pain in the ass. While there is the Features > > > wikipage it rarely is complete (and IF it mentions a feature tells us > > > little about it) and we're forced to go over commit digests and personal > > > blogs to have a more complete picture. > > > > > > If we could improve this somehow, say, developers would commit to having > > > at > > > least significant features mentioned there so that we can rely on it; we > > > can do a lot better, a lot faster. > > > > > > After all, once the features are there, getting screenshots and a pretty > > > text together isn't all that hard. > > > > please dont minimise the mount of work "getting screenshots" minimising > > that lead us to some of the worse RA we hever did. IN fact we have alot, > > and i meen alot to improve in that department. > > > > And repeating what i said in the other thread, reaching a visual concept > > is > > not trivial, in fact its exausting, many here have seen me exasperating > > with this over the last years. > > Well, ideally, we have a screenshot for each major features. If there are > half as many features and half as big an announcement, half as many > screenshots will suffice. [OFFTOPIC] Not that in matters in this discussion but I've always thought that it might be better (for some features at least) to have some sort of video showing some of the new things there are in a new release [/OFFTOPIC] > > Artwork is of course a very different argument - but there is indeed no > reason to do new artwork every 3 months, Aaron's suggestion to concentrate > on a major overhaul once a year seems a good one to me. I agree on this Regards, Marc Deop _______________________________________________ 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.