| 1 |
On Sun, Dec 28, 2008 at 4:19 PM, AllenJB <gentoo-lists@××××××××××.uk> wrote: |
| 2 |
> ...Which isn't stable yet, so stable users won't see them... if there even |
| 3 |
> were any news items (I'm using portage 2.2, just sync'd and there are no |
| 4 |
> news items listed). |
| 5 |
> |
| 6 |
> I was aware of GLEP 42 but it's one of those things that seems to have |
| 7 |
> existed in some form since I started using Gentoo several years ago and has |
| 8 |
> never been implemented. |
| 9 |
> |
| 10 |
|
| 11 |
It was implemented a year ago and released only recently. |
| 12 |
|
| 13 |
> Given that it's apparently already in testing, when will developers start |
| 14 |
> using this system? (And how will it be known if there are any issues with it |
| 15 |
> if it hasn't been used on the live tree before 2.1.6 goes stable?) |
| 16 |
> |
| 17 |
|
| 18 |
Probably once portage versions that support it are stable. |
| 19 |
|
| 20 |
> And who is going to make sure that developers are using it to keep users |
| 21 |
> informed of (potential) issues? |
| 22 |
> |
| 23 |
|
| 24 |
I think the idea of some kind of 'news police' is stupid. Responsible |
| 25 |
developers will write items, have them checked by someone and then |
| 26 |
submit them. Irresponsible developers will not. |
| 27 |
|
| 28 |
> Also, will news items be posted to a web page, forum or mailing list in |
| 29 |
> addition so that they can be easily linked to from forums / irc / mailing |
| 30 |
> lists and users can see issues coming in advance if they don't sync |
| 31 |
> particularly frequently? |
| 32 |
|
| 33 |
Not at this time, but news items are easy to parse, file a bug if you |
| 34 |
think this is useful. |
| 35 |
|
| 36 |
-Alec |
| 37 |
|
| 38 |
> |
| 39 |
> AllenJB |
| 40 |
> |
| 41 |
> Zac Medico wrote: |
| 42 |
>> |
| 43 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
| 44 |
>> Hash: SHA1 |
| 45 |
>> |
| 46 |
>> AllenJB wrote: |
| 47 |
>>> |
| 48 |
>>> Hi all, |
| 49 |
>>> |
| 50 |
>>> I would like to suggest that as part of the stabilization process, |
| 51 |
>>> developers are required to (get PR to) make an announcement about any |
| 52 |
>>> manual intervention that (might be) required on a stable system. |
| 53 |
>>> |
| 54 |
>>> At the moment, this would include most blocks (eg. the recent e2fsprogs |
| 55 |
>>> block) and issues such as the firefox/xulrunner use flag issue. |
| 56 |
>>> |
| 57 |
>>> These announcements should appear on the gentoo.org front page, |
| 58 |
>>> gentoo-announce list and the announcements forum. |
| 59 |
>>> |
| 60 |
>>> The announcement should appear before the first (affected) architecture |
| 61 |
>>> stabilizes the package. |
| 62 |
>>> |
| 63 |
>>> I think this would help alleviate the load of those helping in the |
| 64 |
>>> forums, irc and mailing lists as well as probably reduce the number of |
| 65 |
>>> unnecessarily created bugs. |
| 66 |
>>> |
| 67 |
>>> Obviously the need for these announcements will be drastically reduced |
| 68 |
>>> with the stabilization of portage 2.1.6 / 2.2, but I suspect there will |
| 69 |
>>> still be things which they can not handle automatically. |
| 70 |
>>> |
| 71 |
>>> AllenJB |
| 72 |
>>> |
| 73 |
>>> |
| 74 |
>> |
| 75 |
>> You can use GLEP 42 news items which are supported with portage-2.1.6: |
| 76 |
>> |
| 77 |
>> http://www.gentoo.org/proj/en/glep/glep-0042.html |
| 78 |
>> - -- |
| 79 |
>> Thanks, |
| 80 |
>> Zac |
| 81 |
>> -----BEGIN PGP SIGNATURE----- |
| 82 |
>> Version: GnuPG v2.0.9 (GNU/Linux) |
| 83 |
>> |
| 84 |
>> iEYEARECAAYFAklYEiAACgkQ/ejvha5XGaOD4ACgi11yGFU4Uh4tSz5qhZnsK87n |
| 85 |
>> DesAoJc/L/WdORMZDKua+S9RbcrZeP4N |
| 86 |
>> =gdrX |
| 87 |
>> -----END PGP SIGNATURE----- |
| 88 |
>> |
| 89 |
> |
| 90 |
> |
| 91 |
> |
Archives