[squeak-dev] [ANN] Monticello 2.0.17

> Colin,
> It would be great if you could send a brief mail to the list describing what
> made you rewrite monticello and
> what are the new features or problems that it overcomes in this new
> incarnation.
> Also, where can we find more information about the design differences
> between 2.0 and the
> previous versions?
> Thanks and congratulations!
> Cheers
>
>
>
> r.
>
>
>
>
>
>
> Colin Putney <[hidden email]>
> Sent by: [hidden email]
>
> 11/08/2008 07:27
>
> Please respond to
> The general-purpose Squeak developers list
>  <[hidden email]>
> To
> The general-purpose Squeak developers list
> <[hidden email]>
> cc
> Subject
> [squeak-dev] [ANN] Monticello 2.0.17
>
>
>
>
> Hi all,
>
> I'm very happy to announce that Monticello 2.0 is ready for download.
> This is a ground-up rewrite, using a new, more flexible and more
> performant versioning engine.
>
> http://www.wiresong.ca/static/releases/Monticello-current.zip
>
> A note about versioning numbers. In an effort to make releases easier
> to understand, I'm adopting a new scheme of version numbers for
> releases. They'll each have a major, a minor and a release number.
> Major numbers will be incremented only for major architectural changes
> or significant incompatibility with prior versions. Minor numbers will
> be incremented for significant new features, while release numbers
> will be incremented for *any* change to the code or documentation.
>
> This version, 2.0.17, is the first version of the 2.0 code base that I
> feel is ready for general use, though I've been using it for
> production code on several projects for several months now, and the
> basic versioning engine has been stable for quite some time. Version
> 2.0.17 has only been tested on Squeak 3.10, but I hope to add support
> for earlier versions of Squeak soon.
>
> Although MC 2.0 is stable and useful, there's one important feature
> that is still missing: a network enabled repository. The architectural
> differences between 1.x and 2.0 mean that the HTTP- and FTP-based
> repositories used with MC 1.x don't work well with 2.0. I'm planning
> to implement remote repositories in Monticello 2.1.
>
> As always, feedback is welcome. One thing I've learned in using MC 2
> is that it's quite different than MC 1 and it takes a while to get
> used to it - even for me. This milestone has been a long time coming,
> and I'm glad to finally reach it, but it's really just the beginning.
> I'm looking forward to seeing what becomes of it.
>
> Colin
>
>
>
> ________________________________
>
> Generally, this communication is for informational purposes only and it is
> not intended as an offer or solicitation for the purchase or sale of any
> financial instrument or as an official confirmation of any transaction. In
> the event you are receiving the offering materials attached below related to
> your interest in hedge funds or private equity, this communication may be
> intended as an offer or solicitation for the purchase or sale of such
> fund(s). All market prices, data and other information are not warranted as
> to completeness or accuracy and are subject to change without notice. Any
> comments or statements made herein do not necessarily reflect those of
> JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may
> contain information that is privileged, confidential, legally privileged,
> and/or exempt from disclosure under applicable law. If you are not the
> intended recipient, you are hereby notified that any disclosure, copying,
> distribution, or use of the information contained herein (including any
> reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any
> attachments are believed to be free of any virus or other defect that might
> affect any computer system into which it is received and opened, it is the
> responsibility of the recipient to ensure that it is virus free and no
> responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
> affiliates, as applicable, for any loss or damage arising in any way from
> its use. If you received this transmission in error, please immediately
> contact the sender and destroy the material in its entirety, whether in
> electronic or hard copy format. Thank you. Please refer to
> http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK
> legal entities.
>
>
>