[Release] Philosophical Discussion - The updates button is useless - discuss

[Andreas Raab]

Igor Stasenko wrote:
> 2009/7/8 Andreas Raab <andreas.raab at gmx.de>:
>> I think that the closest we can come in practice to such behavior is
>> merging. Since the MCM updates are merges, you get that precise behavior
>> when using multiple repositories. In other words, if there were a conflict
>> in the updates to 3.11 and Seaside 2.9 the update process would open a merge
>> browser and leave it to you to decide what exactly you want to do with it.
> 
> Yes, but at this point you are already failed. Because you turned
> something as simple as clicking an 'update' button
> into an engineering task for end user.

Hardly. You have been driving the discussion into ever more obscure 
situations without offering any answer whatsoever yourself. Up until the 
point where you were asking about conflicting updates from different 
sources, there was no need for any user interaction. If you are claiming 
that you have some "clever tool" that can automagically merge 
conflicting code, then please put up or shut up. Because this discussion 
is really getting silly and I'm running out of patience quickly.

As soon as you realize that you can't automagically merge conflicting 
updates, having the merge tool is the answer: Allow someone to provide a 
merged set of updates and (instead of subscribing to each stream 
individually) subscribe to the merged stream. Problem solved.

Cheers,
   - Andreas