| 1 |
On Monday 30 July 2001 23:00, you wrote: |
| 2 |
> On Mon, Jul 30, 2001 at 10:59:10PM +0300, Dan Armak wrote: |
| 3 |
> > Hi all, |
| 4 |
> > |
| 5 |
> > In the last few days there has been a edluge of ebuild submission on the |
| 6 |
> > mailing list. I think we need to organize this process, because some |
| 7 |
> > ebuilds get lost, and others may get grabbed by more than one developer. |
| 8 |
> > |
| 9 |
> > A final solution could be, when we introduce stable/unstable trees into |
| 10 |
> > cvs, we could add a "user" tree as well. Then ebuilds would move from |
| 11 |
> > user and unstable into stable as developers find time to test them. |
| 12 |
> > |
| 13 |
> > Until that happy time however we should make some temporary provisions. |
| 14 |
> > Is anyone handling this issue specifically as of now? |
| 15 |
> |
| 16 |
> Nope; would you be willing to grab all ebuild submissions from this mailing |
| 17 |
> list and track their addition to our Portage tree, reporting back to the |
| 18 |
> original submitter, etc? This would also include tracking testing and |
| 19 |
> informing me of people who are creating solid ebuilds so that I can set |
| 20 |
> them up with developer accounts. |
| 21 |
|
| 22 |
I wouldn't mind handling the mailing-list side of the story - grabbing all |
| 23 |
ebuilds and putting them wherever and informing whoever. But many ebuilds |
| 24 |
come through for packages I don't use and in many cases can't test. I don't |
| 25 |
think any one developer could or should handle the testing, that's why we |
| 26 |
have teams. We can have an "incoming" ebuild tree (in cvs or elsewhere) and |
| 27 |
developers could grab ebuilds that fall under their area of interest, test |
| 28 |
them and put them either in the stable or unstable cvs trees. |
| 29 |
|
| 30 |
-- |
| 31 |
|
| 32 |
Dan Armak |
| 33 |
Gentoo Linux Developer, Desktop Team |
| 34 |
Matan, Israel |
Archives