As a sketch on how we can do this without producing too much image generation work -
At the end of one cycle we should release a VI4 image marked as experimental, along with the VI3 for general use. Either on the next cycle or the one after, we run the alpha cycle releasing VI4 images, instead of VI3 ones. Assuming no problems crop up, we make the release using VI4, with VI3 as backup.
Daniel
Tim Rowledge tim@sumeru.stanford.edu wrote:
"Andreas Raab" andreas.raab@gmx.de wrote:
I would VERY much encourage having "parallel" versions of VI3 and VI4 images for a couple of releases.
I think that's a very reasonable idea.
tim
Tim Rowledge, tim@sumeru.stanford.edu, http://sumeru.stanford.edu/tim Oxymorons: Silent scream _______________________________________________ Squeakfoundation mailing list Squeakfoundation@lists.squeakfoundation.org http://lists.squeakfoundation.org/listinfo/squeakfoundation
Hi all! I'd like to do a very small request. I have done a very small Log Engine You can see it at < http://sourceforge.net/projects/cat/ > < http://osdn.dl.sourceforge.net/sourceforge/cat/LogEngine1.0.st.gz >
I'd like to put it in the next Squeak Base image, because I think it can be a very useful tool for developers. It works fine with headless images, and are only 4 classes (I can reduce them to 3 if needed ;) It shines with web servers (like seaside) because you can have multiple log files, and image restart is handled in a very smart fashion: Log files are automatically reopened when the image is launched again. The code is only 9Kb.
Class Comment:
I am a LogClient for Squeak! I am similar to log4j but simpler.
A Sample usage is lc := LogClient getInstance: 'Client'. lc debug:'test1'. lc info:'test2'.
When you create a LogClient, you must use the getInstance: method, passing a "Category Name" used to create a special category log file.
LogClient features: + Integrated con Preferences (debug panel) + Can output on file and on Transcript on demand + Can print the method where the line is called + Can disable the debug level (only this for the meantime, sorry). + Easy to extend
On Saturday, July 12, 2003, at 11:27 PM, Daniel Vainsencher wrote:
[about parallel relases] [...] At the end of one cycle we should release a VI4 image marked as experimental, along with the VI3 for general use. Either on the next cycle or the one after, we run the alpha cycle releasing VI4 images, instead of VI3 ones. Assuming no problems crop up, we make the release using VI4, with VI3 as backup.
Daniel
Hi all!
Giovanni Giorgi jj@objectsroot.com wrote:
Hi all! I'd like to do a very small request. I have done a very small Log Engine You can see it at < http://sourceforge.net/projects/cat/ > < http://osdn.dl.sourceforge.net/sourceforge/cat/LogEngine1.0.st.gz >
I'd like to put it in the next Squeak Base image, because I think it can be a very useful tool for developers.
[SNIP]
Yes, I agree that this should be in the "Basic" Squeak. It still should be a package though.
And while we are on that subject (or something): Should I create categories "Minimal", "Basic" and "Full" and put them under... some nice top category?
And are there other categories we would like to have?
regards, Göran
On Sunday, July 27, 2003, at 11:32 AM, goran.krampe@bluefish.se wrote:
[about LogEngine] Yes, I agree that this should be in the "Basic" Squeak. It still should be a package though.
I can mantian it along with my other suffs at http://cat.sf.net.
And while we are on that subject (or something): Should I create categories "Minimal", "Basic" and "Full" and put them under... some nice top category? And are there other categories we would like to have?
I think a minimal image will be a nice thing, but only if it will not require so-much effort. The "Minimal" image will retain all the programming stuff (like Interpreter, Compiler and so on)? For example, one would install a minimal seaside (or wiki) server without the need of manually remove the other programs (like sound and midi support and so on)...
bye bye
squeakfoundation@lists.squeakfoundation.org