I agree to all you wrote. But the increased speed of releasing new
versions with unstable experimental features somehow contradicts the
otherwise mature development state. As a user of the JavaHL API we only
consider a feature as stable if it is reflected in all binding APIs, too.
--
Best
An interesting if slightly sad read. I want to add my support and praise
as a long-time user of Subversion.
I still come across many users out there. Subversion is thriving in one
particular business I work with. The youngsters have brought some Git in
with them but it seems to be led by
People wanting to donate a feature or fix a bug with Subversion are
increasingly going to be happy with a Docker-based quick start. Most
F/OSS teams want tests too, and y'all are very strict there in that
regard, and someone who can write tests for your test-base covering
code for your codebase is
On Wed, Jun 19, 2019 at 6:36 AM Julian Foad wrote:
> Some time within the past year I looked for the best available Docker
> deployment of Subversion and found this:
>
> https://github.com/elleFlorio/svn-docker
> "Lightweight Docker image to build a container running an SVN server"
>
> It might
Nathan Hartman wrote:
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.
[...]
Subversion 1.x is mature. Subversion 2.0 is now on the drawing board.
A very good point.
[...]
Prong 1:
Some time within the past year I looked for the best available Docker
deployment of Subversion and found this:
https://github.com/elleFlorio/svn-docker
"Lightweight Docker image to build a container running an SVN server"
It might be helpful as a starting point for creating a dev environment.
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 homebrew advice [...]
Paul Hammant wrote:
Michael Pilato wrote:
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.
Is there an opportunity here for someone to whip up a Dockerized
development
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
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
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.
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
Guten Tag Karl Fogel,
am Freitag, 14. Juni 2019 um 18:16 schrieben Sie:
> I just put out an informal Twitter poll to get a sense of how
> people are using Subversion these days:
> https://twitter.com/kfogel/status/1139559630059843586
> (Or at least, to get a sense of how Twitter users who
On Fri, Jun 14, 2019 at 10:35 AM Eric S. Raymond wrote:
> Julian Foad :
> > not dwell on our sadness and criticism of what went before; let us try to
> > keep this thread focused on positive solutions for what to do next.
>
It's all a matter of publicity.
Git gets all the publicity because
Julian Foad wrote:
>Ah, yes -- I didn't mean to discourage anyone from just describing a
>problem; that can then help others seek a solution. [...]
One thing I wonder is how widely Subversion is in non-published trees,
especially corporate trees.
For example, my company uses Subversion
Three PRs out on GitHub for Subversion spanning years -
https://github.com/apache/subversion/pulls
^ "join in" versus "don't join" in is communicated via team welcoming,
curating, and consuming of PRs in this age. Sure, Julian's shelve tech is
the starting point of a PR system for Subversion
Julian Foad :
> Anyone with constructive suggestions, please do share them. Please let us
> not dwell on our sadness and criticism of what went before; let us try to
> keep this thread focused on positive solutions for what to do next.
You guys know me. I'm a past contributor, occasional critic,
Mark Phippard wrote:
Making a suggestion here is tough. [...]
Ah, yes -- I didn't mean to discourage anyone from just describing a
problem; that can then help others seek a solution. Thanks for sharing
the problem of building downstream from the frequent releases.
- Julian
On Fri, Jun 14, 2019 at 9:26 AM Julian Foad wrote:
> The Subversion community has gradually become much less active. We have
> reached the point where we are struggling to even put out a release.
>
> Johan said I may quote his thoughts, so I will:
> > Indeed, I was just wondering about the same
The Subversion community has gradually become much less active. We have
reached the point where we are struggling to even put out a release.
Johan said I may quote his thoughts, so I will:
Indeed, I was just wondering about the same thing, before I read your
response, Julian. It's quite clear
21 matches
Mail list logo
