On 2013-02-05, at 13:59, Igor Stasenko <[email protected]> wrote: > On 5 February 2013 13:13, Camillo Bruni <[email protected]> wrote: >> >> Ask yourself: >> - why do we have tests? >> - why do multiple people work together? >> - why do we want publicly available artifacts? >> - why do we want these artifacts tested publicly? >> - why do we write configurations? >> - why do we try to following coding standards? >> - why do we program in Smalltalk? >> - why do we mostly write deterministic code? >> - why do we work on Pharo? >> - why do we build a jenkins infrastructure? >> - why do we write down documentation? >> >> >> After successfully answering these questions you will understand! > > Of course you right. But i am not arguing about that. Can't you understand?
so then I really don't see why you cannot use the jenkins job? > If you took initiative about something, don't expect that others will > work in same pace as you or > automatically/immediately pick up everything you did and integrate it > into their working cycle. > It takes time and effort (both mental and physical). exactly, that is one of the reason we have a build server. People can just come download and test an artifact. What do you think happened when stef tried to show athens in chile? > Ask yourself: > - who, except original author knows best how things work? most probably the original author, that's also usually the guy you ask if you do not understand something. > - when you create a new artefacts, like a bunch of bash scripts for > jenkins. Who, you think, should take responsibility about them by _default_? so you that means since Christophe did the first pass on all the scripts he owns the responsibility for all the jobs? I did simplify the process, I reduced the dependency on jenkins for most builds, I added command line configuration scripts for Pharo... Really, I even communicated all of that on multiple occasions: by mail, by presentation If they are not good let me know my goal is to improve the situation we have! > - when you reconfiguring stuff and doing it completely different than > it was done before, why you think that rest of the world should > immediately jump in and start using it? Have you really ever had a look at what I did? I doubt it? => I introduced the scripts, I described them, I documented them => if there are difficulties understanding them I will explain it, document it => if something is wrong or should be changed I am willing to change it > - and finally, when you creating/releasing new stuff every other > day.. how many people is capable of keeping clear track of what you > are doing over months (+ doing own tasks)? I did not work on that for 3 months, so it is rather old. Things keep changing maybe for the worse, yes. But so far I haven't had many complaints. And if you had a look at it you would maybe give me instructive comments? Right now it reads as a global disagreement :/ with which I can only disagree
