| 1 |
2012/12/13 Tomáš Chvátal <tomas.chvatal@×××××.com>: |
| 2 |
> |
| 3 |
> But there is one big ass but. We have some packages that were |
| 4 |
> stabilised last time few year back and they provide multiple testing |
| 5 |
> versions on top of that. |
| 6 |
> Who is the one to deterimine which one should go stable and which to get rid of? |
| 7 |
> We had some humble tryouts to create automatic stabilisation request |
| 8 |
> which didn't turn out exactly well as most of the maintainers had to |
| 9 |
> actually do more work ;-) |
| 10 |
> |
| 11 |
> |
| 12 |
I did not ment to send this! It is mail WIP I wanted to store in draft |
| 13 |
folder... anyway so let me expand here: |
| 14 |
|
| 15 |
We need some metadata.xml tag that would allow automatic |
| 16 |
stabilisations without maintainer step so we can speed up things at |
| 17 |
some pace. |
| 18 |
Then we need some nice page displaying results of possible |
| 19 |
stabilisations, where members of Arch teams or AT guys would open up |
| 20 |
new bugs where ccing the respective archs. |
| 21 |
|
| 22 |
Apart from that I dunno what exactly ATs would strive for so Ago, or |
| 23 |
anyone else please show up some ideas :-) |
| 24 |
|
| 25 |
Cheers |
| 26 |
|
| 27 |
Tom |
Archives