Philippe,<br> Giovanni is working hard to give us a workflow.<br>I think you are posing the problems in the wrong way.<br>A package without mantainer is in a very sick state.<br><br>If we want to continue developing in Squeak, we must find a solution together.
<br>If you have a better idea please expose it, but critizing without a suggestion is useless.<br><br><br><br><div><span class="gmail_quote">On 10/16/06, <b class="gmail_sendername">Philippe Marschall</b> <<a href="mailto:philippe.marschall@gmail.com">
philippe.marschall@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2006/10/16, Giovanni Corriga <<a href="mailto:giovanni@corriga.net">
giovanni@corriga.net</a>>:<br>> Il giorno lun, 16/10/2006 alle 12.50 +0200, Philippe Marschall ha<br>> scritto:<br>> > 2006/10/16, Giovanni Corriga <<a href="mailto:giovanni@corriga.net">giovanni@corriga.net
</a>>:<br>> > > Il giorno lun, 16/10/2006 alle 10.55 +0200, Lukas Renggli ha scritto:<br>> > > > > This proposal is based on two points:<br>> > > > > - decentralization of development
<br>> > > > > - fixed duration of iterations ("timeboxing")<br>> > > ><br>> > > > Sounds like a good proposal, however I see a couple of problems that<br>> > > > you don't adress:
<br>> > > ><br>> > > > - How to manage the code and the changes? Most changes related to<br>> > > > Compiler, CompiledMethod, Behavior, Traits, etc. cannot be loaded<br>> > > > using Monticello.
<br>> > ><br>> > > How did these things get managed in 3.9? By changeset and DoIts? Will it<br>> > > be possible to keep doing this for 3.10, until we develop better tools?<br>> > > (MC2 maybe?)
<br>> > > On the other hand, I know this was pretty ugly for Marcus and Stef.<br>> > > Would reducing the scope of the changes to manageable bites solve this,<br>> > > at least in part?<br>> > >
<br>> > > > - What to do with code that is not properly packaged yet? How to pass<br>> > > > code over to another package?<br>> > ><br>> > > Isn't all code in the image segmented into packages?
<br>> ><br>> > In theory yes. In praxis no. You can't just go there and unload eToys.<br>><br>> if we want eToys to be maintained, then the first task of the eToys team<br>[...]</blockquote></div><br>--
<br>"Just Design It" -- GG<br>Software Architect<br><a href="http://www.objectsroot.com/">http://www.objectsroot.com/</a>