Re: KF5 beta3
On Sunday 01 June 2014 20:20:45 David Faure wrote: > As planned, here's KF5 beta3, aka 4.100.0. > > * New this month: > - kfileaudiopreview doesn't exist anymore > - the attached tags.git file indicates the tag to use for distros using git > instead of tarballs [note the exception on the last line...] > > * Public release date: June 4 (unless someone shouts otherwise) A text has been written, I'll try to push the announcement tomorrow morning. Maybe, REAL maybe, I can do it tonight, but no promise :( signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Frameworks 5 Beta 2?
On Wednesday 21 May 2014 09:30:18 Kevin Ottens wrote: > On Wednesday 21 May 2014 09:16:23 David Faure wrote: > > On Tuesday 20 May 2014 23:07:21 Kevin Ottens wrote: > > > On Tuesday 20 May 2014 10:58:01 Albert Astals Cid wrote: > > > > On Tuesday 20 May 2014 11:30:54 Kevin Ottens wrote: > > > > > On Tuesday 20 May 2014 10:20:35 Jos Poortvliet wrote: > > > > > > Meanwhile, I notice that the release date of May 4th for B2 wasn't > > > > > > attained, or did it just go without a announcement and dot story? > > > > > > > > > > It was published, but indeed no announcement and dot story. > > > > > > > > Why did this happen? > > > > > > I think we miss a hand-over from the "tarballs are ready" to "kde-promo > > > can > > > communicate". > > > David, something to add in your release check list? At the end we should > > > notify promo. > > > > That's already in the check list (release-tools/PACKAGING_HOWTO links to > > "RELEASE_PROMOTION"). > > > > And on May 5, I emailed dot-edit...@kde.org and Jos to notify them about > > the beta2 release. > > OK, then it properly happened. Jos any idea where it got lost then? Should > kde-promo added to the forums we should notify? I must've been too busy or somehow else have missed that mail, I didn't see it. Even wondered at a later point, what happened (see my mail). Sorry. I think mailing kde-promo would help getting more eyes on the ball... Hugs, /J > Regards. signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Frameworks 5 Beta 2?
Meanwhile, I notice that the release date of May 4th for B2 wasn't attained, or did it just go without a announcement and dot story? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Fwd: KDE Frameworks Release Cycle
On Tuesday 20 May 2014 19:07:41 Ben Cooksley wrote: > On Tue, May 20, 2014 at 6:04 PM, Kevin Ottens wrote: > > Now, I think we'll have to agree to disagree on something. You believe > > there's some rule written in stone somewhere which will make the > > "everyone will pile up backports only" the new status quo forever, I say > > let's try and find out. > In the meantime, everyone but the developers will suffer. Yes, and saying no to every proposal won't change that. I believe that the only advantage of the current situation (slow release cycle with a period of 'bugfixes' that go untested) seems to be that it is a known evil: we're lying about them being stable bugfix releases but the release numbering and lack of new dependencies makes the distro management believe the story. Perhaps, as proposed, going for a cycle where only the January and July releases introduce a major version number and mandatory new dependencies while the other releases are minor-numbered (but otherwise unconstrained in features as long as new dependencies are optional) means we improve on the current situation (minor/bugfix releases don't get tested very well) while also loosing a little (there are new, but optional, dependencies and new features). The packagers can simply go to distro management and call this bugfix releases, as they will (arguably) be more stable than what they currently accept as 'bugfix releases'. And the developers get what they want, too. So after 5.0, 5.0.1 is released with minor features and bugfixes (but no mandatory changes in dependencies at all); which continues until January, when 5.1 comes out, with new dependencies and changes. Consider the potential new API's and components introduced after 5.0 as 'experimental' until January. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Fwd: KDE Frameworks Release Cycle
On Wednesday 30 April 2014 15:36:10 Àlex Fiestas wrote: > On Wednesday 30 April 2014 08:16:48 Scott Kitterman wrote: > > I get what you're asking for. > > > > What I'm trying to make clear is you aren't going to get it. > > Well, I'd say we try. Isn't there a chance Frameworks 5 WILL be quite relevant for Ubuntu? It would be smart of them to leverage these libraries for the Qt applications and phone stuff they are building... I understand the KDE Applications and Plasma are not that interesting for them, perhaps, but for sure the libraries should be. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-packager] Re: KF5 Beta 1
On Monday 31 March 2014 21:05:25 Martin Graesslin wrote: > On Monday 31 March 2014 19:41:28 Jos Poortvliet wrote: > > On Monday 31 March 2014 17:23:56 Jonathan Riddell wrote: > > > On Sun, Mar 30, 2014 at 12:55:55PM +0200, šumski wrote: > > > > > Good question, I never know how much time I should leave for > > > > > packagers > > > > > and > > > > > dot editors. > > > > > Tuesday OK? Or too short? Tell me :) > > > > > > > > Sounds good. 3, 4 days should be enough. (i just need to push the > > > > publish > > > > button so it could be today even ;-) > > > > WRT Tuesday - i know last time there where some concerns about two > > > > releases on the same day - this time it would overlap with 4.12.4 > > > > > > It needs to be released before Plasma Alpha gets released, and Plasma > > > Alpha is due tomorrow to be on schedule, although I don't mind > > > delaying it a day if necessary. > > > > Ideally, we'd delay Plasma Alpha one day to put it on Wednesday. April > > 1st > > is awkward :D > > Why? Just because some people tend to make a fool out of themselves > tomorrow, it's not a reason to not provide serious news. It's rather > obvious that our beta release of frameworks is not an April fool. > > > We do have a dot rule of only one release per day and I'm only aware of > > these two things atm, if there is more, let me know... > > > > Oh, we're talking KF5 Beta1 here. Hmmm. Though one... Pff, can we try > > that > > today, or should we just move it all another day, or? > > > > After thinking (for some seconds, I'm on adrenaline today) I suggest we > > put KF5B1 and PlasmaAlpha in one article on the dot and two > > announcements on KDE.org. > > And we are back to having a "KDE" release ;-) Let's make it on two > different days to make it obvious. Good point. Ok, talked about this with Sebas. We suggest: we do the 4.12.4 asap in the morning on April 1st and the frameworks5 Beta 1 later that day. Then, Wednesday we do Plasma Next Alpha which then gets proper attention. Plasma Next Alpha dot story is pretty much done (can use review), the Frameworks5 Beta can use a review, too. If any of you has time, please go over them: https://notes.kde.org/p/Frameworks5Beta https://notes.kde.org/p/plasma-next-alpha /J > Cheers > Martin signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-packager] Re: KF5 Beta 1
On Monday 31 March 2014 17:23:56 Jonathan Riddell wrote: > On Sun, Mar 30, 2014 at 12:55:55PM +0200, šumski wrote: > > > Good question, I never know how much time I should leave for packagers > > > and > > > dot editors. > > > Tuesday OK? Or too short? Tell me :) > > > > Sounds good. 3, 4 days should be enough. (i just need to push the publish > > button so it could be today even ;-) > > WRT Tuesday - i know last time there where some concerns about two > > releases on the same day - this time it would overlap with 4.12.4 > > It needs to be released before Plasma Alpha gets released, and Plasma > Alpha is due tomorrow to be on schedule, although I don't mind > delaying it a day if necessary. Ideally, we'd delay Plasma Alpha one day to put it on Wednesday. April 1st is awkward :D We do have a dot rule of only one release per day and I'm only aware of these two things atm, if there is more, let me know... Oh, we're talking KF5 Beta1 here. Hmmm. Though one... Pff, can we try that today, or should we just move it all another day, or? After thinking (for some seconds, I'm on adrenaline today) I suggest we put KF5B1 and PlasmaAlpha in one article on the dot and two announcements on KDE.org. The alternative is to do KF5B1 on Wednesday and PlasmaAlpha on Thursday. Tell me what you like most. /J > Also anyone got this test error in kcrash on i386 only? > http://paste.kde.org/pccpojfwd > > Jonathan signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-promo] kdelibs frozen but... baloo...
On Tuesday 25 March 2014 14:34:30 Aaron J. Seigo wrote: > On Tuesday, March 25, 2014 14:20:40 Jos Poortvliet wrote: > > Reviewing the text as it should be for the announcement of 4.13, I notice > > that it is quite hard to claim that KDELibs hasn't changed as it is > > frozen > > but 'by the way' we've made major changes to it ;-) > > tl;dr -> kdelibs itself is frozen, but there is a new support library > offered with 4.13 for the semantic search (baloo). this is similar to > adding a new library to kdesupport ... > > slightly longer: > > kdelibs itself is frozen. baloo lives in its own git repos, under the > kdelibs namespace on projects.kde.org, see: > > https://projects.kde.org/projects/kde/kdelibs/baloo > > baloo is an additional library separate from kdelibs and the nepomuk stuff > is also still there in their own repositories under the kdelibs namespace > on projects.kde.org. > > so nothing has been 'tampered' with, though we've added a new library > alongside kdelibs. applications that build against / use nepomuk continue > to do so, and applications that port to baloo's API can elect to do so as > of 4.13. Ok, I can work with that. Thanks, Aaron! signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
kdelibs frozen but... baloo...
Heya, Reviewing the text as it should be for the announcement of 4.13, I notice that it is quite hard to claim that KDELibs hasn't changed as it is frozen but 'by the way' we've made major changes to it ;-) Is "KDE Semantic Search" part of KDE Libs? If so, I'll say something like "KDELibs is frozen but an exception is...". If not, I'll talk it up as part of KDE Applications. You're the experts, I just tell the story... So tell me what to say :D /J signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 4.12.2 and Frameworks 5 - WAS - Re: Calligra 2.8 out!
On Sun, Mar 9, 2014 at 11:28 PM, David Faure wrote: > On Sunday 09 March 2014 23:06:18 Albert Astals Cid wrote: >> El Divendres, 7 de març de 2014, a les 11:10:13, Jos Poortvliet va escriure: >> > On Thursday 06 March 2014 19:17:10 Albert Astals Cid wrote: >> > > El Dijous, 6 de març de 2014, a les 10:59:28, Jos Poortvliet va > escriure: >> > > > Heya, >> > > > >> > > > On a related note, 4.12.2 and Frameworks 5 Alpha went out on the same >> > > > day. >> > > > How about we try to space things out the next time, one day in between >> > > > or >> > > > such? Is that doable? >> > > >> > > Have you checked the schedules to see if they collide again? >> > >> > There are a few collisions coming, yes - like April 1st when both >> > Frameworks and SC 4.12.4 do a release again. I would suggest that one of >> > the two slips one day... >> >> Since Frameworks is a bit less "stable" and may actually already slip a bit >> by itself (i think the last one did slip a few days). >> >> David do you mind doing Frameworks on April 2nd? > > Actually, I'll be in Nuremberg that week, so I'd rather release on > Friday 28 March or Saturday 05 April. Well, I mean the day where I make the > packages. The public release can be later of course. Looks like neither of you cares when exactly the dot story goes out so I'd say - you make the schedules and if there's an overlap the dot editors fix that by delaying one of the two by one day. We've done it before and we can do it again... Cheers, J > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Working on KDE, in particular KDE Frameworks 5 > ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: 4.12.2 and Frameworks 5 - WAS - Re: Calligra 2.8 out!
On Thursday 06 March 2014 19:17:10 Albert Astals Cid wrote: > El Dijous, 6 de març de 2014, a les 10:59:28, Jos Poortvliet va escriure: > > Heya, > > > > On a related note, 4.12.2 and Frameworks 5 Alpha went out on the same > > day. > > How about we try to space things out the next time, one day in between or > > such? Is that doable? > > Have you checked the schedules to see if they collide again? There are a few collisions coming, yes - like April 1st when both Frameworks and SC 4.12.4 do a release again. I would suggest that one of the two slips one day... /J > Cheers, > Albert > > > Hugs, > > Jos > > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Plasma Next alpha release engineering bits
On Thursday 06 March 2014 15:18:45 Sebastian Kügler wrote: > On Thursday, March 06, 2014 15:12:32 Jos Poortvliet wrote: > > On Thursday 06 March 2014 11:32:03 Sebastian Kügler wrote: > > > On Thursday, March 06, 2014 10:49:21 Jos Poortvliet wrote: > > > > On Wednesday 05 March 2014 13:10:12 Sebastian Kügler wrote: > > > > > > > > > > > > You want the same as for the Frameworks alpha's? As in, very plain > > > > and > > > > simple as we did the 'noise' in the earlier Tech Preview article: > > > > http://dot.kde.org/2014/03/04/kde-frameworks-5-alpha-two-out > > > > > > > > > > > > > > > > If so, I'd be happy to take care of it. > > > > > > That would totally rock. I can help with nice material to go along with > > > it, > > > and the text of course. > > > > If you braindump to me the major changes since the tech preview and have > > a > > picture or two, I'll do the rest. > > > > What's the date? > > Tagging next Thursday, hopefully pretty quickly then the Alpha release (as > packages pass smoke testing). I'll be travelling starting on Thursday, so > how about we chat about it on, say, Monday, if that fits yourschedule? Yeap, ping me. Just send you a mail with another excuse to talk anyhow ;-) signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Plasma Next alpha release engineering bits
On Thursday 06 March 2014 11:32:03 Sebastian Kügler wrote: > On Thursday, March 06, 2014 10:49:21 Jos Poortvliet wrote: > > On Wednesday 05 March 2014 13:10:12 Sebastian Kügler wrote: > > > As we're planning to release the first alpha of Plasma Next next week, > > > I'd > > > like to go over some details that need discussing. > > > > > > - promo preparations > > > > You want the same as for the Frameworks alpha's? As in, very plain and > > simple as we did the 'noise' in the earlier Tech Preview article: > > http://dot.kde.org/2014/03/04/kde-frameworks-5-alpha-two-out > > > > If so, I'd be happy to take care of it. > > That would totally rock. I can help with nice material to go along with it, > and the text of course. If you braindump to me the major changes since the tech preview and have a picture or two, I'll do the rest. What's the date? > Cheers, signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Calligra 2.8 out!
Heya, I noticed that the Dot didn't say anything about the Calligra 2.8 release - and having at least a short summary would be nice, right? So - I put that together quickly: http://dot.kde.org/2014/03/06/calligra-28-released Inge, next time - just tell us a day or two in advance and we can do this on the same day... It takes like 2 minutes anyway, I just took text from the awesome article you wrote for the original announcement: http://www.calligra.org/news/calligra-2-8-released/ On a related note, 4.12.2 and Frameworks 5 Alpha went out on the same day. How about we try to space things out the next time, one day in between or such? Is that doable? Hugs, Jos signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Plasma Next alpha release engineering bits
On Wednesday 05 March 2014 13:10:12 Sebastian Kügler wrote: > Hi, > > As we're planning to release the first alpha of Plasma Next next week, I'd > like to go over some details that need discussing. > > - promo preparations You want the same as for the Frameworks alpha's? As in, very plain and simple as we did the 'noise' in the earlier Tech Preview article: http://dot.kde.org/2014/03/04/kde-frameworks-5-alpha-two-out If so, I'd be happy to take care of it. /J > - tagging / tarballing: can happen anytime on Thursday next week > - smoke-testing of packages > - rolling out packages on Monday, or sooner depending on testing? > > We'll need someone to roll the tarballs and put them on the download site. > Who is willing to help here? > > Affected repositories: > > - plasma-framework > - kde-workspace > - kde-runtime > - kwin-compositing-kcm > > Am I missing something, perhaps the wallpapers? We have some bits in kde- > baseapps that could be useful, should we include that as well (as sort of > limited tarball)? > > This means: don't make changes to frameworks other than plasma-framework > that are required, we'll not be able to include them in the Alpha. > > It also means that if you have invasive changes, get them in NOW, we need > some time to stabilize them. > > Cheers, signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [dot] KF5 alpha 1
Thanks, all. Putting it online now, should be done soon. On Mon, Mar 3, 2014 at 8:01 AM, Martin Gräßlin wrote: > On Sunday 02 March 2014 19:55:46 Jos Poortvliet wrote: >> On Sat, Mar 1, 2014 at 10:35 AM, David Faure wrote: >> > On Friday 14 February 2014 17:10:15 Jos Poortvliet wrote: >> >> On Tuesday 11 February 2014 23:18:51 David Faure wrote: >> >> > KF5 alpha 1 is out >> >> > >> >> > (I changed permissions on the dir and pushed the tags into git). >> >> > >> >> > If anyone wants to write a release announcement, now is the time :) >> >> >> >> Back from holiday, writing something. Will give it today as release date >> >> and push it out asap. Too bad nobody else found time to pick it up... >> >> >> >> Some info on what's in there would be appreciated. Will ping on IRC. >> > >> > New month, new KF5 release: I'm about to package up KF5 beta1 now. >> > >> > Official release on Tuesday, or do packagers and/or dot editors want more >> > time? >> >> Alpha two? Should not be a huge deal, let's just get it out on >> Tuesday. Any updates on what is new or changed would be appreciated, >> something that can replace this part from alpha 1: >> -- >> Improvements in this release include the addition of .pri files which >> make it easy for qmake based projects to use individual frameworks and >> two new frameworks: kactivities and plasma-framework. There has also >> been significant progress in getting frameworks to work on the >> Microsoft Windows platform. >> -- > > You could mention that our frameworks got fixed to run on Wayland [1]. Feel > free to take one of my screenshots for it. Relevant blog post: > http://blog.martin-graesslin.com/blog/2014/02/running-frameworks-powered-applications-on-wayland/ > > Cheers > > [1] kinit, kdesu and khtml are not yet fixed > Martin ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [dot] KF5 alpha 1
On Sat, Mar 1, 2014 at 10:35 AM, David Faure wrote: > On Friday 14 February 2014 17:10:15 Jos Poortvliet wrote: >> On Tuesday 11 February 2014 23:18:51 David Faure wrote: >> > KF5 alpha 1 is out >> > >> > (I changed permissions on the dir and pushed the tags into git). >> > >> > If anyone wants to write a release announcement, now is the time :) >> >> Back from holiday, writing something. Will give it today as release date and >> push it out asap. Too bad nobody else found time to pick it up... >> >> Some info on what's in there would be appreciated. Will ping on IRC. > > New month, new KF5 release: I'm about to package up KF5 beta1 now. > > Official release on Tuesday, or do packagers and/or dot editors want more > time? Alpha two? Should not be a huge deal, let's just get it out on Tuesday. Any updates on what is new or changed would be appreciated, something that can replace this part from alpha 1: -- Improvements in this release include the addition of .pri files which make it easy for qmake based projects to use individual frameworks and two new frameworks: kactivities and plasma-framework. There has also been significant progress in getting frameworks to work on the Microsoft Windows platform. -- I will copy-paste the rest. And hopefully svn won't have to be cleaned up after me this time \o/ /J > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Working on KDE, in particular KDE Frameworks 5 > ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [dot] KF5 alpha 1
On Tuesday 11 February 2014 23:18:51 David Faure wrote: > KF5 alpha 1 is out > > (I changed permissions on the dir and pushed the tags into git). > > If anyone wants to write a release announcement, now is the time :) Back from holiday, writing something. Will give it today as release date and push it out asap. Too bad nobody else found time to pick it up... Some info on what's in there would be appreciated. Will ping on IRC. /J > Have fun. signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release Cycle
On Thursday 29 August 2013 10:00:54 Martin Graesslin wrote: > On Wednesday 28 August 2013 22:52:17 Jos Poortvliet wrote: > > On Friday 23 August 2013 22:10:32 Albert Astals Cid wrote: > > > El Divendres, 23 d'agost de 2013, a les 08:49:19, Jos Poortvliet va > > > > escriure: > > > > On Thursday 22 August 2013 23:35:49 Albert Astals Cid wrote: > > > > > El Dijous, 22 d'agost de 2013, a les 08:07:22, Jos Poortvliet va > > > > escriure: > > > > > > On Tuesday 20 August 2013 22:40:29 Mark wrote: > > > > > > > On Tue, Aug 20, 2013 at 8:44 PM, Albert Astals Cid > > > > > > > > > > > > > > > wrote: > > > > > > > > El Dimarts, 20 d'agost de 2013, a les 01:54:48, Albert Astals > > > > > > > > Cid > > > > > > > > va > > > > > > > > > > > > escriure: > > > > > > > >> El Dimarts, 20 d'agost de 2013, a les 01:17:18, Aaron J. > > > > > > > >> Seigo > > > > > > > >> va > > > > > > > > > > > > escriure: > > > > > > > >> > On Tuesday, August 20, 2013 00:24:53 Albert Astals Cid wrote: > > > > > > > >> > > El Dilluns, 19 d'agost de 2013, a les 22:18:26, Aaron J. > > > > > > > >> > > Seigo > > > > > > > >> > > va > > > > > > > >> > > > > > > > >> escriure: > > > > > > > >> > > > On Monday, August 19, 2013 22:14:26 Albert Astals Cid > > > > wrote: > > > > > > > >> > > > > There will be a 4.13? Most probably. > > > > > > > >> > > > > Will it be in 2014? For sure > > > > > > > >> > > > > Which month? Noone knows, you can probably guess > > > > > > > >> > > > > it'll > > > > be > > > > > > > > > >> > > > > between > > > > > > > >> > > > > Q2 > > > > > > > >> > > > > and > > > > > > > >> > > > > Q3 > > > > > > > >> > > > > since Q1 would mean <= 3 months of development and > > Q4 > > > > > > > > >> > > > > would > > > > > > > >> > > > > mean > > > > > > > >> > > > > > > > > > > > >> > > > > >= > > > > > > > >> > > > > > > > > > > > >> > > > > 10 > > > > > > > >> > > > > months. > > > > > > > >> > > > > > > > > > > >> > > > unless we change the development cycle, which has not > > yet > > > > > > > > >> > > > been > > > > > > > >> > > > done, > > > > > > > >> > > > which > > > > > > > >> > > > month will 4.13 be in? > > > > > > > >> > > > > > > > > > >> > > Are you disagreeing with the 4.12 schedule? > > > > > > > >> > > > > > > > > >> > No; however, on > > http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule > > > it > > > > > > > > > >> > says > > > > > > > >> > “THIS IS NOT OFFICIAL YET” four times right at the top. I > > > > > > > >> > was > > > > > > > >> > under > > > > > > > >> > the > > > > > > > >> > impression that it was still being discussed and wasn’t ... > > > > > > > >> > you > > > > > > > >> > know > > > > > > > >> > .. > > > > > > > >> > official yet. > > > > > > > >> > > > > > > > >> It will be official when i get tired of waiting for people to > > > > > > > >> oppose > > > > > > > >> to > > > > > > > >> it. > >
Re: Release Cycle
On Thursday 29 August 2013 10:12:41 Albert Astals Cid wrote: > El Dijous, 29 d'agost de 2013, a les 10:00:54, Martin Graesslin va escriure: > > On Wednesday 28 August 2013 22:52:17 Jos Poortvliet wrote: > > > On Friday 23 August 2013 22:10:32 Albert Astals Cid wrote: > > > > El Divendres, 23 d'agost de 2013, a les 08:49:19, Jos Poortvliet va > > > > > > escriure: > > > > > On Thursday 22 August 2013 23:35:49 Albert Astals Cid wrote: > > > > > > El Dijous, 22 d'agost de 2013, a les 08:07:22, Jos Poortvliet va > > > > > > escriure: > > > > > > > On Tuesday 20 August 2013 22:40:29 Mark wrote: > > > > > > > > On Tue, Aug 20, 2013 at 8:44 PM, Albert Astals Cid > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > El Dimarts, 20 d'agost de 2013, a les 01:54:48, Albert > > > > > > > > > Astals > > > > > > > > > Cid > > > > > > > > > va > > > > > > > > > > > > > > escriure: > > > > > > > > >> El Dimarts, 20 d'agost de 2013, a les 01:17:18, Aaron J. > > > > > > > > >> Seigo > > > > > > > > >> va > > > > > > > > > > > > > > escriure: > > > > > > > > >> > On Tuesday, August 20, 2013 00:24:53 Albert Astals Cid > > wrote: > > > > > > > > >> > > El Dilluns, 19 d'agost de 2013, a les 22:18:26, Aaron > > > > > > > > >> > > J. > > > > > > > > >> > > Seigo > > > > > > > > >> > > va > > > > > > > > >> > > > > > > > > >> escriure: > > > > > > > > >> > > > On Monday, August 19, 2013 22:14:26 Albert Astals Cid > > > > > > wrote: > > > > > > > > >> > > > > There will be a 4.13? Most probably. > > > > > > > > >> > > > > Will it be in 2014? For sure > > > > > > > > >> > > > > Which month? Noone knows, you can probably guess > > > > > > > > >> > > > > it'll > > > > > > be > > > > > > > > > > > >> > > > > between > > > > > > > > >> > > > > Q2 > > > > > > > > >> > > > > and > > > > > > > > >> > > > > Q3 > > > > > > > > >> > > > > since Q1 would mean <= 3 months of development and > > > > Q4 > > > > > > > > > > >> > > > > would > > > > > > > > >> > > > > mean > > > > > > > > >> > > > > > > > > > > > > >> > > > > >= > > > > > > > > >> > > > > > > > > > > > > >> > > > > 10 > > > > > > > > >> > > > > months. > > > > > > > > >> > > > > > > > > > > > >> > > > unless we change the development cycle, which has not > > > > yet > > > > > > > > > > >> > > > been > > > > > > > > >> > > > done, > > > > > > > > >> > > > which > > > > > > > > >> > > > month will 4.13 be in? > > > > > > > > >> > > > > > > > > > > >> > > Are you disagreeing with the 4.12 schedule? > > > > > > > > >> > > > > > > > > > >> > No; however, on > > > > http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule > > > > > it > > > > > > > > > > > >> > says > > > > > > > > >> > “THIS IS NOT OFFICIAL YET” four times right at the top. I > > > > > > > > >> > was > > > > > > > > >> > under > > > > > > > > >> > the > > > > > > > >
Re: Release Cycle
On Thursday 29 August 2013 00:09:19 Albert Astals Cid wrote: > El Dimecres, 28 d'agost de 2013, a les 22:52:17, Jos Poortvliet va escriure: > > On Friday 23 August 2013 22:10:32 Albert Astals Cid wrote: > > > El Divendres, 23 d'agost de 2013, a les 08:49:19, Jos Poortvliet va > > > > escriure: > > > > On Thursday 22 August 2013 23:35:49 Albert Astals Cid wrote: > > > > > El Dijous, 22 d'agost de 2013, a les 08:07:22, Jos Poortvliet va > > > > escriure: > > > > > > On Tuesday 20 August 2013 22:40:29 Mark wrote: > > > > > > > On Tue, Aug 20, 2013 at 8:44 PM, Albert Astals Cid > > > > > > > > > > > > > > > wrote: > > > > > > > > El Dimarts, 20 d'agost de 2013, a les 01:54:48, Albert Astals > > > > > > > > Cid > > > > > > > > va > > > > > > > > > > > > escriure: > > > > > > > >> El Dimarts, 20 d'agost de 2013, a les 01:17:18, Aaron J. > > > > > > > >> Seigo > > > > > > > >> va > > > > > > > > > > > > escriure: > > > > > > > >> > On Tuesday, August 20, 2013 00:24:53 Albert Astals Cid wrote: > > > > > > > >> > > El Dilluns, 19 d'agost de 2013, a les 22:18:26, Aaron J. > > > > > > > >> > > Seigo > > > > > > > >> > > va > > > > > > > >> > > > > > > > >> escriure: > > > > > > > >> > > > On Monday, August 19, 2013 22:14:26 Albert Astals Cid > > > > wrote: > > > > > > > >> > > > > There will be a 4.13? Most probably. > > > > > > > >> > > > > Will it be in 2014? For sure > > > > > > > >> > > > > Which month? Noone knows, you can probably guess > > > > > > > >> > > > > it'll > > > > be > > > > > > > > > >> > > > > between > > > > > > > >> > > > > Q2 > > > > > > > >> > > > > and > > > > > > > >> > > > > Q3 > > > > > > > >> > > > > since Q1 would mean <= 3 months of development and Q4 > > > > > > > >> > > > > would > > > > > > > >> > > > > mean > > > > > > > >> > > > > > > > > > > > >> > > > > >= > > > > > > > >> > > > > > > > > > > > >> > > > > 10 > > > > > > > >> > > > > months. > > > > > > > >> > > > > > > > > > > >> > > > unless we change the development cycle, which has not > > > > > > > >> > > > yet > > > > > > > >> > > > been > > > > > > > >> > > > done, > > > > > > > >> > > > which > > > > > > > >> > > > month will 4.13 be in? > > > > > > > >> > > > > > > > > > >> > > Are you disagreeing with the 4.12 schedule? > > > > > > > >> > > > > > > > > >> > No; however, on > > > > > > > >> > http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedul > > > > > > > >> > e > > > > it > > > > > > > > > >> > says > > > > > > > >> > “THIS IS NOT OFFICIAL YET” four times right at the top. I > > > > > > > >> > was > > > > > > > >> > under > > > > > > > >> > the > > > > > > > >> > impression that it was still being discussed and wasn’t ... > > > > > > > >> > you > > > > > > > >> > know > > > > > > > >> > .. > > > > > > > >> > official yet. > > > > > > > >> > > > > > > > >> It will be official when i get tired of waiting for people to >
Re: Release Cycle
On Friday 23 August 2013 22:10:32 Albert Astals Cid wrote: > El Divendres, 23 d'agost de 2013, a les 08:49:19, Jos Poortvliet va escriure: > > On Thursday 22 August 2013 23:35:49 Albert Astals Cid wrote: > > > El Dijous, 22 d'agost de 2013, a les 08:07:22, Jos Poortvliet va escriure: > > > > On Tuesday 20 August 2013 22:40:29 Mark wrote: > > > > > On Tue, Aug 20, 2013 at 8:44 PM, Albert Astals Cid > > > > wrote: > > > > > > El Dimarts, 20 d'agost de 2013, a les 01:54:48, Albert Astals Cid > > > > > > va > > > > > > > > escriure: > > > > > >> El Dimarts, 20 d'agost de 2013, a les 01:17:18, Aaron J. Seigo va > > > > > > > > escriure: > > > > > >> > On Tuesday, August 20, 2013 00:24:53 Albert Astals Cid wrote: > > > > > >> > > El Dilluns, 19 d'agost de 2013, a les 22:18:26, Aaron J. > > > > > >> > > Seigo > > > > > >> > > va > > > > > >> > > > > > >> escriure: > > > > > >> > > > On Monday, August 19, 2013 22:14:26 Albert Astals Cid wrote: > > > > > >> > > > > There will be a 4.13? Most probably. > > > > > >> > > > > Will it be in 2014? For sure > > > > > >> > > > > Which month? Noone knows, you can probably guess it'll be > > > > > >> > > > > between > > > > > >> > > > > Q2 > > > > > >> > > > > and > > > > > >> > > > > Q3 > > > > > >> > > > > since Q1 would mean <= 3 months of development and Q4 > > > > > >> > > > > would > > > > > >> > > > > mean > > > > > >> > > > > > > > > > >> > > > > >= > > > > > >> > > > > > > > > > >> > > > > 10 > > > > > >> > > > > months. > > > > > >> > > > > > > > > >> > > > unless we change the development cycle, which has not yet > > > > > >> > > > been > > > > > >> > > > done, > > > > > >> > > > which > > > > > >> > > > month will 4.13 be in? > > > > > >> > > > > > > > >> > > Are you disagreeing with the 4.12 schedule? > > > > > >> > > > > > > >> > No; however, on > > > > > >> > http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule it > > > > > >> > says > > > > > >> > “THIS IS NOT OFFICIAL YET” four times right at the top. I was > > > > > >> > under > > > > > >> > the > > > > > >> > impression that it was still being discussed and wasn’t ... you > > > > > >> > know > > > > > >> > .. > > > > > >> > official yet. > > > > > >> > > > > > >> It will be official when i get tired of waiting for people to > > > > > >> oppose > > > > > >> to > > > > > >> it. > > > > > >> If it makes you happier, I can declare it official now. > > > > > > > > > > > > There you go. > > > > > > > > > > > > Cheers, > > > > > > > > > > > > Albert > > > > > >> > > > > > >> Well, not now, i'm going to sleep now. > > > > > >> > > > > > >> Cheers, > > > > > >> > > > > > >> Albert > > > > > >> > > > > > >> ___ > > > > > >> release-team mailing list > > > > > >> release-team@kde.org > > > > > >> https://mail.kde.org/mailman/listinfo/release-team > > > > > > > > > > > > ___ > > > > > > release-team mailing list > > > > > > release-team@kde.org > > > > > > https://mail.kde.org/mailman/listinfo/release-te
Re: Release Cycle
On Thursday 22 August 2013 23:35:49 Albert Astals Cid wrote: > El Dijous, 22 d'agost de 2013, a les 08:07:22, Jos Poortvliet va escriure: > > On Tuesday 20 August 2013 22:40:29 Mark wrote: > > > On Tue, Aug 20, 2013 at 8:44 PM, Albert Astals Cid wrote: > > > > El Dimarts, 20 d'agost de 2013, a les 01:54:48, Albert Astals Cid va > > > > escriure: > > > >> El Dimarts, 20 d'agost de 2013, a les 01:17:18, Aaron J. Seigo va > > > > escriure: > > > >> > On Tuesday, August 20, 2013 00:24:53 Albert Astals Cid wrote: > > > >> > > El Dilluns, 19 d'agost de 2013, a les 22:18:26, Aaron J. Seigo va > > > >> > > > >> escriure: > > > >> > > > On Monday, August 19, 2013 22:14:26 Albert Astals Cid wrote: > > > >> > > > > There will be a 4.13? Most probably. > > > >> > > > > Will it be in 2014? For sure > > > >> > > > > Which month? Noone knows, you can probably guess it'll be > > > >> > > > > between > > > >> > > > > Q2 > > > >> > > > > and > > > >> > > > > Q3 > > > >> > > > > since Q1 would mean <= 3 months of development and Q4 would > > > >> > > > > mean > > > >> > > > > > > > >> > > > > >= > > > >> > > > > > > > >> > > > > 10 > > > >> > > > > months. > > > >> > > > > > > >> > > > unless we change the development cycle, which has not yet been > > > >> > > > done, > > > >> > > > which > > > >> > > > month will 4.13 be in? > > > >> > > > > > >> > > Are you disagreeing with the 4.12 schedule? > > > >> > > > > >> > No; however, on > > > >> > http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule it > > > >> > says > > > >> > “THIS IS NOT OFFICIAL YET” four times right at the top. I was under > > > >> > the > > > >> > impression that it was still being discussed and wasn’t ... you > > > >> > know > > > >> > .. > > > >> > official yet. > > > >> > > > >> It will be official when i get tired of waiting for people to oppose > > > >> to > > > >> it. > > > >> If it makes you happier, I can declare it official now. > > > > > > > > There you go. > > > > > > > > Cheers, > > > > > > > > Albert > > > >> > > > >> Well, not now, i'm going to sleep now. > > > >> > > > >> Cheers, > > > >> > > > >> Albert > > > >> > > > >> ___ > > > >> release-team mailing list > > > >> release-team@kde.org > > > >> https://mail.kde.org/mailman/listinfo/release-team > > > > > > > > ___ > > > > release-team mailing list > > > > release-team@kde.org > > > > https://mail.kde.org/mailman/listinfo/release-team > > > > > > What you just did means that KDE SC 4.12 will in fact be a 5 month > > > release cycle. Earlier there was talk about outlining the future > > > releases. That blog/news item is probably going to have to take the > > > new 5 month cycle into account. > > > > Yes. What about this then: > > === > > KDE frameworks 5 preview 1 December 2013 > > KDE frameworks 5 release 1st half 2014 > > KDE Workspaces 4.11 is last release (LTS) > > KDE Workspaces 2.0 preview 1st half 2014 > > KDE Workspaces 2.0 release 2nd half 2014 > > KDE Applications 4.12 December 18 2013 > > KDE Applications 4.13 June 2014 > > 4.12 and 4.13 will include kdelibs too (that have been almost-frozen for a > while but we still increase its version number on each release) > > Also we don't have a date for 4.13. > > It may well be May or July or even March or August since we haven't started > planning for it and we can't do it since at Akademy it was agreed we'd do a > shorter cycle (4.12) and then evaluate if that had worked or not, and to > evaluate it, we have to let 4.12 happen. > > So please be very clear June is a guessed month from your side since the > Release Team has not started discussing about it. "As with any schedule for a major technological transition, please note that the above is subject to change." Is that enough? Please note, as Aaron already said, that it is better to have a plan now and change it later than to have no plan at all. > Cheers, > Albert > > > As with any schedule for a major technological transition, please note > > that > > the above is subject to change. > > == > > > > If this is OK then we'll communicate it this way. > > > > > I like this new shorter cycle! > > > ___ > > > release-team mailing list > > > release-team@kde.org > > > https://mail.kde.org/mailman/listinfo/release-team > > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release Cycle
On Thursday 22 August 2013 16:00:00 Sebastian Kügler wrote: > On Thursday, August 22, 2013 15:38:20 Sebastian Kügler wrote: > > KDE Workspaces 2.0 preview 1st Q1/2013 > > KDE Workspaces 2.0 release 2nd Q2/2013 > > It's hard to write, let me try again: > > KDE Workspaces 2.0 preview Q1/2014 > KDE Workspaces 2.0 release Q2/2014 > > This sounds more like it. :) hehe thanks signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release Cycle
On Tuesday 20 August 2013 22:40:29 Mark wrote: > On Tue, Aug 20, 2013 at 8:44 PM, Albert Astals Cid wrote: > > El Dimarts, 20 d'agost de 2013, a les 01:54:48, Albert Astals Cid va escriure: > >> El Dimarts, 20 d'agost de 2013, a les 01:17:18, Aaron J. Seigo va escriure: > >> > On Tuesday, August 20, 2013 00:24:53 Albert Astals Cid wrote: > >> > > El Dilluns, 19 d'agost de 2013, a les 22:18:26, Aaron J. Seigo va > >> > >> escriure: > >> > > > On Monday, August 19, 2013 22:14:26 Albert Astals Cid wrote: > >> > > > > There will be a 4.13? Most probably. > >> > > > > Will it be in 2014? For sure > >> > > > > Which month? Noone knows, you can probably guess it'll be between > >> > > > > Q2 > >> > > > > and > >> > > > > Q3 > >> > > > > since Q1 would mean <= 3 months of development and Q4 would mean > >> > > > > >= > >> > > > > 10 > >> > > > > months. > >> > > > > >> > > > unless we change the development cycle, which has not yet been > >> > > > done, > >> > > > which > >> > > > month will 4.13 be in? > >> > > > >> > > Are you disagreeing with the 4.12 schedule? > >> > > >> > No; however, on > >> > http://techbase.kde.org/Schedules/KDE4/4.12_Release_Schedule it says > >> > “THIS IS NOT OFFICIAL YET” four times right at the top. I was under the > >> > impression that it was still being discussed and wasn’t ... you know .. > >> > official yet. > >> > >> It will be official when i get tired of waiting for people to oppose to > >> it. > >> If it makes you happier, I can declare it official now. > > > > There you go. > > > > Cheers, > > > > Albert > >> > >> Well, not now, i'm going to sleep now. > >> > >> Cheers, > >> > >> Albert > >> > >> ___ > >> release-team mailing list > >> release-team@kde.org > >> https://mail.kde.org/mailman/listinfo/release-team > > > > ___ > > release-team mailing list > > release-team@kde.org > > https://mail.kde.org/mailman/listinfo/release-team > > What you just did means that KDE SC 4.12 will in fact be a 5 month > release cycle. Earlier there was talk about outlining the future > releases. That blog/news item is probably going to have to take the > new 5 month cycle into account. Yes. What about this then: === KDE frameworks 5 preview 1 December 2013 KDE frameworks 5 release 1st half 2014 KDE Workspaces 4.11 is last release (LTS) KDE Workspaces 2.0 preview 1st half 2014 KDE Workspaces 2.0 release 2nd half 2014 KDE Applications 4.12 December 18 2013 KDE Applications 4.13 June 2014 As with any schedule for a major technological transition, please note that the above is subject to change. == If this is OK then we'll communicate it this way. > I like this new shorter cycle! > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release Cycle
On Monday 19 August 2013 21:18:52 Aaron J. Seigo wrote: > On Monday, August 19, 2013 16:52:28 Martin Graesslin wrote: > > which would be more likely May/June if we stick to five month cycle. Note: > > one of the outcomes of the "shorter release cycle" BOF at Akademy was that > > we might re-evaluate the situation after the 4.11 release. So in external > > communication I would not yet settle for a date because it could be > > anywhere between the three months later as proposed by Alex and return to > > six months as it used to be. > > imho, that’s fine. we can say we are planning 4.13 for August 2014, and if > we end up changing our mind we can announce that later as a clarification. > > we really don’t know if there will be shorter cycles after 4.11, so the > default expectation is to keep doing releases every six months. until we > know otherwise, that is the default plan. > > by saying that we currently plan on 4.13 in august 2014 we communicate to > the outside world that we have a roadmap. this is quite true, as can be > seen by the amount of thought going in this exact topic by so many people > from so many different angles (promo, apps, workspaces ...) > > so my recommendation is to go with Jos’ outline and if we change course for > 4.12/4.13 announce that then. > > really the worst thing we can do for external confidence is say “we don’t > know”, because that translates externally to “we aren’t planning”. but we > are planning. so we do know. and that’s what we need to communicate. Does this "let's go with Jos' roadmap" include the Plasma- and Frameworks proposal? Obviously we would make clear that, this being a major transition, people should expect changes in the roadmap... /J signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Release Cycle
On Monday 19 August 2013 16:19:42 Torgny Nyblom wrote: > On Monday 19 August 2013 15.43.54 Martin Graesslin wrote: > > So far there has not been any discussion about it (AFAIK). We only had a > > discussion about reducing the release cycle. Given that my personal > > expectation is that some time after 4.12 there will be 4.13. > > So far the plan is to continue with the normal release cycle until further > notice. When this notice will happen is not decided and as far as I know it > has not even been discussed. Ok, cool. Note that the goal of this article is to alleviate the exact issue Martin pointed to - people (and esp press) not understanding what is going on. I've contacted LinuxMagazin already and am about to contact golem.de as well. The reason we're being a bit pushy is that the more information we have, the better we can inform people ;-) It would be nice to know what the release plans are for at least 2014. Until now, we have something like I painted in my blog: KDE frameworks 5 preview 1 December 2013 KDE frameworks 5 release 1st half 2014 KDE Workspaces 4.11 is last release (LTS) KDE Workspaces 2.0 preview 1st half 2014 KDE Workspaces 2.0 release 2nd half 2014 KDE Applications 4.12 Januari 2014 KDE Applications 4.13 August 2014 How realistic is the above? It would be a nice roadmap to communicate. The only thing missing is then the transition of the Applications to Frameworks 5 but we can easily say that, given at least another year of releases, we'll inform people about that later. Cheers, Jos > /Regards > Torgny > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: promoting the release
On Saturday 17 August 2013 10:45:14 Martin Graesslin wrote: > On Friday 16 August 2013 17:21:57 Jos Poortvliet wrote: > > On Wednesday 14 August 2013 18:44:34 Martin Graesslin wrote: > > > On Wednesday 14 August 2013 18:40:16 Jos Poortvliet wrote: > > > > Heya, > > > > > > > > I noticed that when we promote the release over social media (dunno > > > > who > > > > does this) we link to the kde.org announcement. While that's cool and > > > > all, I think it would be better to link to the dot: there, people can > > > > leave comments and we can get a more lively place for ppl to go to > > > > when > > > > clicking links. > > > > > > > > What do we think? > > > > > > Sounds good, but there is not yet a story on the dot to link to :-) > > > > Sure there was, at least - I was coordinating with the release dude to > > make > > sure both would be ready at the same time... And the story was already > > published (but not on the front page) at the time the kde.org page was > > still full of 'work in progress' hints... > > I don't know, but when I wrote that mail I went before to: > * kde.org - announcement linked > * dot.kde.org - nothing As I said, the announcement was there and published, just not visible on the front page yet as the release was not officially out. It was official when we decided it was. In the Good Old Days, Sebas would make sure the announcement would not be visible on kde.org at all and go live with the dot story simultaneously. And that is how it should be, of course. Sorry, we shouldn't have talked in a private channel but on #kde-promo so you would've known the announcement was not out yet. And we should set a strict time for the announcement before AND stick to it (we set a time, 18:00 Amsterdam/Berlin/Paris time and then released earlier). Anyway, we can do better next time, let's do that. In general, while we put in a lot of work in the actual announcement, the process around it is not very good, clearly. I think we could do far better if we had better coordination and would follow a real release plan including social media messages, a count down perhaps, a note to the press with some info in advance, things like that. I just checked google.com/trends for GNOME and KDE and despite the distortion from Garden Gnomes it is visible that GNOME gets more attention for their releases (a spike in search volume) and we don't. Surely 4.11 is far more boring than 3.0 and 3.1 but still, we can do better... /J > * kdenews.org - nothing > > Given the timestamps of the mails it was at least half an hour after Albert > pushed the announcement. > > So that looks to me like there was some coordination missing or the dot > taking too long to publish the page (I had seen cases when one news was on > dko but not on kdenews.org). > > Anyway when I first shared the news on G+ there was no link on dot I could > share ;-) I honestly thought that there won't be one. > > Cheers > Martin signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-promo] Kopete changes for KDE 4.11
On Thursday 15 August 2013 06:22:19 Carl Symons wrote:
> On Thu, Aug 15, 2013 at 12:48 AM, Pali Rohár wrote:
> > On Saturday 13 July 2013 22:47:26 Jos Poortvliet wrote:
> >> On Saturday, July 13, 2013 09:53:25 Pali Rohár wrote:
> >> > Hello,
> >> >
> >> > Kopete in KDE 4.11 has fixed more bugs and has lot of new
> >> > features (comparing to 4.10/9/8 versions). I'm sending list
> >> > of some new changes which could be in KDE 4.11 release
> >> > page.
> >> >
> >> > * Kopete migrated from svn to git
> >> > * Fixed memory leaks, corruptions and NULL dereferences
> >> > * Fixed lot of Kopete crashes at exit, at logout and when
> >> > closing modal dialogs * Support for adding new contacts to
> >> > Top Level group * Allow inviting users to groupchat by
> >> > drag-n-dropping * Automatically logout and login with
> >> > suspend/resume * Activate webcam preview in settings dialog
> >> > only if webcam tab is selected * New sqlite history plugin
> >> > (by default old one is used and new is disabled) * SSL
> >> > support for ICQ protocol (enabled by default for all ICQ
> >> > accounts) * Updated jabber libiris library from upstream
> >> >
> >> > - Fixed lot of connections problems (specialy legacy SSL
> >> > and logining) - Support for SCRAM-SHA-1 SASL login
> >> > mechanism (needed for new servers) - XMPP 1.0 support
> >> > (this fixed login to gmx, facebook and other servers)
> >> >
> >> > * Updated jabber google libjingle library for gtalk voice
> >> > calls * Fixed wizard for registring new jabber account
> >> > * Support for jabber XEP-0184: Message Delivery Receipts
> >> > (sender and reciver of chat messages will see delivery
> >> > status) * Support for jabber XEP-0199: XMPP Ping
> >> > * Fixed problems with skype protocol when user sent or
> >> > recived same/duplicate messages
> >>
> >> I love you. Really, if I wasn't married, I might propose ;-)
> >>
> >> If only more developers would do this ;-)
> >>
> >> Thanks a lot!
> >>
> >> @release team: I'd love it if you folk would think about a
> >> process change for our development which would include,
> >> somewhere, the writing-down-of-features a bit like above.
> >> Like in the always-summer thing: feature branches being
> >> merged need a proper explanation (like above) and a tag
> >> ("FEATURE:XX) or get denied. Or something like that. Then
> >> we'd just collect the change logs that are tagged with
> >> FEATURE and we can write announcements.
> >>
> >> /me can dream
> >
> > Ah, I'm unhappy, that you did not mention anything about kopete
> > on KDE 4.11 release page :-( Now for users it can looks like
> > kopete development is dead...
> >
> > --
> > Pali Rohár
> > pali.ro...@gmail.com
>
> On behalf of everyone who worked on the announcement...some much more
> than others (Jos)...I apologize.
let me also apologize myself, I must have missed adding this. I'm really sorry
as it is a very good text... It just slipped through the cracks :(
> I've added a comment to the Dot story. Ironically, Kopete will get
> more attention this way than if had been summarized and included in
> the announcement.
>
> Your information is exactly what is needed from developers so that
> developers' work can be publicized properly. This episode makes it
> painfully clear that the release process needs to be improved.
>
> Carl
signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
Re: promoting the release
On Wednesday 14 August 2013 18:44:34 Martin Graesslin wrote: > On Wednesday 14 August 2013 18:40:16 Jos Poortvliet wrote: > > Heya, > > > > I noticed that when we promote the release over social media (dunno who > > does this) we link to the kde.org announcement. While that's cool and > > all, I think it would be better to link to the dot: there, people can > > leave comments and we can get a more lively place for ppl to go to when > > clicking links. > > > > What do we think? > > Sounds good, but there is not yet a story on the dot to link to :-) Sure there was, at least - I was coordinating with the release dude to make sure both would be ready at the same time... And the story was already published (but not on the front page) at the time the kde.org page was still full of 'work in progress' hints... In any case, this then is a lack of coordination, if anything :D Next release I propose all people who want to help, in any capacity, even if it's just 'plus+'ing the announcement, hang on kde-promo. And we talk there. And yes, that means I did it wrong too as Albert and myself were talking in a private IRC channel... /J > Cheers > Martin signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
promoting the release
Heya, I noticed that when we promote the release over social media (dunno who does this) we link to the kde.org announcement. While that's cool and all, I think it would be better to link to the dot: there, people can leave comments and we can get a more lively place for ppl to go to when clicking links. What do we think? /Jos signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Can i still merge this, small KDirWatch improvement.
On Wed, Aug 7, 2013 at 7:37 PM, Albert Astals Cid wrote: > El Dimecres, 7 d'agost de 2013, a les 13:13:36, Mark va escriure: >> On Wed, Aug 7, 2013 at 10:38 AM, Albert Astals Cid wrote: >> >> Hi Release team, >> > >> > Hi >> > >> >> I just got the OK to ship [1] but considering the very close release >> >> of KDE 4.11 it seems right to ask the release team for permission as >> >> well. >> >> >> >> The patch simply prevents one stat call with KDirWatch and makes the >> >> code a little bit better to understand. Tests pass just fine and othe >> >> additional (visual and gdb) testing hasn't shown any regression. >> >> >> >> If i am not allowed to push it (due to the very close 4.11 tag), when >> >> can i push it then? Right after the tag i assume? >> > >> > Honestly, if this is just a [small] speed optimization and doesn't fix any >> > bug, i don't see it belonging to 4.11 at all, just commit it to master >> > and leave it for 4.12. >> > >> > Unless is a so huge optimization our users are going to send us money for >> > the speed difference :D >> > >> > Cheers, >> > >> > Albert >> >> Hi Albert, >> >> I'm OK with this not going into 4.11.0 since that is just a too short >> notice. But i do like to get this in the next bugfix release (4.11.1). It >> might not be a strict "bugfix", but that's only because nobody ever >> opened a bug report for it. >> Specially because 4.11 is LTS! Users and likely some company's are >> going to be running that version for years to come. They should have >> this fix. > > Let me repease, 4.11 is LTS *only for kde-workspace*. This patch is for > kdelibs, which will have a regular 4.12 release, so they'll get this > optimization in 5 months. Just to check, distro's using the 4.11 LTS for workspaces are likely, you think, to upgrade the KDElibs to 4.12 underneath it so they will get this patch? If not, the argument that there'll be a 4.12 doesn't really have much value... And, as KDELibs is so frozen-y, perhaps it should be LTS too, instead of doing a 4.12 release... > Cheers, > Albert > >> >> No, it won't get you or KDE any money, but it does save one stat call >> in a very common code path (creating files) thus you could argue that >> this patch will extend the life of storage devices ;-) >> >> >> Kind regards, >> >> Mark >> >> >> >> [1] https://git.reviewboard.kde.org/r/111870/ >> >> ___ >> release-team mailing list >> release-team@kde.org >> https://mail.kde.org/mailman/listinfo/release-team > > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Can i still merge this, small KDirWatch improvement.
On Wednesday 07 August 2013 10:12:48 Albert Astals Cid wrote: > > On Wednesday 07 August 2013 09:38:51 Albert Astals Cid wrote: > > > > Hi Release team, > > > > > > Hi > > > > > > > I just got the OK to ship [1] but considering the very close release > > > > of KDE 4.11 it seems right to ask the release team for permission as > > > > well. > > > > > > > > The patch simply prevents one stat call with KDirWatch and makes the > > > > code a little bit better to understand. Tests pass just fine and othe > > > > additional (visual and gdb) testing hasn't shown any regression. > > > > > > > > If i am not allowed to push it (due to the very close 4.11 tag), when > > > > can i push it then? Right after the tag i assume? > > > > > > Honestly, if this is just a [small] speed optimization and doesn't fix > > > any > > > bug, i don't see it belonging to 4.11 at all, just commit it to master > > > and > > > leave it for 4.12. > > > > > > Unless is a so huge optimization our users are going to send us money > > > for > > > the speed difference :D > > > > Don't want to interfere with the release team work - but, if 4.11 is going > > to be a long term maintained version (and it is) doesn't it make sense to > > let this go in during say 4.11.3 or so (it would've gotten some more > > testing by then)? Otherwise, this won't reach users for a long time - and > > that's neither very motivating nor benefiting anybody. > > The only thing long term in 4.11 is kde-workspace, this is not > kde-workspace, so your rationale doesn't apply. It's KDELibs then? The rationale is kind'a the same - Frameworks 5 is still a while off, it seems sensible to let users benefit from a slightly more liberal policy with regards to our .x releases until the 5 series arrives on the scene. Even if not for this patch, don't you think it makes sense to adopt a similar policy as we did in the KDE 3.5 times? > Cheers, > Albert > > > > Cheers, > > > > > > Albert > > > > > > > Kind regards, > > > > Mark > > > > > > > > [1] https://git.reviewboard.kde.org/r/111870/ signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Can i still merge this, small KDirWatch improvement.
On Wednesday 07 August 2013 09:38:51 Albert Astals Cid wrote: > > Hi Release team, > > Hi > > > I just got the OK to ship [1] but considering the very close release > > of KDE 4.11 it seems right to ask the release team for permission as > > well. > > > > The patch simply prevents one stat call with KDirWatch and makes the > > code a little bit better to understand. Tests pass just fine and othe > > additional (visual and gdb) testing hasn't shown any regression. > > > > If i am not allowed to push it (due to the very close 4.11 tag), when > > can i push it then? Right after the tag i assume? > > Honestly, if this is just a [small] speed optimization and doesn't fix any > bug, i don't see it belonging to 4.11 at all, just commit it to master and > leave it for 4.12. > > Unless is a so huge optimization our users are going to send us money for > the speed difference :D Don't want to interfere with the release team work - but, if 4.11 is going to be a long term maintained version (and it is) doesn't it make sense to let this go in during say 4.11.3 or so (it would've gotten some more testing by then)? Otherwise, this won't reach users for a long time - and that's neither very motivating nor benefiting anybody. > Cheers, > Albert > > > Kind regards, > > Mark > > > > [1] https://git.reviewboard.kde.org/r/111870/ signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Shift releases?
On Tuesday 23 July 2013 20:11:55 Albert Astals Cid wrote: > El Dimarts, 23 de juliol de 2013, a les 08:29:05, Andras Mantia va escriure: > > Hi, > > > > was RC1 already prepared/tagged? > > Yes, last week. > > http://www.kde.org/announcements/announce-4.11-rc1.php > http://www.kde.org/info/4.10.95.php perhaps it is worth doing a call-for-testing on the dot, mentioning that this release is meant to be the last in the 4 series for at least the workspaces? It could be a quick, short article, just to get a few extra testers... > Cheers, > Albert > > > KDEPIM has a major regression in maildir > > > > handling in it. We are working on that (and actually Sergio reverted the > > commit (3f86351c2082cbcabc897dfceac95496b7876cf0), so I'd be glad if the > > hotfix is in RC1. > > > > Not having it causes VERY slow Kmail behavior and lots of duplicated > > mails > > > > in maildir folders that you can't get rid of easily. > > > > Andras > > ___ > > release-team mailing list > > release-team@kde.org > > https://mail.kde.org/mailman/listinfo/release-team > > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Kopete changes for KDE 4.11
On Saturday, July 13, 2013 09:53:25 Pali Rohár wrote:
> Hello,
>
> Kopete in KDE 4.11 has fixed more bugs and has lot of new features
> (comparing to 4.10/9/8 versions). I'm sending list of some new
> changes which could be in KDE 4.11 release page.
>
> * Kopete migrated from svn to git
> * Fixed memory leaks, corruptions and NULL dereferences
> * Fixed lot of Kopete crashes at exit, at logout and when closing modal
> dialogs * Support for adding new contacts to Top Level group
> * Allow inviting users to groupchat by drag-n-dropping
> * Automatically logout and login with suspend/resume
> * Activate webcam preview in settings dialog only if webcam tab is selected
> * New sqlite history plugin (by default old one is used and new is disabled)
> * SSL support for ICQ protocol (enabled by default for all ICQ accounts) *
> Updated jabber libiris library from upstream
> - Fixed lot of connections problems (specialy legacy SSL and logining)
> - Support for SCRAM-SHA-1 SASL login mechanism (needed for new servers)
> - XMPP 1.0 support (this fixed login to gmx, facebook and other servers)
> * Updated jabber google libjingle library for gtalk voice calls
> * Fixed wizard for registring new jabber account
> * Support for jabber XEP-0184: Message Delivery Receipts (sender and reciver
> of chat messages will see delivery status) * Support for jabber XEP-0199:
> XMPP Ping
> * Fixed problems with skype protocol when user sent or recived
> same/duplicate messages
I love you. Really, if I wasn't married, I might propose ;-)
If only more developers would do this ;-)
Thanks a lot!
@release team: I'd love it if you folk would think about a process change for
our development which would include, somewhere, the writing-down-of-features a
bit like above. Like in the always-summer thing: feature branches being merged
need a proper explanation (like above) and a tag ("FEATURE:XX) or get denied.
Or something like that. Then we'd just collect the change logs that are tagged
with FEATURE and we can write announcements.
/me can dream
signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
Re: Kopete changelog
On Friday 11 January 2013 08:06:54 Pali Rohár wrote: > Hello, > > I do not know how is KDE developers adding changelog or future > list to announcement of new KDE version on kde.org. But I added > to Kopete support for disabling all visible & sound notifications > in Busy / Do Not Disturb status. So now Kopete has real Do Not > Disturb mode. Patch was commited after review from: > https://svn.reviewboard.kde.org/r/6586/ > http://websvn.kde.org/?revision28745&view=revision > and fixing more reported bugs: > https://bugs.kde.org/show_bug.cgi?id"9306 > https://bugs.kde.org/show_bug.cgi?id 5303 > https://bugs.kde.org/show_bug.cgi?id4113 > First time this problem was reported on 2007-03-29. > > CCing kde release team and kdenetwork maintainer, maybe you know > how to add new info about fixed bug to kde announcement page... Heya, We use the feature plan for the announcement text: http://techbase.kde.org/Schedules/KDE4/4.10_Feature_Plan But mailing kde-promo also works and I monitor this list as well - so thanks :D /Jos signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: We are having RC3 was: Re: Another RC?, was: Re: Akonadi-Nepomuk Feeder Improvements
On Monday 31 December 2012 17:23:11 Albert Astals Cid wrote: > El Dilluns, 31 de desembre de 2012, a les 16:44:18, Martin Gräßlin va > escriure: > > what about Kubuntu uses stable from branch as of freeze day? That would > > be very close to 4.10.2. > > > > Or maybe tag 4.10.2 at the Kubuntu freeze day, but otherwise keep the > > schedule shifted? > > Honestly, who cares if Kubuntu ships 4.10.1(because we made an RC3) or > 4.10.2 (because we did not make an RC3)? > > It will still be "x days" after the freeze so the code quality will be > very similar. > > Since it seems almost everyone agrees we want an RC3 but noone is doing > the step to announce it, i will do it. > > We will keep the same separation as between RC1 and RC2, i.e. two weeks, > so > > January 2, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 2 > January 3, 2013: KDE SC 4.10 Release Candidate 2 Tagging > January 4, 2013: KDE SC 4.10 Release Candidate 2 Release > January 16, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 3 > January 17, 2013: KDE SC 4.10 Release Candidate 3 Tagging > January 18, 2013: KDE SC 4.10 Release Candidate 3 Release > January 30, 2013: KDE SC 4.10 Final Tag > February 6, 2013: KDE SC 4.10 Release > > Vishesh, Christian can you please commit your respective code ASAP? > > Cheers, > Albert Cool. Even inspired me to prepare the dot story for the release (just re- doing the first sentences...) Text: "Today KDE released the second release candidate for its renewed Workspaces, Applications, and Development Platform. Meanwhile, the KDE release team has decided to schedule a 3rd release candidate to allow for more testing, pushing the 4.10 releases into the first week of February 2013. Further testing and bug fixing will allow KDE to deliver rock-stable products to millions of users world wide." http://dot.kde.org/2013/01/01/kde-ships-second-release-candidate-plasma- workspaces-applications-and-platform-410 I know the dot story isn't the biggest chunk of work but every bit helps, right? Jos signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Another RC?, was: Re: Akonadi-Nepomuk Feeder Improvements
On Sunday 30 December 2012 20:55:22 Scott Kitterman wrote: > On Monday, December 31, 2012 12:24:18 AM Sebastian Kügler wrote: > > On Sunday, December 30, 2012 02:41:43 Scott Kitterman wrote: > > > Assuming 4.10.1 and 4.10.2 slip similarly, that would result in the > > > next > > > Kubuntu release having 4.10.1 instead of 4.10.2. We might also have > > > to > > > make some adjustments to our internal testing milestone schedule. > > > > > > 4.10.2 would come out a day or two before Kubuntu 13.04 (far to late > > > for > > > pre- release updates) so we'd get to release without the current KDE > > > SC. We do ship the point releases as post-release updates, so they > > > would > > > get to users eventually, but post-release QA is a lot more work for > > > us. > > > > > > This isn't precisely a problem, but changing the release cycle now is > > > not > > > idea for us. As long as 4.11 drops back into the usual time slot > > > (and > > > doesn't also slip), then the impact would not be major. > > > > Would adding in two instead of three weeks work for you? > > No. Looking at the schedule, it would need to be only a week later than > the current schedule to make it. If the 4.10.0 -> 4.10.1 and 4.10.1 -> > 4.10.2 intervals were slightly reduced, maybe we could get there? > > Scott K Just out of curiosity - how big a deal is it to ship with 4.10.1 instead of 4.10.2? Does it matter, other than the number? As a user, I'm rather fond of having a much more usable KDE PIM in 4.10... I can't judge the technical side of this argument but the impact of crappy Nepomuk<->KDEPIM interaction is still very noticeable in the RC... signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: No more release schedules.
On Friday 10 June 2011 01:00:45 Andreas K. Huettel wrote: > > I just read a very good novel where all such talk about "Software > > Collection" > > > or "Platform" was aptly called "commercial bulshytt". I think many of us, > > including your "only-users", would appreciate it if you all there > > upstream would just stick to KDE, because that is what everyone uses. > > Nothing else. > > > > Not on-topic for this list at all, nor relevant for this thread... > > That is not true. > > The large majority of your _userbase_ does not identify themselves with, > say, solid, okular, libkipi, phonon, and krosspython. Maybe some > technically minded people are huge enthusiasts about plasma. In the end, > however, what people are talking about is the entity KDE, and what people > appreciate is its entirety as desktop environment. Not a development > library framework. "Software Collection" at least had that still half-way > in mind. > > Even plasma will by most people be perceived as "the desktop of KDE". > > Please don't misunderstand me, of course for software developers the > viewpoint is a bit different, but I'm talking about users here. > > In the end, you will be perceived for what you release - and here we get > back to this list. KDE lives from being a consistent whole. Eric Hameleers > already made some very valid points there. Breaking KDE up does not help, > and the coordinated releases were/are a great thing. No matter your or anyone else's opinion on this, I think Toma is saying: let the release team discuss and come up with a proposal, THEN comment on it on kde-devel, kde-packager etcetera. A very valid request from him and I think you should follow it. signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Akonadi Meeting: exception request. / Porting Status?
On Mon, May 10, 2010 at 6:45 PM, Tom Albers wrote: > > On Mon, 10 May 2010 18:11:24 +0200, Jos Poortvliet > wrote: >> On Mon, May 10, 2010 at 12:11 PM, Sebastian Kügler > wrote: >>> Hi PIMsters, >> >> >> >>> When would be a good moment to start testing KDE PIM 4.5? I've svn >>> switched those >>> modules to the 4.4 version until further notice when you guys began >>> porting, but >>> haven't seen any meaningful communication about stability and progress >>> of this >>> critical KDE SC component. >> >> Yes, communication is lacking now. I'd love to see a little more >> blogging and info for users, even a call for testing or help if there >> are issues - let us know what is going on. Even if it's just a few >> bullet points on a blog or a repost of an important mail to the pim >> mailinglist... Doesn't have to be complicated. >> >> And if there is or might be an issue, we should communicate it to our >> users, rally some support in testing or even patches... You can't >> expect 10 new developers in a week but by having regular updates >> people will have more feeling with PIM and are more inclined to help >> out. >> >> If you need help with this, just let me know, the promo team is surely >> willing to help but we need at least SOME input! >> >> Cheers, >> Jos > > Thanks Jos, > > I'ld love a dedicated promo/marketing dude that comes to every pim & > akonadi meeting, blogs regular announcements and updates and tries to > educate the developers. I've indicated that a couple of times here and > there, but apart from some incidental help (which I appreciate), nothing > structural has been done. And I think that is very needed. Yes, and tbh I really remember someone stepping up to do that but I don't remember who it was... I know, weak of me... > Best, > > -- > Tom Albers > KDE Developer > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team > ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Akonadi Meeting: exception request. / Porting Status?
On Mon, May 10, 2010 at 12:11 PM, Sebastian Kügler wrote: > Hi PIMsters, > When would be a good moment to start testing KDE PIM 4.5? I've svn switched > those > modules to the 4.4 version until further notice when you guys began porting, > but > haven't seen any meaningful communication about stability and progress of this > critical KDE SC component. Yes, communication is lacking now. I'd love to see a little more blogging and info for users, even a call for testing or help if there are issues - let us know what is going on. Even if it's just a few bullet points on a blog or a repost of an important mail to the pim mailinglist... Doesn't have to be complicated. And if there is or might be an issue, we should communicate it to our users, rally some support in testing or even patches... You can't expect 10 new developers in a week but by having regular updates people will have more feeling with PIM and are more inclined to help out. If you need help with this, just let me know, the promo team is surely willing to help but we need at least SOME input! Cheers, Jos *A while ago there was a great plan to promote PIM better - will have a look at that and see if I can start the discussion again. > Thanks, > -- > sebas > > http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 > ___ > release-team mailing list > release-team@kde.org > https://mail.kde.org/mailman/listinfo/release-team > ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.5 schedule
On Saturday 27 March 2010 15:40:06 泡泡龙 wrote: > 2009？？？ Our dear aaron is just being ambitious here, why o why is ambition always shot down in the KDE community? Where did we go wrong?!? grumble grumble... ;-) signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: How to release an extragear app?
On Saturday 27 February 2010 18:51:56 Eike Hein wrote: > On 02/27/2010 06:26 PM, Andreas Pakulat wrote: > > Besides tagging, tarballing, branching, notifying packagers and writing > > a dot-announcement is there anything else I need to take care of? > > Here's some mails about this I wrote recently: > http://lists.kde.org/?l=kde-extra-gear&m=124927007024432&w=2 > http://lists.kde.org/?l=kde-extra-gear&m=124928664908058&w=2 > > The checklist has changed a bit recently, e.g. because > the tarballs are now on download.kde.org which implies > 6h or so of mirror syncing before being able to do the > public announcements, and because there are new commu- > nication channels like Facebook that the release is > also announced on, and because of the move to git (now > using a homecooked tool rather than create_tarball atm), > but that's basically it. > > > Andreas Please let the promo team know at least a few days beforehand when the release will be. If you want us we can try and help you write the announcement (pls give us a week) and maybe a feature guide (but of course a feature guide would take more than a week, think more like a month). We'll also help promote the release to facebook, youtube (if you have video's) and other channels. The dot editors also need a heads-up a few days before if you want a timely release announcement on the dot. Cheers, Jos ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-promo] release PR update
On Monday 08 February 2010 09:26:44 Franz Keferböck wrote: > Hi all, > > this is a sign of life again from me (i've been virtually dead the > last year++, not just in KDE land) and i'd like to address the "buzz" > thing. > > Out of a notion - and the fact that i couldn't look at the current > buzz.kde.org site as it kept on killing my browser I tried to use my > "spare time" to reimplement something like it again - yet cleaner and > faster. I guess I managed to, sent the results to Lydia who also > included Tom Albers in the discussion on finishing it. Nuno blessed > the Design (mostly a copy of the orignial anyways, just a couple if > details he had to check, mainly with the item's layout and design). I > made it all GPL and included the license with all source files (those > I wrote, there's also one PHP from the web > [http://pear.php.net/pepr/pepr-proposal-show.php?id=198 BSD Licensed] > and of course mootools [http://www.mootools.net MIT License] included > as they are from the original websites). The code works fairly well > and i've not yet had any real issues since the last bugs Jos > Poortvliet found where ironed out. That was what i then committed to > svn (/home/kde/trun/www/sites/buzz) as that's where TomA pointed me > to. He was noticed by Lydia about it, i'll try to catch him today to > see what's still there. > > If you want to have a look on what it is like now, point your browser > to http://www.isis-marketing.at/buzz/ > > The last issue i can see is that the icons in the top row are all the > same - which is in fact the "dot" icon from planetkde. I'd appreciate > if you could point me to the correct icons for the other websites to > be included. > > I'll be on IRC all day long today (at least till 4pm CET, maybe > longer, no long travelling or flight planning or such today), channels > #kde-promo, #oxygen, #kde-www and #kde-devel (still fkefer there ;-). > > Good to find my way back again, really, i felt SO bad already, but i > couldn't help, my private life was going down for some time, and as > that stopped my company kept sending me to all different places all > over the world, with little internet for private use yet lots of > interesting things to see... nice tradeoff, yet not for KDE. > > So "Hi, i'm trying to find my way back" to ya all (instead of bye) I think you made quite a splash coming back like this, thanks for the great work ;-) signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-promo] Not available for beta1 release
On Tue, May 20, 2008 at 4:13 PM, Will Stephenson <[EMAIL PROTECTED]> wrote: > On Tuesday 20 May 2008 12:28:27 Sebastian Kügler wrote: >> I'll be on vacation next week so I don't expect to have a reliable Internet >> connection (nor the guts to tell my girlfriend that I have to work) to do >> the release announcement for beta1 and website updating dance next Tuesday. >> >> If anyone else can step up, please do so. I can explain and help where >> necessary. It's also a good idea to have a second person aware of the >> release PR involves, bus numbers ... >> >> So, who's in a for a crash-course release PR? > > I can do it. And I can probably help as well. > Will > > ___ > 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. > ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-ev-marketing] Delaying 4.0?
On 11/28/07, Wade Olson <[EMAIL PROTECTED]> wrote: > On Nov 28, 2007 8:29 AM, Sebastian Kügler <[EMAIL PROTECTED]> wrote: > > [CC:ing ev-marketing anyway.] > > > > On Wednesday 28 November 2007 15:08:50 Andreas Pakulat wrote: > > > On 28.11.07 07:30:29, Rex Dieter wrote: > > > > Andras Mantia wrote: > > > > > On Wednesday 28 November 2007, Rex Dieter wrote: > > > > >> If this is absolutely the last slip, sure. Otherwise, the release > > > > >> party scheduled for January 17 will look pretty silly. > > > > > > > > > > But doing a release just for the shake of the release party is equally > > > > > silly. :) > > > > > > > > So, do *you* want to be the one to tell the event organizers that all > > > > their hard work and effort to pull the event together is now in > > > > jeopardy? Not I. > > > > > > Huh? Why is their effort wasted if the release happens on Feb. 4th or > > > some such? They can still pull off a release party. Its not like the > > > party is going to be months before the release. > > Because we, the release planning group, have been asking since the > summer for a good, safe, reliable date for a release event would be. > And guess what: that answer was November. So we padded 2 months and > are now running into the same problem. > > So if we had listened to even the most conservative estimates, it > would have been *exactly* like the party was months before the > release. > > Having a release party before the release? Hell, we might as well > roll in a 4.1 and 4.2 release party at the same time, since we know > what's going to be in them as well. I hear some frustration ;-) But yeah, delaying to the day we do the release party (eg give the releaseparty when KDE is released) might be fun, but later... I think that would really suck for our image. Most ppl don't believe we can release in 2007, slipping by 2 weeks is bad already, but not making our release party date at all... bleh. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-ev-marketing] the "gamma" proposal - details that need working out
Op Saturday 14 July 2007, schreef Troy Unrau: > On 10/07/07, Thiago Macieira <[EMAIL PROTECTED]> wrote: > > Aaron J. Seigo wrote: > > >the aim is to create a 4.0 release in october (or whenever it is > > >deemed "ready") without an official "to the rest of the world" > > > announcement. this allows us to push 4.0 out to the community -and- > > > create a media event on a day we can count on (e.g. past the day of > > > scheduled release) > > > > I thought that was the plan all along. Why are we arguing about it then? > > > > Release Team gets code ready and tells Marketing Team: "here, release it > > when you find the best time for it". > > Yeah, more or less. The only difference is that between the scheduled > release and the actual party is like three months, so we were assuming > that there would be substantial improvements to the code in those > months, especially the translations. But we still wanted that release > announcement to be about 4.0.0, and the way to do that was to shift > all the release numbers down by one. The better solution, as > suggested by a few others, is to simply use release names. > > Cheers Now onto this proposal: three months. Why do we want it? Three reasons I can think off: - Stability. We want to give out a message 'this is ready for corporate use' - Time. We need time for our release event... - Features. We need some support from the community for language packs, plugins, applets, plasmoids and other user-generated stuff. I think for marketing, we should focus on the third. If we tell ppl about the first, they will see our 4.0 release as a release candidate. Of course, we can mention it later on as an advantage... Second - a bit silly. But the third... "We, KDE developers, have worked on this for 2 years. Now it's time for the community to get involved! You will have three months to work on additions to KDE, like (blabla). After this time, we will choose the best of them, and bundle them with the official KDE." This way, we can put KDE firmly with it's feet in the community, AND we get more commitment! We should open the 4.0.x series of course only for bugfixes, but maybe also for some usability fixing like toolbar button configuration and such. And of course translations and documentation. These three months can see regular subreleases, which will keep the fire going. We can tell, at each release, who's work (from community members) we're thinking of incorporating in KDE. How about this? Grtz Jos -- Disclaimer: Alles wat ik doe denk en zeg is gebaseerd op het wereldbeeld wat ik nu heb. Ik ben niet verantwoordelijk voor wijzigingen van de wereld, of het beeld wat ik daarvan heb, noch voor de daaruit voortvloeiende gedragingen van mezelf. Alles wat ik zeg is aardig bedoeld, tenzij expliciet vermeld. Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html A: Because it destroys the flow of the conversation Q: Why is top-posting bad? signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [kde-ev-marketing] the "gamma" proposal - details that need working out
Op Saturday 14 July 2007, schreef Troy Unrau: > On 10/07/07, Thiago Macieira <[EMAIL PROTECTED]> wrote: > > Aaron J. Seigo wrote: > > >the aim is to create a 4.0 release in october (or whenever it is > > >deemed "ready") without an official "to the rest of the world" > > > announcement. this allows us to push 4.0 out to the community -and- > > > create a media event on a day we can count on (e.g. past the day of > > > scheduled release) > > > > I thought that was the plan all along. Why are we arguing about it then? > > > > Release Team gets code ready and tells Marketing Team: "here, release it > > when you find the best time for it". > > Yeah, more or less. The only difference is that between the scheduled > release and the actual party is like three months, so we were assuming > that there would be substantial improvements to the code in those > months, especially the translations. But we still wanted that release > announcement to be about 4.0.0, and the way to do that was to shift > all the release numbers down by one. The better solution, as > suggested by a few others, is to simply use release names. > > Anyway, the marketing stuff comes below: > > This whole debate can be solved if we move to using release names > rather than numbers. In that event we can totally pull the wool over > the eyes of the press. eg: Windows XP == NT 5.1, but still had a big > impact. OS X is releasing 10.5 shortly, but by giving it a name and > burying the release number, it seems fresh and new. After monitoring > this discussion, I now believe that moving to named releases would > solve our problems without messing with the current release cycle or > structure. Then everyone is happy, even Sebas. :) > > So, we then need names that reflect the state of 4.0 for both the > "4.0.0" October release, and our slightly more > polished/translated/fixed "4.0.1" release in January which would be > used for the announcement. > > Since a number of the marketing types are trying to steal and > repurpose the word "gearhead" to mean "person involved or interested > in KDE", I believe we could reasonably call 4.0.0 in October as "KDE 4 > Gearhead Edition". Developers and early adopters would all likely be > classified as gearheads, at least by the definition we've been using > up until this point. > > Then in late January we can call 4.0.1 as "KDE Fourth Gear Edition" or > such (inspired by a comment on one of ade's KDE T-shirt blog posts). > Which is professional sounding enough to announce in Silicon Valley > while giving it a strong KDE flavour and effectively disguising from > the fact that it's actually 4.0.1 under the hood. > > Additionally, since our main press event is in California (there will > be other concurrent, community oriented events happening elsewhere of > course), the terminology of Fourth Gear will be a hit. For those > unaware, Fourth Gear here is generally considered to be the gear you > hit on the freeway when you want to pass somebody. If we play this up > properly, we can use this as the release where we are 'passing Gnome' > or 'passing OS X' or such to go to the front of the pack. (Your > thoughts on this name Aaron? since you're presenting speaking at this > announcement...) > > Unless someone has a serious and legitimate objection to this (and not > just bikeshedding on the names), I suggest that we make this our > official course of action. > > We will be nailing down the exact date (of the announcement) this > upcoming Thursday on a conference call between the event planners. > Once that date is set (likely last week of january, or even February > 1st), it cannot slip since we'll be booking hotels, journalists will > be invited who will need to book flights, and so forth. "KDE 4 > Gearhead Edition" (4.0.0) can slip a little if the release team needs > more time (up to three months I guess) and it won't bother our > announcement in January. > > Cheers I agree, but I sure do want to bikeshed on the name. gearhead - isn't that a bit childish? The second name is reasonable, but the first... I'm not sure, maybe others can respond? -- Disclaimer: Alles wat ik doe denk en zeg is gebaseerd op het wereldbeeld wat ik nu heb. Ik ben niet verantwoordelijk voor wijzigingen van de wereld, of het beeld wat ik daarvan heb, noch voor de daaruit voortvloeiende gedragingen van mezelf. Alles wat ik zeg is aardig bedoeld, tenzij expliciet vermeld. Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html A: Because it destroys the flow of the conversation Q: Why is top-posting bad? signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
