On Tue, Dec 20, 2016 at 1:49 AM, Nico Kadel-Garcia wrote:
> On Mon, Dec 19, 2016 at 6:10 PM, Matt Garman wrote:
>> Looking at the Subversion 1.7 release notes[2], and also my own
>> testing, it appears that what I could do to make this easy for
>> everyone is to upgrade al
We're looking at upgrading our systems from CentOS 6 to CentOS 7[1].
CentOS 6 provides subversion-1.6, and CentOS 7 provides
subversion-1.7. We have far too many machines and too much custom
development to upgrade all servers at once. So there will be a period
where the two OSes must co-exist. (
On Wed, Jun 1, 2016 at 10:58 AM, Pavel Lyalyakin
wrote:
> Hello Matt,
>
> Why do you use `rsync`?
>
> [1]: http://svnbook.red-bean.com/en/1.8/svn.ref.svnadmin.c.freeze.html
> [2]: http://svnbook.red-bean.com/en/1.8/svn.ref.svnadmin.c.hotcopy.html
I have no good reason! Backup scripts were setup
I think there's two questions here: (1) what are general good backup
practices, and (2) how to backup svn repos specifically.
"If we lose it, we're all out of work." Hopefully your boss
recognizes this and has budgeted appropriately. In my experience
there is no perfect backup; the best you can
Consider this scenario: our project has concurrent releases, R8 and
R9. These releases have been indicated in the repo by some means,
either a tag or a branch.
Now, we need to bugfix R8 only. Specifically, we want to do a release
R8.1 that does not include R9 features.
Through some means, e.g. m
