A useful, well-documented process of a fellow Apache community ... a
process that has worked steadily and produced (your words) "outstanding
stability, backwards compat, and steadily add new features, big and small".
We're talking process, not the merits of software package that uses it (and
this
(as a completely external voice, user, packager, architect of systems big
and small) - would it not make sense to model the workflow of a project
that has a more positive feature _and_ stability profile?
With all due respect, Subversion is an old project, offering little new,
with a dwindling user
Great info! Thanks!
> On Apr 20, 2018, at 9:52 AM, Greg Stein wrote:
>
> Hi all,
>
> I've been kind of watching the thrashing around on several threads now about
> problems and fixes to how the HTTPD project manages its process around
> releases. I thought it might be a good idea to suggest a
Hi all,
I've been kind of watching the thrashing around on several threads now
about problems and fixes to how the HTTPD project manages its process
around releases. I thought it might be a good idea to suggest a
tried-and-true alternative defined by the Apache Subversion project, and
documented e
