On Sat, 2008-10-04 at 23:29 +0200, Marcus Denker wrote:
> Hi,
> 
> Maybe I need to make some thing clear
> 
> 1) There will be mistakes.
> 
Yep, change includes mistake!

> When integrating bugfixes and enhancements, it is impossible to not  
> make mistakes.
> The problem is that one can not check every single fix, this is just  
> not possible. And even
> if it would be checked line-by-line and very closely, there would be  
> new bugs. It is just impossible
> that this does not happen.
> 
> The problem is of course that the people doing the integration  
> everytime a bug is introduced look
> (and feel) like idiots.
> It would help if people would not strengthen this feeling... if I do  
> something where I feel like an
> idiot most of the time, at some point I will stop.
> 
Uhhh, is it that? I didn't read that much complaints on the list. 
Marcus, you are doing an incredible job!! And my feeling is that 
you are _really_ fast integrating stuff.  Seeing that it is 
embarrassing for me as I don't find any time to do something for 
pharo at the moment.

> 2) There is only limited time.
> 
> We can not look at every submission directly, we can not fix every bug  
> (even those introduced recently)
> very fast. This does not mean that we don't like the person who  
> submited something (or that this person
> did something wrong). It *especially* does not mean to discriminate  
> againt projects. e.g. if Seaside can't
> be loaded because of somet stupid bug, this does not mean that seaside  
> is not wanted or something like that.
> 
> 3) There is a lot of stuff that should be done
> ... and the only reason it is not done is lack of time. It's not  
> because we are idiots.
> 
I think we should build this community on trust. Trusting submissions
of community members is not something bad in my opinion. It's not your
job to check everything very deeply. It is the job of everyone to 
review updates/changes and to test them.

Taking all together I think we need to split upstream. As long as there
is only one upstream you can't check that _before_ it gets published.
And people see a version in the upstream as the next stable thing. So
we need a side channel for integration and testing. 

Norbert




_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to