When Tony's PR to 3.x is working, we'll merge it. Should be in time.
https://github.com/apache/couchdb/pull/3506
On 17/04/2021 16:42, yhilem wrote:
> Hi,
>
> If possible add Prometheus (https://github.com/apache/couchdb/pull/3416).
>
> Thanks
> Youcef HILEM
>
>
>
> --
> Sent from:
Hi,
If possible add Prometheus (https://github.com/apache/couchdb/pull/3416).
Thanks
Youcef HILEM
--
Sent from: http://couchdb-development.1959287.n2.nabble.com/
I just completed an open PR sweep on -docs, everything has an open PR in
need of +1s (thanks Nick, there's more waiting!) or needs some
additional help from the community.
I've also created a 3.2.0 milestone in the main repo:
https://github.com/apache/couchdb/milestone/8
Feel free to add
Following up on my open PR sweep:
@Joan: I see that you've asked on a couple of PRs back in Oct 2020 if
they are to be merged and some of them were left open.
Is there any objection to closing them all? Or let's ignore them for now?
Donat
On Mon, Mar 29, 2021 at 11:06 AM Bessenyei Balázs Donát
I think I have read access to the COUCHDB namespace in Confluence, but not edit.
I'll skim through `main` to see if we need to / want to backport
things from there.
I can also bump every PR targeted for 3.x to see if people want to get
that content in there.
Release notes: I'm really _not_ good
Great! Excited to get help.
Here's the release procedure:
https://cwiki.apache.org/confluence/display/COUCHDB/Release+Procedure
Make sure you have wiki access, your Apache creds should get you in.
The most valuable thing you can do is make sure all of the PRs that we
want to land, have
Let’s do it :)
Best
Jan
—
> On 28. Mar 2021, at 19:03, Joan Touzet wrote:
>
> Hi everyone,
>
> We have a number of high profile improvements to 3.x since 3.1.1 came
> out. I think it's about time for 3.2. Does everyone agree?
>
> If so, we should start a clock for ~2 weeks to finish closing
+1
Let me know how I can help.
Donat
On Sun, Mar 28, 2021 at 7:03 PM Joan Touzet wrote:
>
> Hi everyone,
>
> We have a number of high profile improvements to 3.x since 3.1.1 came
> out. I think it's about time for 3.2. Does everyone agree?
>
> If so, we should start a clock for ~2 weeks to
Hi everyone,
We have a number of high profile improvements to 3.x since 3.1.1 came
out. I think it's about time for 3.2. Does everyone agree?
If so, we should start a clock for ~2 weeks to finish closing out any
last minute improvements, fixes, tweaks, etc. anyone wants to get in.
-Joan "we did
