Re: [gentoo-dev] Unstable branch proposal - second round

[George Shapovalov]

Hi again

I would like to somewhat clarify my previous submission. 
So the new ebuild submission and processing procedure can be as follows:

1. new ebuild gets submitted through bugs.gentoo.org as it is now (no change)
change starts:
2. it immediately gets incorporated into the main portage tree with the 
"unstable" status (robot).
3. ebuild voting statistics are kept on bugs.gentoo.org, attached to ebuild 
submission topic. Voters have to be registered with bugs.gentoo.org as they 
are now.
4. When ebuild accumulates enough unique votes is gets "confirmed" status
Meanwhile updates and patches to ebuild are submitted as usual but whoever 
cares to correct/update it via existing mechanism.
5. if ebuild reaches second threshold of "approval wanted" votes or is of 
special interest for core group it gets reviewed and manually assigned 
"approved" status and is maintained by the core group. 
Or there can be additional layer, where ebuild just gets an approval and then 
when it gets core maintaince it gets "core" status.

Comments
It can seem like a lot of new activity for bugs.gentoo.org. However half of 
that functionality is already implemented and activity is taking place. The 
other half is happening and requires manual interaction. Ebiuld submissions 
are soaring so that some rework of bugs.gentoo.org will probably be necessary 
anyway. This looks like a way to simplify life fore core developers and 
everybody else. (When ebuilds start to be posted to mailing list instead of 
accepted procedure is the time to start thinking about the procedure I think).


George