Yes I do something similar to ben. Stef
On Fri, Nov 24, 2017 at 4:43 AM, Ben Coman <[email protected]> wrote: > Every time I investigate an issue from the tracker, I start with a new fresh > image. > Often its useful to track down which build introduced a bug, so I need to > bisect the last 500 builds or so. > I select a build version from the "Template" side and create an image named > "CaseCCCCC-BBBBB" > where CCCCC is the issue number and BBBBB is the build number. > I'll quickly end up with a dozen images then delete all but the two either > side of where the bug was introduced, > to examine the differences between them, and develop a fix for the later > build, then testing that fix in the latest build. > > Also when someone announces a new library, I can quickly create a new image > "SomeProject-BBBBB" > which I can dip my toes into as I get time available. > > Nowadays the matching VM is automatically downloaded, which makes it easier > to keep up with the latest VM+Image. > > cheers -ben > > On 23 November 2017 at 19:56, Herby Vojčík <[email protected]> wrote: >> >> Stephane Ducasse wrote: >>> >>> Hi >>> >>> I love the PharoLauncher. >> >> >> Pardon my question, I have downloaded it and looked at it, but I don't get >> it. What does it do / what are the use cases (honest question)? >> >> Thanks, Herby >> >> >>> It helps me to manage my parallel development and projects. >>> >>> We should put a link on the Pharo web site because >>> >>> http://files.pharo.org/platform/launcher/ >>> >>> is arcane. >>> >>> Stef >>> >> >> >
