[Seaside-dev] [Seaside] Package conventions & monticello versioning

Avi Shefi avishefi at gmail.com
Thu Feb 3 18:41:34 UTC 2011


Hi,
Assuming you are working on fixing several issues on the Seaside-Core
package, what's the best way to work on issues & patches using Monticello?
The best option I can think of is:
1) do your work on the issue
2) save it to a mcz file named: Seaside-Core-<initials>-issueXXX.mcz
3) reload the original ancestor from which you started
4) keep working on other issues without having the code of the previous fix
inside the image

This way, if you make multiple changes on the same package you will be able
to send each one of them in a different file, without getting the code
mixed-up along the fixes you submit.

Is this the right way?


Thanks,
Avi.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20110203/0d8a9499/attachment.htm


More information about the seaside-dev mailing list