This came to my attention last night as I made a modification to MC1.5 in order to work with Pharo packages. ----- Forwarded message from Keith Hodges <keith_hodges@yahoo.co.uk> ----- To: The general-purpose Squeak developers list <squeak-dev@lists.squeakfoundation.org> From: Keith Hodges <keith_hodges@yahoo.co.uk> Date: Fri, 27 Jun 2008 17:18:56 +0100 Subject: [squeak-dev] Monticello version numbers Many do not know that Monticello 1.5 supports more complicated/natural version numbering schemes. Versions can be... 100 1.0.20 b523057e.606b.464b (abbreviated UUID with: $- replaced by $.) so.... this means... PLEASE DONT USE $. in your author initials when saving MC packages!!!!!! this has been a public service announcement Keith ----- End forwarded message ----- I don't know how or if it conflicts with Pharo dev policy. I don't see any requirement to use author names like lukas.renglli, but it happened. I don't think this version number scheme has been actually tested, despite what Keith said; it gave me a walkback when the version number was accidentally detected as 'renglli.271'. Does this interfere with some pharo policy? If so, any suggestions on a remedy? How do you envision MC package naming working once Author class is created? Keith's motivation behind the change: Seaside2.8 used version names with periods, but inside the package name. He made it more first-class UUID versions were a request by Chris Mueller -- Matthew Fulmer -- http://mtfulmer.wordpress.com/