[Newbies] Frequency of saving changes to Monticello?

[Grant Rettke]

Your workflow might look something like:
1. Create a category for your business logic.
2. Create a category for the tests for (step 1).
3. Create a business logic class.
4. Create a business logic test class.
5. Run the test, it fails, implement that functionality.
6. Save to Monticello.

On 1/10/07, stephane ducasse <stephane.ducasse at free.fr> wrote:
> In Squeak, the system logs ***every*** code you edit and compile. You
> can have a look at what you did by opening
> the "recover last changes"
>
> So normally you should never lose any code. Now it is a good practice
> to commit each time you broke and fix
> your test. Usually I write tests (red), then make them green and
> commit. :)
> But this is in the great days of hacking.
>
> Stef
>
> On 10 janv. 07, at 19:28, Grant Rettke wrote:
>
> > Hi,
> >
> > With Subversion the motto is "commit frequently". I commit after
> > nearly every change, no matter how small. What is the
> > motto/approach/style for committing to Monticello your changes to your
> > classes?
> >
> > Regards,
> >
> > Grant
> > _______________________________________________
> > Beginners mailing list
> > Beginners at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/mailman/listinfo/beginners
> >
>
> _______________________________________________
> Beginners mailing list
> Beginners at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>