On Fri, Mar 28, 2014 at 8:17 PM, Ben Coman <b...@openinworld.com> wrote:
> p...@highoctane.be wrote: > > Looks like a lot of people are going to be running patched versions if the > release goes without some enhancements. > > What about a > ConfigurationOfPharo30EnhancementsPackThatWereNotIntegratedForSomeSurelyVeryValidReason > ? > > (Let's make the name shorter but you get the idea). > > Phil > > > I wonder if it would be more or less effort to operate a "hot fix" > facility between releases. By this I mean, after Pharo 3 release all slices > fixing Pharo 3 bugs are based off the static release. This might have the > advantages that: > * Users get to select the bug fixes important to them > * Ergo, users can can avoid bug fixes not relevant to them that might have > unintended consequences in production. > * Bug fixes don't go stale when fixed in the released Pharo 3 but the > Pharo 3 builds have progressed a lot. > * Users don't have to decide between waiting for a the next Pharo 3 > minor-release, or tracking a moving target with continued evolution of > "latest" Pharo 3 after release. > * The part of the community that wants longer term support for systems in > production could take a greater role in maintaining Pharo 3, while the core > focus moves on to Pharo 4. > > A simple process might be tagging such resolved issues in Fogbugz as as > 3.0-hotfix. Alternatively a tool like the Configuration Browser might list > them in image. That tool could be installed from the Configuration Browser > as ConfigurationOfHotfix. > > The downside would be more difficulty in packaging hotfixes together for a > minor-release. However over time hotfixes might be consolidated into other > hotfixes, and the greatest of these becomes the basis for the minor-release. > > Just a passing thought. > cheers, Ben > > > A hotfix tool would be the other side of the Kommiter coin. So, Hotfixer? With a UI showing slices for which the status in FogBugz would be "hotfix30" Or a list of HOTFIX- in Pharo/Pharo30Hotfix/ in Smalltalkhub. Ah, let's make something for getting the ball rolling: http://www.smalltalkhub.com/#!/~Pharo/Pharo3Hotfix So,a HOTFIX shall possibly combine SLICEs or packages in a proper loading order and postscripts (like the one of Ben). I am currently writing some package loading code for my own use, this would be a nice opportunity for me to do a Spec based tool. Wanna join forces, people? Phil > > > > > > On Fri, Mar 28, 2014 at 4:02 PM, Johan Brichau <jo...@inceptive.be> wrote: > >> Hi all, >> >> With Sven's fixes loaded, our model unit tests are all running fine. The >> benchmarks indicate the same speed as in 1.4. This is really great! >> I'm still running the entire suite of tests but that will take a while to >> complete. But essential datetime bugs should have been spotted already. >> >> Great work Sven! >> I think it's worth integrating. If not, we will definitely work with this >> patched version. >> >> Johan >> >> On 28 Mar 2014, at 13:36, Pharo4Stef <pharo4s...@free.fr> wrote: >> >> > Hi johan >> > >> > Please let us know because I would be in favor of integrating such >> speed up if your system fully work. >> > >> > stef >> > >> > >> > On 28 Mar 2014, at 09:17, Johan Brichau <jo...@inceptive.be> wrote: >> > >> >> >> >> On 28 Mar 2014, at 06:24, Esteban Lorenzano <esteba...@gmail.com> >> wrote: >> >> >> >>> Bugs are errors that prevents the system to run. >> >> >> >> <nagging> >> >> Some performance problems make the system impossible to work with >> >> </nagging> >> >> >> >> Anyway, going to check in Sven's changes today. >> >> >> >> cheers >> >> Johan >> >> >> > >> > >> >> >> > >
