I think all this have sense in the automate it. So, I would use Gofer (if possible) to script such things.
If you have that, then call it from Hudson should be easy. But please, please, please, if we change this, we need to change all the documents and website where we explain the submit code steps. For example, there we say that if you only touch one package, no need of a slice. And even the name of the slice may change (as I read here). Cheers Mariano On Thu, May 20, 2010 at 4:19 PM, Stéphane Ducasse <[email protected] > wrote: > Me tooooooooooo > > > > I sort of prefer: > > SLICE-IssueXYZM-DescriptionOfIssue (possibly without the Issue prefix) > > That way all slices are next to each other in the inbox, and ordered by > number, which makes it much easier to find what you're looking for, either > when starting out with an issue from the bug tracker you need to integrate, > or when you're looking at which slices are in inb > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
