March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Log of the retrospective analysis from Pharo 2.0

by Ben Coman

StÃ©phane Ducasse wrote: > Hello happy pharoers > > Since Pharo2.0 will be released pretty soon, we led a retrospective analysis to learn and improve our process. > Here are the notes taken by clement from the meeting led by esteban with all the team here. > > Pharo 2.0 Retrospective meeting by Esteban Lorenzo > > The Good > All great initiatives and really adds a lot to the professional feel of Pharo. Nice to see such a review. > The Bad > > Long development cycle (1 year), Focus problem : most things works but are not finished > We should have a 1 to 2 months cycle with a part where we introduce new things and a part where we only fix bugs. At the end of each cycle, Pharo should be stable. As a user this is really interesting and attractive. Here is a related article on Software Inventory [1] by Joel of Trello & Fogbugz fame. Some of the philosophy is a little strong for me, but mostly it sounds right. [1] http://www.joelonsoftware.com/items/2012/07/09.html. With a faster release cycle, users might find 'major.minor.bugfix' semantic versioning more useful. Perhaps if submitted slices could be tagged new-feature or bug-fix that would help the CI and integrator automation. The CI could automatically take care of semantic versioning the builds, replacing the current #20534 type of build name. I understand that limited resources is an impediment to managing multiple branches, but perhaps it gets easier with CI and integration automation, such that only bugfixes directly advance the mainline while new-features are tested against the mainline and various combinations of each other. > Each cycle should have a retrospective meeting. We should pair program every friday afternoons on Pharo improvements. > New failing test in Jenkins, Red builds on jenkins stayed forever > We need a clear separation between pharo and pharo contribution both on smalltalk hub and Jenkins to have a clean green front end to show to end users > In case of a red build, we need a quick meeting to pick someone to fix it. > We need to fix the red builds on the friday' mandatory mini sprint > Perhaps if a build is red for too long there can be a default mechanism to revert the last change. cheers -ben

March 16, 2013

[Pharo-project] https://pharo.fogbugz.com : can I have an account there?

by Stephan Eggermont

And me too? Stephan

March 15, 2013

[Pharo-project] grease-core extensions that exist in pharo 2.0

by Tudor Girba

Hi, (sorry for the cross-post, but I was not quite sure where to send it) In Grease-Core, there are a couple of String extensions (trimBoth, trimBoth:, trimLeft, trimLeft: trimRight, trimRight:, trimLeft:right:) that already exist in Pharo 2.0. I would like to remove them and let platform-specific extension packages add them if needed. Unfortunately, I do not have an account for the www.squeaksource.com/Seaside30.html repository. Can anyone give me access to the repository? Cheers, Doru -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

March 15, 2013

Re: [Pharo-project] Log of the retrospective analysis from Pharo 2.0

by Tudor Girba

Thanks for the report. It's great to see you doing a retrospective. I hope you will do it regularly :). Cheers, Doru On Mar 15, 2013, at 9:49 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hello happy pharoers > > Since Pharo2.0 will be released pretty soon, we led a retrospective analysis to learn and improve our process. > Here are the notes taken by clement from the meeting led by esteban with all the team here. > > Pharo 2.0 Retrospective meeting by Esteban Lorenzo > > The Good > â¢ BugTracker as Backlog > â¢ Sprint / mini - sprint / pair programming > â¢ Locking changes before release > â¢ Community getting involved > â¢ Web doc > â¢ jenkins : the monkey, zeroconf script > â¢ Smalltalkhub > The Bad > â¢ Trello > â¢ We need a place to backlog what to do. We should use the FogBugz bug tracker > â¢ Long development cycle (1 year), Focus problem : most things works but are not finished > â¢ We should have a 1 to 2 months cycle with a part where we introduce new things and a part where we only fix bugs. At the end of each cycle, Pharo should be stable. Each cycle should have a retrospective meeting. We should pair program every friday afternoons on Pharo improvements. > â¢ New failing test in Jenkins, Red builds on jenkins stayed forever > â¢ We need a clear separation between pharo and pharo contribution both on smalltalk hub and Jenkins to have a clean green front end to show to end users > â¢ In case of a red build, we need a quick meeting to pick someone to fix it. > â¢ We need to fix the red builds on the friday' mandatory mini sprint > â¢ Integrator bottleneck > â¢ More intelligent monkey > â¢ better tools (spec tool idea from Esteban where you just click accept and the slce is integrated) > â¢ New features accepted only with tests and comments > â¢ Only slices accepted no more change sets > â¢ Pointless discussions on the mailing list > â¢ Documentation : class comments, ... > â¢ do not integrate undocumented features > â¢ add code critics features in the monkey > â¢ change the template of the class comment > The Ugly > â¢ 2 weeks lost : broken image during ESUG > â¢ 2 weeks lost : beginning of the year : no VM working, jenkins couldnât test things. > â¢ -> we will staged development. > â¢ Communication failed : team and community > â¢ For new features, send more mails to the Pharo or RMOD mailing list and less to the RMOD mailing list or private mails between few people > â¢ Infrastructure > â¢ VM : stability > â¢ Stability : 1 VM release per Pharo release. 1 official Vm which is not just some VM from a build. > â¢ Stability : VM not release if an acceptance list does not work with the VM. The acceptance list is for now all the Pharo core, seaside and Moose > -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

March 15, 2013

Re: [Pharo-project] Keyboard Shortcuts and Menus

by Esteban Lorenzano

wow... really cool... we need that in 3.0 :) On Fri, Mar 15, 2013 at 10:05 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > I did a quick experiment to see if the shortcuts can be displayed nicely ;) > > Anyway esteban did already a hell of a job to add all the keys, still the > menus and shortcuts will need some more love in 3.0. > > >

March 15, 2013

Re: [Pharo-project] https://pharo.fogbugz.com : can I have an account there?

by Camillo Bruni

On 2013-03-15, at 21:10, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Can I get an account, too? done > Doru > > > On Mar 15, 2013, at 5:31 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> >> On 2013-03-15, at 17:25, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: >> >>> Will the bugtracker be open one day? >>> >>> Can I have an account? >> >> you're in, request a new password when you connect and everything should work. >> >>> >>> Esteban A. Maringolo >>> >>> >>> 2013/3/8 phil(a)highoctane.be <phil(a)highoctane.be>: >>>> 'k thx. >>>> >>>> I do use FBZ since quite a while (v3), so good :-) >>>> >>>> 2013/3/8 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >>>>> For now we are just migrating, but soon the doors will be open : >>>>> >>>>> Steps needed before official announcement: >>>>> - Migrate all issues ( we are currently at 7026 issues migrated) >>>>> - Deploy the Penelope website (to register easily to the issue tracker and >>>>> have a list of open issues) >>>>> - Fix dependency between issues (blockedOn:) >>>>> - Polish a bit statuses in fogbugz >>>>> The plan is to announce it at the same time that the announcement of >>>>> Pharo2.0 release :) >>>>> >>>>> Ben >>>>> >>>>> On Mar 8, 2013, at 11:13 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>> >>>>> patience, patience :D, we will announce that pretty soon. >>>>> until then you can still report on the old issue tracker. >>>>> >>>>> On 2013-03-08, at 10:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>>> >>>>> How to do? >>>>> >>>>> Guess bug reporting occurs there now. >>>>> >>>>> Regards, >>>>> Phil >>>>> >>>>> >>>>> >>>>> >>>> >>> >> >> > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > >

March 15, 2013

[Pharo-project] Keyboard Shortcuts and Menus

by Camillo Bruni

I did a quick experiment to see if the shortcuts can be displayed nicely ;) Anyway esteban did already a hell of a job to add all the keys, still the menus and shortcuts will need some more love in 3.0.

March 15, 2013

[Pharo-project] Log of the retrospective analysis from Pharo 2.0

by StÃ©phane Ducasse

Hello happy pharoers Since Pharo2.0 will be released pretty soon, we led a retrospective analysis to learn and improve our process. Here are the notes taken by clement from the meeting led by esteban with all the team here. Pharo 2.0 Retrospective meeting by Esteban Lorenzo The Good BugTracker as Backlog Sprint / mini - sprint / pair programming Locking changes before release Community getting involved Web doc jenkins : the monkey, zeroconf script Smalltalkhub The Bad Trello We need a place to backlog what to do. We should use the FogBugz bug tracker Long development cycle (1 year), Focus problem : most things works but are not finished We should have a 1 to 2 months cycle with a part where we introduce new things and a part where we only fix bugs. At the end of each cycle, Pharo should be stable. Each cycle should have a retrospective meeting. We should pair program every friday afternoons on Pharo improvements. New failing test in Jenkins, Red builds on jenkins stayed forever We need a clear separation between pharo and pharo contribution both on smalltalk hub and Jenkins to have a clean green front end to show to end users In case of a red build, we need a quick meeting to pick someone to fix it. We need to fix the red builds on the friday' mandatory mini sprint Integrator bottleneck More intelligent monkey better tools (spec tool idea from Esteban where you just click accept and the slce is integrated) New features accepted only with tests and comments Only slices accepted no more change sets Pointless discussions on the mailing list Documentation : class comments, ... do not integrate undocumented features add code critics features in the monkey change the template of the class comment The Ugly 2 weeks lost : broken image during ESUG 2 weeks lost : beginning of the year : no VM working, jenkins couldnât test things. -> we will staged development. Communication failed : team and community For new features, send more mails to the Pharo or RMOD mailing list and less to the RMOD mailing list or private mails between few people Infrastructure VM : stability Stability : 1 VM release per Pharo release. 1 official Vm which is not just some VM from a build. Stability : VM not release if an acceptance list does not work with the VM. The acceptance list is for now all the Pharo core, seaside and Moose

March 15, 2013

Re: [Pharo-project] https://pharo.fogbugz.com : can I have an account there?

by Tudor Girba

Can I get an account, too? Doru On Mar 15, 2013, at 5:31 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-03-15, at 17:25, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > >> Will the bugtracker be open one day? >> >> Can I have an account? > > you're in, request a new password when you connect and everything should work. > >> >> Esteban A. Maringolo >> >> >> 2013/3/8 phil(a)highoctane.be <phil(a)highoctane.be>: >>> 'k thx. >>> >>> I do use FBZ since quite a while (v3), so good :-) >>> >>> 2013/3/8 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >>>> For now we are just migrating, but soon the doors will be open : >>>> >>>> Steps needed before official announcement: >>>> - Migrate all issues ( we are currently at 7026 issues migrated) >>>> - Deploy the Penelope website (to register easily to the issue tracker and >>>> have a list of open issues) >>>> - Fix dependency between issues (blockedOn:) >>>> - Polish a bit statuses in fogbugz >>>> The plan is to announce it at the same time that the announcement of >>>> Pharo2.0 release :) >>>> >>>> Ben >>>> >>>> On Mar 8, 2013, at 11:13 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> >>>> patience, patience :D, we will announce that pretty soon. >>>> until then you can still report on the old issue tracker. >>>> >>>> On 2013-03-08, at 10:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>> >>>> How to do? >>>> >>>> Guess bug reporting occurs there now. >>>> >>>> Regards, >>>> Phil >>>> >>>> >>>> >>>> >>> >> > > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

March 15, 2013

Re: [Pharo-project] https://pharo.fogbugz.com : can I have an account there?

by Esteban Lorenzano

yes... we have some infrastructure problems, but it will be integrated and accounts auto-created :) On Mar 15, 2013, at 5:25 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > Will the bugtracker be open one day? > > Can I have an account? > > Thnx! > > Esteban A. Maringolo > > > 2013/3/8 phil(a)highoctane.be <phil(a)highoctane.be>: >> 'k thx. >> >> I do use FBZ since quite a while (v3), so good :-) >> >> 2013/3/8 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >>> For now we are just migrating, but soon the doors will be open :) >>> >>> Steps needed before official announcement: >>> - Migrate all issues ( we are currently at 7026 issues migrated) >>> - Deploy the Penelope website (to register easily to the issue tracker and >>> have a list of open issues) >>> - Fix dependency between issues (blockedOn:) >>> - Polish a bit statuses in fogbugz >>> The plan is to announce it at the same time that the announcement of >>> Pharo2.0 release :) >>> >>> Ben >>> >>> On Mar 8, 2013, at 11:13 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>> patience, patience :D, we will announce that pretty soon. >>> until then you can still report on the old issue tracker. >>> >>> On 2013-03-08, at 10:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>> >>> How to do? >>> >>> Guess bug reporting occurs there now. >>> >>> Regards, >>> Phil >>> >>> >>> >>> >> >

March 15, 2013