Re: Running SVN 1.9.x on ASF servers?
From: Tony Stevenson <pctony_at_apache.org>
Date: Sat, 10 Oct 2015 09:14:17 +0100
For quite some time (well over 18 months now) the Infrastructure team has a policy that we will only deploy products, from packages stored in an accessible repo.
By default this only includes upstream suppliers from the OS. The OS is currently Ubuntu 14.04 - so by default we will only ship the latest version available in the repo.
However that said we are allowed to build our own packages and deploy those from an apt repo that we manage too.
If we do this, of course the package needs to be 100% safe to roll forwards and backwards. So full dependency management, clean install and removal. Etc etc.
To be clear. We will not just deploy some code anymore. This is because the work has to be completely idempotent and totally reproducible each and every time.
The httpd project were also affected by this - as we used to run trunk there. The team has moved on from this, as while it was nice to let folks do this, it added a non-insignificant burden on the Infra team to support it. Plus we have also be tasked with improving the infrastructure, making it more stable, more resilient, and less blocked on individuals. It also needs to fit in with our policy of using puppet to manage production services.
Given our recent (relatively) pain points with our subversion hosts (not the code) we'd be less likely today to just push out a 1.9.x beta release into production.
Please also remember that between the svn service and the mail service we have our by far two biggest services historically. This adds (rightly or wrongly) a higher barrier to entry as we are more sensitive about screwing them up.
What I will say is that:
- if you guys produced a .deb package that did all the things above
If you can do this. You may well find us saying yes that much more easily.
Please also remember that we have SLAs we have to work towards - so upgrades need be announced a minimum of 72hours prior, but the more the better.
I am happy to continue this thread if you want to ask more questions. But the 'it must be a package' - 'from a repo we trust' - 'all changes managed by puppet' are firm policies that we will not shift from.
So if you can work within those constraints we might be able to do something.
On behalf of the Apache Infrastructure Team
Sent from my iPhone
> On 10 Oct 2015, at 08:17, Branko Čibej <brane_at_apache.org> wrote:
This is an archived mail posted to the Subversion Dev mailing list.