Dockerized build templates would be great for a quickstart. I might have
one or two for Svn and if I de-hack them might be shareable. They'd be
biased towards Linux for build/test/standup of course, but would be better
than nothing.
On 6/18/19 9:50 AM, Paul Hammant wrote:
> Nobody is going to roll up to contribute to 1.x or 2.x Subversion if
> there is no copy-pasteable instructions for building on Mac, Win and
> Linux. And there's not -
> https://svn.apache.org/repos/asf/subversion/trunk/INSTALL - has no
> apt, nuget or h
Nobody is going to roll up to contribute to 1.x or 2.x Subversion if there
is no copy-pasteable instructions for building on Mac, Win and Linux. And
there's not - https://svn.apache.org/repos/asf/subversion/trunk/INSTALL -
has no apt, nuget or homebrew advice for people wanting to get into
developm
On Tue, Jun 18, 2019 at 7:00 AM Julian Foad wrote:
> Here is my suggestion.
>
>
> Primary goals:
>
> * Stability
>
> * Availability
All of the above -- being mature, reaching the stability phase, etc --
is true of Subversion 1.x. It is _not_ true of "Subversion" without a
1.x after it.
Sub
Here is my suggestion.
Primary goals:
* Stability
- because that's the stage in the project's life cycle
- if anyone wants to invest in development, that's fine too, but is
not what the current stewards of the project should be concentrating on
* Availability
- because stability for us
Hi all,
I'm hosting SVN-repos using svnserve and by providing the argument
"--root" with the parent dir of all my repos. In the past, all repos
have been placed as a direct child of the given path, but recently I
refactored that to manage repos by customers, topics and stuff. This
works pretty eas
6 matches
Mail list logo
