On 12.08.2009, at 16:47, Ken Causey wrote:

> On Wed, 2009-08-12 at 14:49 +0200, Bert Freudenberg wrote:
>> I just merged a Monticello fix from the inbox (thanks Bernhard!) to
>> the trunk. Now that this package is dealt with, what do we do?  
>> Perhaps
>> we need an "inbox-merged" repository where we can move these  
>> packages?
>> Or possibly two repositories for accepted and rejected packages? Can
>> all developers move versions between repositories, or only admins?
>>
>> - Bert -
>
> I have to say I've wondered about this myself.
>
> Regarding 'who' moves them:  I assume you are asking about policy  
> rather
> than technical capability.  Unless you are doing this some way I'm not
> aware of anyone who has write capability can do it.

AFAICT only project admins can delete or move versions.

>  In terms of policy
> I would be comfortable mapping it to capability, which is to say that
> all core-devs can move packages from inbox to trunk.

Right. I'd add a "devs can move" flag to SSAccessPolicy to allow  
developers to move versions out of a repository that has this flag  
enabled. Unless Adrian thinks that's a dumb idea ;)

Then I'd enable it for the inbox. So packages could be moved out of  
it, but not out of the trunk, which I'd find safer.

Packages should be moved from the inbox only to the "treated" repo,  
rather than directly into the trunk, IMHO. This is so it's clear in  
the trunk repo which core developer uploaded a version. Possibly this  
should be enforced by having two flags instead of one (devCanMoveIn  
and devCanMoveOut).

- Bert -


> That said, you bring up a good point regarding tracking what has been
> done.  As it stands you have to see what is in inbox and then look at
> the listing in trunk to see if that file is in the listing there.  Of
> course that ignores the possibility that it's not actually in the
> ancestry of the current latest version and is ultimately overlooked  
> that
> way.  It would also be useful to provide some easy feedback for those
> submitting issues to the inbox indicating when their submission has  
> been
> accepted.  Perhaps it's time for our own SqueakSource branch.
>
> Ken
>