Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 493782 (kde-4.11.5-stable) - KDE 4.11.5 stabilization
Summary: KDE 4.11.5 stabilization
Status: RESOLVED FIXED
Alias: kde-4.11.5-stable
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Keywording and Stabilization (show other bugs)
Hardware: All Linux
: Normal enhancement with 1 vote (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords: STABLEREQ
Depends on: 493278 493304 494732
Blocks:
  Show dependency tree
 
Reported: 2013-12-09 20:16 UTC by Johannes Huber (RETIRED)
Modified: 2014-02-26 09:34 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
kde-4.11.4-stable-list v1 (list.txt,7.90 KB, text/plain)
2013-12-09 20:22 UTC, Johannes Huber (RETIRED)
Details
kde-4.11.5-stable-list v1 (4.11.5,7.93 KB, text/plain)
2014-02-05 11:54 UTC, Michael Palimaka (kensington)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Huber (RETIRED) gentoo-dev 2013-12-09 20:16:05 UTC
In preparation, please avoid talking here.
Comment 1 Johannes Huber (RETIRED) gentoo-dev 2013-12-09 20:22:51 UTC
Created attachment 365020 [details]
kde-4.11.4-stable-list v1

First draft, please only add NEEDED packages to the list.
Comment 2 Agostino Sarubbo gentoo-dev 2013-12-10 08:05:10 UTC
I just want to remember that _I_ will cc kde-stable when I guess is the time. Thanks
Comment 3 Johannes Huber (RETIRED) gentoo-dev 2013-12-18 21:48:53 UTC
(In reply to Agostino Sarubbo from comment #2)
> I just want to remember that _I_ will cc kde-stable when I guess is the
> time. Thanks

Yes, and you please dont change keywords until all arches stable. We the kde herd will do it in one commit.
Comment 4 Agostino Sarubbo gentoo-dev 2014-01-07 19:23:55 UTC
(In reply to Johannes Huber from comment #3)
> Yes, and you please dont change keywords until all arches stable. We the kde
> herd will do it in one commit.

the test is not done at the same time for all arches. So there will be some delay between the amd64 stabilization and the ppc64 stabilization.
Comment 5 Michael Palimaka (kensington) gentoo-dev 2014-01-10 07:16:07 UTC
Maybe we should target 4.11.5 to reduce workload on arch teams?
Comment 6 rick vernam 2014-01-10 15:24:17 UTC
Where does discussion take place regarding stabilization process?
I ask b/c it seems from the outside that something is being done differently than in the past, and I wonder if it results in an inefficient release process.
For example, why should amd64 have to wait for ppc64?
I've been using Gentoo and KDE since 3.1 or so, and I've really felt like stabilization of KDE 4.10 and 4.11 has been way too slow.

Thanks - again, I understand this is not the place for this discussion, though I would be interested to know where such a discussion would be appropriate.
-Rick
Comment 7 Michael Palimaka (kensington) gentoo-dev 2014-01-11 00:22:11 UTC
(In reply to rick vernam from comment #6)
> Where does discussion take place regarding stabilization process?
> I ask b/c it seems from the outside that something is being done differently
> than in the past, and I wonder if it results in an inefficient release
> process.
> For example, why should amd64 have to wait for ppc64?
> I've been using Gentoo and KDE since 3.1 or so, and I've really felt like
> stabilization of KDE 4.10 and 4.11 has been way too slow.
> 
> Thanks - again, I understand this is not the place for this discussion,
> though I would be interested to know where such a discussion would be
> appropriate.
> -Rick

Hi,

If stabilisations have seemed a bit delayed, it is probably due to the very high workload of the arch teams. In this case, there are still unresolved bugs marked as blocking this bug.

Regarding amd64 waiting for ppc64, it is a lengthy process making changes to the entire SC. In the past, sometimes we have changed the keywords stable all at once after all arch teams were finished in order to avoid that repeated effort.
Comment 8 Agostino Sarubbo gentoo-dev 2014-01-12 18:04:44 UTC
(In reply to Michael Palimaka (kensington) from comment #5)
> Maybe we should target 4.11.5 to reduce workload on arch teams?

Yes, is fine.
Comment 9 Agostino Sarubbo gentoo-dev 2014-01-15 13:22:42 UTC
If we don't have regressions since the stabilization of 4.11 resolved in 4.11.5 I'd say to skip any other 4.11 stabilization and go ahead for the 4.12.
Comment 11 Michael Palimaka (kensington) gentoo-dev 2014-01-21 06:50:47 UTC
creffett said he wants to target 4.11.5
Comment 12 Eric F. GARIOUD 2014-02-03 22:15:34 UTC
OK, I can understand the usual no talking there!
That's true project management.
OK, I acknowledge I'am some kind of overpaid old crow!

However :

Reading about the workload on the arch teams is becomming some recurrent argument.
To this regard :

Do you *really* mean that picmi was/should have stand as a blocker for kde stabilization ????

When I read the package stabilization list, I just cannot trust it.
What does packages such as amor, kiten, kteatime and kyriads of the kind are doing in such a list ? kde-base you said ? really ?

I you actually want to speed up stabilization processes and reduce the load on the arch teams, please bring back some basic project management in there which, I make no doubt about this, would immediately start slimming down this list.
Comment 13 Johannes Huber (RETIRED) gentoo-dev 2014-02-04 10:12:03 UTC
(In reply to Eric F. GARIOUD from comment #12)
> Do you *really* mean that picmi was/should have stand as a blocker for kde
> stabilization ????
> 
> When I read the package stabilization list, I just cannot trust it.
> What does packages such as amor, kiten, kteatime and kyriads of the kind are
> doing in such a list ? kde-base you said ? really ?
> 
> I you actually want to speed up stabilization processes and reduce the load
> on the arch teams, please bring back some basic project management in there
> which, I make no doubt about this, would immediately start slimming down
> this list.

Yes kde-base is the normal category that we stabilize, as it is the set of packages which belongs to a KDE SC release. There is no alternative and please stop talking here.
Comment 14 Michael Palimaka (kensington) gentoo-dev 2014-02-05 11:54:19 UTC
Created attachment 369584 [details]
kde-4.11.5-stable-list v1

Updated stable list for 4.11.5. No blockers remain.

Eric, if you would like more information regarding our stabilisation process or would like to discuss the issue further, please feel free to join us in #gentoo-kde or or post to the gentoo-desktop mailing list.
Comment 15 Michael Palimaka (kensington) gentoo-dev 2014-02-06 15:12:20 UTC
KDE stable testers, do your magic!
Comment 16 Agostino Sarubbo gentoo-dev 2014-02-09 10:08:25 UTC
amd64 stable
Comment 17 jim.sublette@gmail.com 2014-02-09 14:10:26 UTC
amd64 looks stable here also.
Comment 18 Michael Mair-Keimberger (iamnr3) 2014-02-11 07:44:14 UTC
Installed/tested kde on both amd64 and x86. Works fine for me.
Comment 19 academicsam@gmail.com 2014-02-11 14:58:53 UTC
Upgrade (amd64) from kde 4.11.2-r2 was smooth. Daily use since Friday and no issues.
Comment 20 Andreas K. Hüttel archtester gentoo-dev 2014-02-11 17:20:39 UTC
(In reply to jim.sublette@gmail.com from comment #17)
> amd64 looks stable here also.

(In reply to Sam I am from comment #19)
> Upgrade (amd64) from kde 4.11.2-r2 was smooth. Daily use since Friday and no
> issues.

Gentlemen, PLEASE. amd64 has already been marked stable. (Hasn't ago told you anything about stable testing? :o) You are just adding noise.
Comment 21 Agostino Sarubbo gentoo-dev 2014-02-16 07:23:31 UTC
x86 stable, thanks guys