I think all this have sense in the automate it. So, I would use Gofer (if possible) to script such things.<br><br>If you have that, then call it from Hudson should be easy. <br><br>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). <br>
<br>Cheers<br><br>Mariano<br><br><div class="gmail_quote">On Thu, May 20, 2010 at 4:19 PM, St�phane Ducasse <span dir="ltr">&lt;<a href="mailto:stephane.ducasse@inria.fr">stephane.ducasse@inria.fr</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Me tooooooooooo<br>
<div class="im">&gt;<br>
&gt; I sort of prefer:<br>
&gt; SLICE-IssueXYZM-DescriptionOfIssue (possibly without the Issue prefix)<br>
&gt; 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&#39;re looking for, either when starting out with an issue from the bug tracker you need to integrate, or when you&#39;re looking at which slices are in inb<br>

<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Pharo-project mailing list<br>
<a href="mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.gforge.inria.fr</a><br>
<a href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project" target="_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project</a><br>
</div></div></blockquote></div><br>