1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 20/08/13 02:19 PM, William Hubbs wrote: |
5 |
> All, |
6 |
> |
7 |
> I'm not really sure what the answer to this problem is, so I want |
8 |
> to know what the group thinks about how we can handle it. |
9 |
> |
10 |
> During the last release of OpenRC, I learned that people *do* run |
11 |
> production servers on ~arch. I asked about it and was told that |
12 |
> the reason for this is bitrot in the stable tree. |
13 |
> |
14 |
> My question is, how can we improve our stabilization |
15 |
> procedures/policies so we can convince people not to run production |
16 |
> servers on ~arch and keep the stable tree more up to date? |
17 |
> |
18 |
> Thanks, |
19 |
> |
20 |
> William |
21 |
> |
22 |
|
23 |
I see a few issues with ~arch -> table migrations: |
24 |
|
25 |
#1 - things just sit in ~arch. The auto-stablereq script should help |
26 |
with this one I think; we should give it some time to see if it works out. |
27 |
|
28 |
#2 - the inter-related'ness of packages -- sending one package from |
29 |
~arch to stable is often not sufficient, rather that package and a |
30 |
whole set of (r)deps all need to go to stable at the same time, and |
31 |
those packages are not necessarily managed by the same herd or team. |
32 |
Because of this I can see why the solution to #1 ends up getting |
33 |
blocked. I don't have a solution for this one; we need to figure out |
34 |
better ways of dev's working together to push packages to stable more |
35 |
often; maybe more tracker bugs? dunno... |
36 |
|
37 |
Of course, developer communication only improves things when there |
38 |
aren't any bugs that block one package and therefore the entire set of |
39 |
(r)deps. It could be that this is the real root cause of ~arch holdbacks. |
40 |
|
41 |
|
42 |
-----BEGIN PGP SIGNATURE----- |
43 |
Version: GnuPG v2.0.20 (GNU/Linux) |
44 |
|
45 |
iF4EAREIAAYFAlITtT8ACgkQ2ugaI38ACPDFvQEAvMsB/0+l/upCsHF4Fo1wDcar |
46 |
RWd8jh+qtRBY7vnL/0wA/0c0jNpUva5QY4VfLFlI0oO3Zyeui2yh6JaVzST6Gqar |
47 |
=6AqJ |
48 |
-----END PGP SIGNATURE----- |