I was thinking about following rules to make life easier:
- a submission in PharoInbox must be a slice
- slice must be formatted like LabelOfPatch-IssueNumber
for example:
BadCharactersInPackagenames-2124
PerformWithArgsPrimFailure-2443
- reject automatically slices which don't follow the name convention

Then
- it's easy to build an interface which shows queued patches (filter by package name)
- it's easy to clean PharoInbox / delete required packages
- more visibility to the contribution process, one way of doing things (so we can automate - hudson server which test patch integration :)

What do you think ?��

Laurent Laffont

http://pharocasts.blogspot.com/
http://magaloma.blogspot.com/


On Thu, May 20, 2010 at 2:31 PM, St��phane Ducasse <stephane.ducasse@inria.fr> wrote:
Yes!
I clean but this is really tedious

stef

On May 20, 2010, at 11:57 AM, Torsten Bergmann wrote:

> Hi Stephane,
>
> the MCZ's for
> HelpSystem-Core-tbn.45
> HelpSystem-Core-tbn.43
>
> were already harvested. So shouldnt this be moved
> to treated inbox then?
>
> Thx
> T.
> --
> GRATIS f��r alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project