Please keep your cool new stuff for Pharo 4
So⦠instead following my advice, you people continue submitting and asking for integration things that are API changes. As a result, instead gaining stability we are loosing it⦠can you guys please be so kind and stop doing what you shouldnât? I will ask it again: *now* we need to bugfix the upcoming release. Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min). I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version. Thanks, Esteban
Thanks Gemini Criquet :) You are right On 30 Jan 2014, at 17:11, Esteban Lorenzano <estebanlm@gmail.com> wrote:
So⦠instead following my advice, you people continue submitting and asking for integration things that are API changes. As a result, instead gaining stability we are loosing itâ¦
can you guys please be so kind and stop doing what you shouldnât?
I will ask it again: *now* we need to bugfix the upcoming release. Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min).
I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version.
Thanks, Esteban
Esteban Lorenzano wrote:
So⦠instead following my advice, you people continue submitting and asking for integration things that are API changes. As a result, instead gaining stability we are loosing itâ¦
can you guys please be so kind and stop doing what you shouldnât?
I will ask it again: *now* we need to bugfix the upcoming release. Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min).
I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version.
Thanks, Esteban
Also time is consumed developing, reviewing and integrating non-bug-cases, which could be tackling bugs. Can a "Pharo4.0" milestone be added to Fogbugz? Setting something to "Later" feels like it might get lost in the woods of old tickets imported from the old tracker. For instance, I've recently submitted a slice for [1] that adds two new methods and a trivial refactoring of one other to Spec's ComposableModel (so I can't imagine it would break anything), but in support of discipline on the feature freeze, I could get by with making these PharoLauncher extensions for now and hold them over to Pharo4.0. [1] https://pharo.fogbugz.com/f/cases/12677/subscribe-to-window-closed-event-out... Indeed, it might even be worthwhile to be more heavy handed and for New Cases replace 'Pharo3.0' with 'Pharo3.0-bugfix-only' - or maybe there is some way to splash some heading text at the top of each page using BugMonkey. cheers -ben
On 31 Jan 2014, at 17:31, btc@openinworld.com wrote:
Esteban Lorenzano wrote:
So⦠instead following my advice, you people continue submitting and asking for integration things that are API changes. As a result, instead gaining stability we are loosing it⦠can you guys please be so kind and stop doing what you shouldnât?
I will ask it again: *now* we need to bugfix the upcoming release. Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min). I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version. Thanks, Esteban
Also time is consumed developing, reviewing and integrating non-bug-cases, which could be tackling bugs.
Can a "Pharo4.0" milestone be added to Fogbugz?
Yes, we should⦠Marcus
On 31 janv. 2014, at 17:40, Marcus Denker <marcus.denker@inria.fr> wrote:
On 31 Jan 2014, at 17:31, btc@openinworld.com wrote:
Esteban Lorenzano wrote:
So⦠instead following my advice, you people continue submitting and asking for integration things that are API changes. As a result, instead gaining stability we are loosing it⦠can you guys please be so kind and stop doing what you shouldnât?
I will ask it again: *now* we need to bugfix the upcoming release. Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min). I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version. Thanks, Esteban
Also time is consumed developing, reviewing and integrating non-bug-cases, which could be tackling bugs.
Can a "Pharo4.0" milestone be added to Fogbugz?
Done
Yes, we shouldâ¦
Marcus
On 31 Jan 2014, at 13:29, btc@openinworld.com wrote:
For instance, I've recently submitted a slice for [1] that adds two new methods and a trivial refactoring of one other to Spec's ComposableModel (so I can't imagine it would break anything), but in support of discipline on the feature freeze, I could get by with making these PharoLauncher extensions for now and hold them over to Pharo4.0. [1] https://pharo.fogbugz.com/f/cases/12677/subscribe-to-window-closed-event-out...
Spec is actually hold beside Pharo3 now for this exact reason :) So things can continue to be integrated into Spec but not Pharo. And Spec bugfix for Pharo can then also be pushed into Spec. Ben PS: I will review your code within the week end, I am now at the Santiago airport waiting for a 14h long flight :)
participants (6)
-
Benjamin -
btc＠openinworld.com -
Camille Teruel -
Esteban Lorenzano -
Marcus Denker -
Pharo4Stef