+1 to all the proposed cuts.
I’m keen to see couch_server.erl itself go, so its remaining uses need new
homes (couch_passwords an obvious choice for the hashing referred to, etc).
I’m inferring that neither purge and global_changes work on main anyway, but
they can still be called and will
The current versions of those apps rely on mem3, clustering, adding
nodes, etc and they will trail behind the 3.x versions since
developers wouldn't think to port those updates to main since they are
simply non-functional there. Most of those apps have to be re-written
from scratch and it would be
Generally +1 with one major reservation:
On 12/04/2021 12:25, Nick Vatamaniuc wrote:
> * Some applications we want to have in main, but the way they are
> implemented currently rely completely or mostly on 3.x code: purge
> logic, couch_peruser, global_changes, setup. I am thinking it may be
>
+1 for cleanup of the codebase
On 2021/04/12 16:25:42, Nick Vatamaniuc wrote:
> Hi all,
>
> Currently we have a bunch of 3.x applications in the main branch which
> are not functional. Some even start supervisors and expose HTTP
> endpoints, like _reshard (mem3). Initially the idea was to keep
Hello again,
It turns out that I didn't read the notice from Bintray carefully
enough. The notice says that today, and April 26th, the service will
experience a forced "brown out" to let users know the service is going
offline at the end of the month.
This means you won't be able to install our
Hi all,
Currently we have a bunch of 3.x applications in the main branch which
are not functional. Some even start supervisors and expose HTTP
endpoints, like _reshard (mem3). Initially the idea was to keep those
applications there to make it easy to merge fixes back and forth, but
I wonder if it
