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

[Julian Fitzell]

Hi Avi,

Sounds sensible, yes...

Julian

On Thu, Feb 3, 2011 at 6:41 PM, Avi Shefi <avishefi at gmail.com> wrote:
>
> 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.
>
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
>