May 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] SVN vs Git for the cogvm

by Igor Stasenko

On 3 May 2011 17:42, Torsten Bergmann <astares(a)gmx.de> wrote: >>if so, the merge will always be more complicated and the differences >>will be more and more... > > The more you branch/fork/clone the more you have to manage. Does switching > Â to SVN with one "trunk" help? Sorry couldnt resist ;) I disagree. Process management lies in social plane. To my own experience it is completely orthogonal to what tools we using. > > Bye > T. > -- > NEU: FreePhone - kostenlos mobil telefonieren und surfen! > Jetzt informieren: http://www.gmx.net/de/go/freephone > > -- Best regards, Igor Stasenko AKA sig.

May 3, 2011

[Pharo-project] [OT] Meeting in Europe

by Torsten Bergmann

>eastern Europe Didnt know that Europe is that small, could you be more exact about country/place. Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

May 3, 2011

[Pharo-project] [OT] Meeting in Europe

by HernÃ¡n Morales Durand

Hi all, Sorry for the OT, I'm during this month in eastern Europe, if someone would like to meet and talk about the Smalltalk world just write me here or by private e-mail. Cheers, -- HernÃ¡n Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

May 3, 2011

[Pharo-project] SVN vs Git for the cogvm

by Torsten Bergmann

>if so, the merge will always be more complicated and the differences >will be more and more... The more you branch/fork/clone the more you have to manage. Does switching to SVN with one "trunk" help? Sorry couldnt resist ;) Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

May 3, 2011

Re: [Pharo-project] add temp does not add the temp in 1.3 13179

by StÃ©phane Ducasse

it does not work in OB in 1.3 nor in the plain default browser. Now in plain 1.3-core it is working in the default browser. So this is probably linked with a package loaded in the dev image. I was thinking OC? Stef On May 3, 2011, at 2:30 PM, Johan Brichau wrote: > > On 03 May 2011, at 10:14, Mariano Martinez Peck wrote: > >> aha.... I didn't try that ;) >> So...in 1.2.1 adding from a browser does work, but not from the debugger? >> And in 1.3 none of them? > > > I don't know about 1.3 but it's one of the things I started to notice about 1.2.1 this week. > In the browser, it works fine.

May 3, 2011

[Pharo-project] Cog open-source process [WAS] Re: [Vm-dev] Re: SVN vs Git for the cogvm

by Mariano Martinez Peck

On Tue, May 3, 2011 at 5:06 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > On 3 May 2011 16:57, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Instead of discussing where to commit I would discuss how to merge and > > define the process with VMMaker. I mean, how WE (the community) and > Eliot, > > manage the development of Cog (the VMMaker part). > > > > Take as an example today. There is "our branch" which is in > > VMMaker-oscog-XXX.NUMBER. For example, the last one is > > VMMaker-oscog-MarianoMartinezPeck.66. > > Eliot commits are in (since now) VMMaker.oscog-eem.56. Who merges? > Eliot? > > us? Would Eliot took the result of the merge as his next base version? > > Because suppose I merge it, and I get > VMMaker-oscog-MarianoMartinezPeck.67 > > which is the merge with VMMaker.oscog-eem.56. Will Eliot take that > version > > and follow his code from that one? > > or he will release VMMaker.oscog-eem.5N tomorrow, and we will need to > merge > > with VMMaker-oscog-MarianoMartinezPeck.6N? if so, the merge will always > be > > more complicated and the differences will be more and more... > > > > As to me the rule is simple: > - before making new release (or snapshot) an author should merge with > latest available version. > > it means, whoever are responsible for update, he should merge previous > work (or just base his work on > latest available version). > > This btw, a typical rule for group development. I've been followed it > since using CVS, then SVN > in many other project i were involved. > Its simple and straightforward. > Why we should invent something else? > Because it is not fun to do the same merge over and over. And the merge will be each time bigger and bigger. This is why I would like to know whether Eliot will take the result of the merge or not as the base of his next version > > Okay. So, Mariano, it is your call. Please do the merge eem.56 + > MarianoMartinezPeck.66 > and then create new ConfigurationOfCog, so next time we will build new > VMs based on this version. > > mmm I don't promise anything. I don't feel brave enough. My unique commit to VMMaker (.66) was a simple change in VMMakerTool to avoid the WorldMenu. There are more than 10 commits between them and none of them done by me. So...I am not sure I will be able to do it or to do it correctly (as opposite to CMakeVMMaker where I feel more confortable to commit and merge). Moreover one of the commits of Dave changed almost all classes (I am not saying it is bad ehh!!)...so the merge doesn't look easy. I would appreciate if you can take a look this time. Otherwise, I will try to do it along the week. Cheers mariano > Cheers > > > > Mariano > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Mariano http://marianopeck.wordpress.com

May 3, 2011

Re: [Pharo-project] SVN vs Git for the cogvm

by Igor Stasenko

On 3 May 2011 16:57, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Instead of discussing where to commit I would discuss how to merge and > define the process with VMMaker.Â I mean, how WE (the community) and Eliot, > manage the development of Cog (the VMMaker part). > > Take as an example today. There is "our branch" which is in > VMMaker-oscog-XXX.NUMBER. For example, the last one is > VMMaker-oscog-MarianoMartinezPeck.66. > Eliot commits are in (since now) VMMaker.oscog-eem.56.Â Who merges? Eliot? > us? Would Eliot took the result of the merge as his next base version? > Because suppose I merge it, and I get VMMaker-oscog-MarianoMartinezPeck.67 > which is the merge with VMMaker.oscog-eem.56. Will Eliot take that version > and follow his code from that one? > or he will release VMMaker.oscog-eem.5N tomorrow, and we will need to merge > with VMMaker-oscog-MarianoMartinezPeck.6N?Â if so, the merge will always be > more complicated and the differences will be more and more... > As to me the rule is simple: - before making new release (or snapshot) an author should merge with latest available version. it means, whoever are responsible for update, he should merge previous work (or just base his work on latest available version). This btw, a typical rule for group development. I've been followed it since using CVS, then SVN in many other project i were involved. Its simple and straightforward. Why we should invent something else? Okay. So, Mariano, it is your call. Please do the merge eem.56 + MarianoMartinezPeck.66 and then create new ConfigurationOfCog, so next time we will build new VMs based on this version. > Cheers > > Mariano -- Best regards, Igor Stasenko AKA sig.

May 3, 2011

Re: [Pharo-project] SVN vs Git for the cogvm

by Mariano Martinez Peck

Instead of discussing where to commit I would discuss how to merge and define the process with VMMaker. I mean, how WE (the community) and Eliot, manage the development of Cog (the VMMaker part). Take as an example today. There is "our branch" which is in VMMaker-oscog-XXX.NUMBER. For example, the last one is VMMaker-oscog-MarianoMartinezPeck.66. Eliot commits are in (since now) VMMaker.oscog-eem.56. Who merges? Eliot? us? Would Eliot took the result of the merge as his next base version? Because suppose I merge it, and I get VMMaker-oscog-MarianoMartinezPeck.67 which is the merge with VMMaker.oscog-eem.56. Will Eliot take that version and follow his code from that one? or he will release VMMaker.oscog-eem.5N tomorrow, and we will need to merge with VMMaker-oscog-MarianoMartinezPeck.6N? if so, the merge will always be more complicated and the differences will be more and more... Cheers Mariano On Tue, May 3, 2011 at 4:45 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 3 May 2011 16:36, Toon Verwaest <toon.verwaest(a)gmail.com> wrote: > > On 05/03/2011 07:57 AM, StÃ©phane Ducasse wrote: > >> > >> LOL > >> > >> But I can tell that I hated when sbe changed under my feets from svn to > >> git. > > > > Why the hate? See it as an opportunity to grow ;) > > > > > Personally, i really like a > git status > command.. > > It is much more convenient than analogous to svn or cvs. > I am also like that i can do crazy things with branches/sources , and > be sure that nothing is lost > and i can always revert things back to normal if i break something. > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Mariano http://marianopeck.wordpress.com

May 3, 2011

Re: [Pharo-project] [OT] Meeting in Europe

by StÃ©phane Ducasse

what is eastern europe? we are at one hour from paris so if you drop by let us know Stef On May 3, 2011, at 5:45 PM, HernÃ¡n Morales Durand wrote: > Hi all, > > Sorry for the OT, I'm during this month in eastern Europe, if someone > would like to meet and talk about the Smalltalk world just write me > here or by private e-mail. > Cheers, > > -- > HernÃ¡n Morales > Information Technology Manager, > Institute of Veterinary Genetics. > National Scientific and Technical Research Council (CONICET). > La Plata (1900), Buenos Aires, Argentina. > Telephone: +54 (0221) 421-1799. > Internal: 422 > Fax: 425-7980 or 421-1799. >

May 3, 2011

Re: [Pharo-project] SVN vs Git for the cogvm

by Igor Stasenko

On 3 May 2011 16:36, Toon Verwaest <toon.verwaest(a)gmail.com> wrote: > On 05/03/2011 07:57 AM, StÃ©phane Ducasse wrote: >> >> LOL >> >> But I can tell that I hated when sbe changed under my feets from svn to >> git. > > Why the hate? See it as an opportunity to grow ;) > > Personally, i really like a git status command.. It is much more convenient than analogous to svn or cvs. I am also like that i can do crazy things with branches/sources , and be sure that nothing is lost and i can always revert things back to normal if i break something. -- Best regards, Igor Stasenko AKA sig.

May 3, 2011