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

[Dale Henrichs]

Avi,

There have been a number of package naming conventions over the years, but unfortunately none of the conventions have been enforced by the GUI, so folks have been free to create mcz files of all sorts ...

Now technically Monticello itself does not care about the name of the mcz file ... any old name will do, but it is useful for humans and tools to be able to interpret the file name as an indication of the contents of the mcz file and as a result it is unfortunate that the file name and mcz contents are not synchronized ...

For your personal use only it almost doesn't matter what names you use, however, you have to be aware that Gofer/Monticello can get confused if you have "private" mcz files in your package-cache that inadvertently match a pattern...

Dale

On Feb 4, 2011, at 5:54 AM, Avi Shefi wrote:

Thank you.
I'm just trying to keep track of all the changes I'm doing while working on issues.
It seems like you have to work your way around this, since Monticello doesn't provide you with a tool/methodology for this use case.


Avi.

On Fri, Feb 4, 2011 at 3:33 PM, Dale Henrichs <dhenrich at vmware.com<mailto:dhenrich at vmware.com>> wrote:
Avi,

I am suspicious about using a '-' to separate the author name and issueXXX .... I don't recall the exact rules that Gofer/Monticello uses in interpreting mcz file names, but I think that using the '-' where you suggest will cause issueXXX to be interpreted as the author name ... also you need to include an integer count of some sort before the .mcz extension or you will get into even more trouble.

I have had success over the years using the following pattern:

 Seaside-Core.IssueXXX-<initials>.<count>.mcz

This pattern will not be inadvertently interpreted as a Seaside-Core package by Gofer/Monticello and is very readable.

Dale

On Feb 3, 2011, at 10:41 AM, Avi Shefi 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.

<ATT00001..txt>

_______________________________________________
seaside-dev mailing list
seaside-dev at lists.squeakfoundation.org<mailto:seaside-dev at lists.squeakfoundation.org>
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

<ATT00001..txt>