SLA

Daniel,

Beside working with OpenERP I am in charge of one of the largest implementation of MS CRM in region.
It is near EOL now :( ,soon more time for OE :).

Take a quick look at this:
http://blogs.msdn.com/b/emeadcrmsupport/archive/2010/04/13/microsoft-crm-4-0-update-rollup-overview.aspx
If you think OpenERP bugs are scary you can read details. 

Process goes like this:
1. Inform a client about availability of a update, possible problems and benefits,
2. If client approves we are testing upgrade procedure on fresh backup database simulating processes 
3. If all goes well we are upgrading customer test environment
4. Only after customer tests and approval, (and a notice about possible unavailability of service to all users) we are updating production servers and database (usually saturday night) testing that most critical business functions are ok,
and in case of interface change ...

I am not providing that service level for OpenERP(yet), but if we are to rely on some community project for production systems of our clients then ideally once a week (or ~, month) we would review source code changes, fight with community if necessary, temporarily fork if in panic, proposing changes until it is acceptable for production.
Definitely having private fork synchronized with main.

So this must be fast and simple and in one repository (server, web, addons, community...) so that impact on production system can be estimated quickly, easy to fork and merge back.

In our country not even SAP is able to cope with constant law changes - sometimes AFTER law is valid they are changing rules, so we are out of community for a month to sort out crisis. 
When we are back I want to do single git pull and get myself informed of what is going on.
Then I may be interested in WIP of Slovenian/Romanian devs (EU, ex socialist country with storno accounting) maybe we can
convince community to split some method so we don't have to override something like tax.calculate() for example,
and try to make localizations compatible.
All this is happening on LP, but I share Raphael that git has potential to increase participation.

Personally I don't have a use-case for package mgmt system and dayly updates.
But I must say that Tryton packaging is making me believe that they have far more mature ecosystem 
(small but knowledgeable). If I remember correctly every 6 months + critical patches - that makes sense.
Let's say OE community release with 4. number increase every 3-4 months reasonably tested by community,
3. number increase every 6-8 months "approved", or whatever model community is capable of.

I will definitely try your pipo, it looks like great tool for newcomers to easily install and test new versions,
but in real life i need banking addons from 6 month agg + latest currency_update + heavily patched payment module +
to be compatible with localization that i haven't find a time to propose to OCA, so is on temp fork I will sync later.

Best regards
Goran Kliska
PS I have highest regards for your OE community work - love mgmt modules.