Ok, I've blessed as release the version used in pharo dev from the following
Configs:

ConfigurationOfPharoMorphicExtras
ConfigurationOfPharoNonCore
ConfigurationOfPharoSound
ConfigurationOfRefactoringBrowser
ConfigurationOfScriptManager
ConfigurationOfShout
ConfigurationOfXMLSupport
ConfigurationOfOCompletion
ConfigurationOfNile
ConfigurationOfObjectMetaTools


These ones were already blessed:

ConfigurationOfAutotest
ConfigurationOfProfStef
ConfigurationOfXMLWriter
ConfigurationOfAutomaticMethodCategorizer


These one left to be blessed:

ConfigurationOfOmniBrowser  (I'd like not to release it until we get that
last issue fixed)
ConfigurationOfMemoryMonitor  (Alex, can the actual version be released?)
ConfigurationOfPharo (I'd like not to release it until everything is ready)



On Sun, Mar 13, 2011 at 7:45 AM, Mariano Martinez Peck <
marianop...@gmail.com> wrote:

>
>
> On Sun, Mar 13, 2011 at 7:19 AM, Guillermo Polito <
> guillermopol...@gmail.com> wrote:
>
>>
>>
>> On Sat, Mar 12, 2011 at 4:19 PM, Mariano Martinez Peck <
>> marianop...@gmail.com> wrote:
>>
>>> So....here is the list of things I guess are pending:
>>>
>>> 1) "Release" all configurations included in Pharo (this is,
>>> ConfigurationOfPharo and all it dependencies). I mean, we should NOT use or
>>> depend on #development versions.
>>>
>>
>> I'll take a look at this...  I had two weeks without programming, and I
>> can't sleep now without doing something :P
>>
>
> please, be my guest :)
>
>
>>
>>
>>> 2) Update the one click image to use latest cog images and "pharo
>>> prepared vms". There are some issues regarding this...
>>> 3) Write down all the things/summary done in Pharo 1.2
>>> 5) Update  SystemVersion current -->> Pharo1.2rc2 of 27 January 2011
>>> update 12340
>>> 6) Condense sources? condense changes?  #cleanUpForRelease
>>>
>>> Cheers
>>>
>>> Mariano
>>>
>>
>>
>

Reply via email to