Ben
On Apr 5, 2013, at 8:29 AM, Igor Stasenko <siguc...@gmail.com> wrote: > On 4 April 2013 19:52, Camillo Bruni <camillobr...@gmail.com> wrote: >> >> On 2013-04-04, at 18:51, Igor Stasenko <siguc...@gmail.com> wrote: >> >>> On 4 April 2013 17:38, Camillo Bruni <camillobr...@gmail.com> wrote: >>>> >>>> On 2013-04-04, at 16:11, Igor Stasenko <siguc...@gmail.com> wrote: >>>> >>>>> On 4 April 2013 15:45, Esteban Lorenzano <esteba...@gmail.com> wrote: >>>>>> really? >>>>>> please, add an issue in the tracker and submit a slice, as everybody >>>>>> else. >>>>>> >>>>> calm down, we're just discussing here. >>>>> I provided code here intentionally for nay-sayers like you to try it >>>>> and to check if it not breaks >>>>> something else (your workflow). >>>> >>>> Igor, not Esteban's workflow.. OUR WORKFLOW! >>>> >>> >>> Sure sure. Now have you tried the code which i sent if it works/breaks for >>> you? >>> >>> Or i should spend like 10 minutes filing the issue before figuring >>> that it is unacceptable? >> >> What the fuck do you think the rest does? >> >>> https://pharo.fogbugz.com/default.asp?10228 >> >> |( well the issue is the main entry point. If the code does not work >> you will be notified VIA the issue => manageed entity >> >> However how you solve this issue right now is by some fuzzy undefined process >> nobody manages. If you think that this change is worth getting into pharo >> then >> you open an issue and attach the SLICE (no changeset, SLICES). >> >> Then the whole machinery starts, people (INCLUDING YOU) look at the issues. >> Issue get rejected, modified, adapted! >> >> What you show here is IGNORANCE on a higher level. >> YOU IGNORE A WHOLE DAMN DEVELOPMENT PROCESS PEOPLE USE EVERY DAY. >> And you put yourself into the brilliant exception position. >> > Not at all. > >> Believe me I am not the only one who is upset with that. (but usually the >> one who complains first). >> >> >> So why do I complain? >> >> - I know that you haven't filed a single issue on the new issue tracker >> - I know that you DO NOT like the new issue tracker >> - I know that you DO NOT like to use SLICES (even though everybody else does) >> >> and.. >> - I am pretty convinced that you will never file an issue on the new issue >> tracker >> > > Hmm.. I already did. Before you even wrote your outrageous post. > >> >> Why? I don't know, I really don't. I wish I could understand your point >> here, but I cannot. > > You did not replied to a most important question , which goes first: > does it works for you or not. > > Issue tracker (as its name states) helps with tracking the issue, but > it does not solves it. > > Putting things on issue tracker doesn't means that issue will be > solved. Because nothing forces you to look at issue, you can still > ignore it. That's exactly why here we have automated actions performed. (and on the other hand, nothing forces you to provide a fix, to code, to go outside of you bed …) > You can complain that it was not filed correctly, there's "field A is > empty", field B is wrong and all sorts of bureaucracy.. > > So, if there's no action (like trying the proposed solution) while > topic is hot on mailing list, > i am pretty sure that there will be no any action with that issue later. > The code will be just silently integrated, only to be found later that > change is inappropriate and breaks things here and there.. and then we > go over again, by opening one more issue, and spending our precious > time on following the process, instead of solving the real problems. And when we will try to tackle issues to fix, we will iterate over all mailing list thread to find them ? If discussion like this happened in the issue tracker - people not implied in Pharo bug fixing (aka people without an account on fogbugz) do not get massively spammed - when someone want to fix this, he/she will not have to try to remember what it's about, guess the discussion was in the mailing list, retrieve the thread, etc … If you think that your time is more precious that any one else's, then maybe you missed what a community is … People spent time setting up the issue tracker to make it fit into our usual workflow, writing documentation about how to report an issue, and it has been decided that it was the way we (the community) manage bugs. Managing them in a mailing list has already been tried, and was not successful. I hate to blame, but the way you are acting know is just saying "I will not try to fit into the community workflow, I will stick to mine, and people will have to adapt'. I am sorry, it doesn't work. Ben PS: I flag your issue resolved (since a fix has been proposed), as explained here[1], it's the first and last time. My time is not less precious than yours [1] https://pharo.fogbugz.com/default.asp?W46 > > -- > Best regards, > Igor Stasenko. >
