RE: CouchDB 3.0 Update - Dec 3rd

[Peng Hui Jiang]

Glad to know that SpiderMonkey update is an interested topic. Currently,
this task is under
final review phase. I also tested and made it working for Windows platform.
Hopefully we can
move forward soon.

Cheers,
Peng Hui

Peng Hui Jiang
Cloudant Development and Operation, China Development Lab



From:   Arturo GARCIA-VARGAS 
To: dev@couchdb.apache.org
Date:   2019/12/08 04:04 AM
Subject:[EXTERNAL] Re: CouchDB 3.0 Update - Dec 3rd



I think _access should wait and give way for a feature freeze and
subsequent release.  The _access branch is a major feature, touches a
lot of the inner workings of CouchDB, and the branch might need some
broader review once rebased.  Also, extra time might be welcomed?

I am personally waiting for the SpiderMonkey update and
dreyfus-by-default to migrate my patches (woohoo!).

   Cheers and be merry,

   Arturo

On 05/12/2019 18:34, Denitsa Burroughs wrote:
> Hi all -
>
> Thanks all for your input so far. Anyone else care to share their
> preference on the release options for 3.0?
>
> a) release in December
> b) release in January
> c) code freeze (now) after the required content is merged and only allow
> bug fixes through January?
>
> Thanks!
>
> Deni
>
> On Wed, Dec 4, 2019 at 11:53 AM Robert Newson  wrote:
>
>> Hi,
>>
>> I’m fine with a release either side of Christmas but I agree with Joan’s
>> point.
>>
>> I suggest a compromise of a code freeze. Only fixes for 3.0 to be merged
>> until the new year then do the release dance.
>>
>>> On 4 Dec 2019, at 14:45, support-tiger  wrote:
>>>
>>> fyi: Every year Ruby releases a new major version on Christmas - has
>> become a tradition with the user base - so no need to worry about
holidays
>> but obviously must be ready to ship.
>>>
>>> Do not forget about PR - I have seen little on the web about the
>> upcoming major version release.  What are the major new features ?  (not
>> just a changelog).  How about a review from someone trying out the beta
or
>> RC.
>>>
>>> One more thing: node express crud example ?  (if you want to attract
>> users to a JSON database)
>>>
>>> And one more thing:  are Fedora, Debian, Ubuntu pkgs ready ?
>>>
>>>
>>>> On 12/4/19 6:43 AM, Denitsa Burroughs wrote:
>>>> Hi Joan,
>>>>
>>>> Point taken. Let's see what the rest of the PMC members thinks. Just
to
>> be
>>>> clear: I had spoken to Bob about helping with the release activities,
>> so I
>>>> wasn't expecting this to land on you. :)
>>>>
>>>> I think that the biggest challenge would be getting the release notes
>> and
>>>> documentation ready. I would appreciate some feedback on areas that
are
>>>> lacking (if any) so that I can track it. Happy to open a ticket where
we
>>>> could capture a list if that makes sense.
>>>>
>>>> Thanks,
>>>>
>>>> Deni
>>>>
>>>>> On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet  wrote:
>>>>>
>>>>> Deni,
>>>>>
>>>>> Is it wise to rush out a 3.0 release prior to the holidays? I don't
>>>>> think so. Practically speaking we have 2 weeks before people start
>>>>> disappearing (including me, I'm gone as of Dec 18) and I don't think
>>>>> we'll get either the critical mass for testing, nor the attention
from
>>>>> our release channels, if we rush to get it done before then.
>>>>>
>>>>> Consider this an informal desire to push off the RC/release process
>>>>> until January 2020. If the rest of the PMC want to push ahead
(knowing
>> I
>>>>> won't be here to help, and are ready to do it themselves), go for it.
>>>>>
>>>>> -Joan
>>>>>
>>>>>> On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:
>>>>>> 
>>>>>>> On 4. Dec 2019, at 05:32, Denitsa Burroughs <
>>>>> denitsa.burrou...@gmail.com> wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> We are really close to merging the last few open PRs for CouchDB
3.0.
>>>>> I'd
>>>>>>> like to propose that we aim to merge all remaining changes *by the
>> end
>>>>> of
>>>>>>> the week* (Dec 6th) and work on a first RC next week. Please let me
>>>>> know if
>>>>>>> you don't think you could meet that goal. Also, last call for any
>>>>>>> additional cha

Re: CouchDB 3.0 Update - Dec 3rd

[Arturo GARCIA-VARGAS]

I think _access should wait and give way for a feature freeze and 
subsequent release.  The _access branch is a major feature, touches a 
lot of the inner workings of CouchDB, and the branch might need some 
broader review once rebased.  Also, extra time might be welcomed?


I am personally waiting for the SpiderMonkey update and 
dreyfus-by-default to migrate my patches (woohoo!).


  Cheers and be merry,

  Arturo

On 05/12/2019 18:34, Denitsa Burroughs wrote:

Hi all -

Thanks all for your input so far. Anyone else care to share their
preference on the release options for 3.0?

a) release in December
b) release in January
c) code freeze (now) after the required content is merged and only allow
bug fixes through January?

Thanks!

Deni

On Wed, Dec 4, 2019 at 11:53 AM Robert Newson  wrote:


Hi,

I’m fine with a release either side of Christmas but I agree with Joan’s
point.

I suggest a compromise of a code freeze. Only fixes for 3.0 to be merged
until the new year then do the release dance.


On 4 Dec 2019, at 14:45, support-tiger  wrote:

fyi: Every year Ruby releases a new major version on Christmas - has

become a tradition with the user base - so no need to worry about holidays
but obviously must be ready to ship.


Do not forget about PR - I have seen little on the web about the

upcoming major version release.  What are the major new features ?  (not
just a changelog).  How about a review from someone trying out the beta or
RC.


One more thing: node express crud example ?  (if you want to attract

users to a JSON database)


And one more thing:  are Fedora, Debian, Ubuntu pkgs ready ?



On 12/4/19 6:43 AM, Denitsa Burroughs wrote:
Hi Joan,

Point taken. Let's see what the rest of the PMC members thinks. Just to

be

clear: I had spoken to Bob about helping with the release activities,

so I

wasn't expecting this to land on you. :)

I think that the biggest challenge would be getting the release notes

and

documentation ready. I would appreciate some feedback on areas that are
lacking (if any) so that I can track it. Happy to open a ticket where we
could capture a list if that makes sense.

Thanks,

Deni


On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet  wrote:

Deni,

Is it wise to rush out a 3.0 release prior to the holidays? I don't
think so. Practically speaking we have 2 weeks before people start
disappearing (including me, I'm gone as of Dec 18) and I don't think
we'll get either the critical mass for testing, nor the attention from
our release channels, if we rush to get it done before then.

Consider this an informal desire to push off the RC/release process
until January 2020. If the rest of the PMC want to push ahead (knowing

I

won't be here to help, and are ready to do it themselves), go for it.

-Joan


On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:


On 4. Dec 2019, at 05:32, Denitsa Burroughs <

denitsa.burrou...@gmail.com> wrote:

Hi all,

We are really close to merging the last few open PRs for CouchDB 3.0.

I'd

like to propose that we aim to merge all remaining changes *by the

end

of

the week* (Dec 6th) and work on a first RC next week. Please let me

know if

you don't think you could meet that goal. Also, last call for any
additional change requests!
Here's the current status:

*In progress:*
- 2167 Remove vestiges of view-based `_changes` feed
 *(Eric) **- PR

reviewed,

addressing comments*
- 1875 Update SpiderMonkey version
 *(Peng Hui)* *- PR
reviewed, addressing comments*
- 2171 Document new management subsystems (smoosh, ioq, ken)
-ioq left. *(Adam)

**-

ioq

only, doc ticket, not a blocker*
- 1524 Per-document access control  #1524
 *(Jan)* -
*Need an ETA*

Def not before Christmas, but as stated, happy to leave this for 3.1

or

later. EXCEPT for one patch to accept the _access member in docs.

Im travelling internationally until the end of *next* week, so I can't

promise that before Dec 13.

It is a relatively minor patch, though, so we might be okay with

sneaking it during the RC phase.

Best
Jan
—


- 2249 Cluster setup does not create IOQ stats database
  *(Adam) **- ETA

Dec 6

*

*Backlog:*
*- *2191 Tighten up security model
 *- **(TBD)** change

db

security to admin_only, small change*
- Release Notes
- Blog posts (see Jan's email)

Thanks!

Deni


--
Support Dept
Tiger Nassau, Inc.
www.tigernassau.com
406-624-9310

Re: CouchDB 3.0 Update - Dec 3rd

[Joan Touzet]

On 2019-12-05 14:09, Adam Kocoloski wrote:
> Here’s my view:
> 
> - A release should have convenience binaries available within days
> - We don’t need to have all the deep dive blog posts on the new capabilities 
> ready, but they should follow within weeks
> - I don’t think we need to insert code freeze delays more than the usual 
> window of testing for a release candidate
> 
> My understanding is that one of the benefits of the new Jenkins setup is the 
> ability to automate many steps of the binary package generation. I think we 
> can devote some time to getting that online while we chase down the last few 
> remaining tickets and see if we can lighten the load for binary package 
> generation. If we can get this done in December - great!

I am pessimistic we'll have things ready for binary releases, even
automated ones, before the 18th. 9 business days is probably not enough
time.

I am just trying to be realistic here. If we can, then sure, that'd be
"great". But let's not count on it.

Based on "A release should have convenience binaries available within
days" my vote is still for waiting until January to do the RC. We can
code freeze / branch 3.0.x except for fixes, documentation and release
notes anytime.

-Joan

Re: CouchDB 3.0 Update - Dec 3rd

[Adam Kocoloski]

Here’s my view:

- A release should have convenience binaries available within days
- We don’t need to have all the deep dive blog posts on the new capabilities 
ready, but they should follow within weeks
- I don’t think we need to insert code freeze delays more than the usual window 
of testing for a release candidate

My understanding is that one of the benefits of the new Jenkins setup is the 
ability to automate many steps of the binary package generation. I think we can 
devote some time to getting that online while we chase down the last few 
remaining tickets and see if we can lighten the load for binary package 
generation. If we can get this done in December - great!

Adam

> On Dec 5, 2019, at 1:34 PM, Denitsa Burroughs  
> wrote:
> 
> Hi all -
> 
> Thanks all for your input so far. Anyone else care to share their
> preference on the release options for 3.0?
> 
> a) release in December
> b) release in January
> c) code freeze (now) after the required content is merged and only allow
> bug fixes through January?
> 
> Thanks!
> 
> Deni
> 
> On Wed, Dec 4, 2019 at 11:53 AM Robert Newson  wrote:
> 
>> Hi,
>> 
>> I’m fine with a release either side of Christmas but I agree with Joan’s
>> point.
>> 
>> I suggest a compromise of a code freeze. Only fixes for 3.0 to be merged
>> until the new year then do the release dance.
>> 
>>> On 4 Dec 2019, at 14:45, support-tiger  wrote:
>>> 
>>> fyi: Every year Ruby releases a new major version on Christmas - has
>> become a tradition with the user base - so no need to worry about holidays
>> but obviously must be ready to ship.
>>> 
>>> Do not forget about PR - I have seen little on the web about the
>> upcoming major version release.  What are the major new features ?  (not
>> just a changelog).  How about a review from someone trying out the beta or
>> RC.
>>> 
>>> One more thing: node express crud example ?  (if you want to attract
>> users to a JSON database)
>>> 
>>> And one more thing:  are Fedora, Debian, Ubuntu pkgs ready ?
>>> 
>>> 
 On 12/4/19 6:43 AM, Denitsa Burroughs wrote:
 Hi Joan,
 
 Point taken. Let's see what the rest of the PMC members thinks. Just to
>> be
 clear: I had spoken to Bob about helping with the release activities,
>> so I
 wasn't expecting this to land on you. :)
 
 I think that the biggest challenge would be getting the release notes
>> and
 documentation ready. I would appreciate some feedback on areas that are
 lacking (if any) so that I can track it. Happy to open a ticket where we
 could capture a list if that makes sense.
 
 Thanks,
 
 Deni
 
> On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet  wrote:
> 
> Deni,
> 
> Is it wise to rush out a 3.0 release prior to the holidays? I don't
> think so. Practically speaking we have 2 weeks before people start
> disappearing (including me, I'm gone as of Dec 18) and I don't think
> we'll get either the critical mass for testing, nor the attention from
> our release channels, if we rush to get it done before then.
> 
> Consider this an informal desire to push off the RC/release process
> until January 2020. If the rest of the PMC want to push ahead (knowing
>> I
> won't be here to help, and are ready to do it themselves), go for it.
> 
> -Joan
> 
>> On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:
>> 
>>> On 4. Dec 2019, at 05:32, Denitsa Burroughs <
> denitsa.burrou...@gmail.com> wrote:
>>> Hi all,
>>> 
>>> We are really close to merging the last few open PRs for CouchDB 3.0.
> I'd
>>> like to propose that we aim to merge all remaining changes *by the
>> end
> of
>>> the week* (Dec 6th) and work on a first RC next week. Please let me
> know if
>>> you don't think you could meet that goal. Also, last call for any
>>> additional change requests!
>>> Here's the current status:
>>> 
>>> *In progress:*
>>> - 2167 Remove vestiges of view-based `_changes` feed
>>>  *(Eric) **- PR
> reviewed,
>>> addressing comments*
>>> - 1875 Update SpiderMonkey version
>>>  *(Peng Hui)* *- PR
>>> reviewed, addressing comments*
>>> - 2171 Document new management subsystems (smoosh, ioq, ken)
>>> -ioq left. *(Adam)
>> **-
> ioq
>>> only, doc ticket, not a blocker*
>>> - 1524 Per-document access control  #1524
>>>  *(Jan)* -
>>> *Need an ETA*
>> Def not before Christmas, but as stated, happy to leave this for 3.1
>> or
> later. EXCEPT for one patch to accept the _access member in docs.
>> Im travelling internationally until the end of *next* week, so I can't
> promise that before Dec 13.
>> It is a relatively minor patch, though, so we might be okay with
> 

Re: CouchDB 3.0 Update - Dec 3rd

[Denitsa Burroughs]

Hi all -

Thanks all for your input so far. Anyone else care to share their
preference on the release options for 3.0?

a) release in December
b) release in January
c) code freeze (now) after the required content is merged and only allow
bug fixes through January?

Thanks!

Deni

On Wed, Dec 4, 2019 at 11:53 AM Robert Newson  wrote:

> Hi,
>
> I’m fine with a release either side of Christmas but I agree with Joan’s
> point.
>
> I suggest a compromise of a code freeze. Only fixes for 3.0 to be merged
> until the new year then do the release dance.
>
> > On 4 Dec 2019, at 14:45, support-tiger  wrote:
> >
> > fyi: Every year Ruby releases a new major version on Christmas - has
> become a tradition with the user base - so no need to worry about holidays
> but obviously must be ready to ship.
> >
> > Do not forget about PR - I have seen little on the web about the
> upcoming major version release.  What are the major new features ?  (not
> just a changelog).  How about a review from someone trying out the beta or
> RC.
> >
> > One more thing: node express crud example ?  (if you want to attract
> users to a JSON database)
> >
> > And one more thing:  are Fedora, Debian, Ubuntu pkgs ready ?
> >
> >
> >> On 12/4/19 6:43 AM, Denitsa Burroughs wrote:
> >> Hi Joan,
> >>
> >> Point taken. Let's see what the rest of the PMC members thinks. Just to
> be
> >> clear: I had spoken to Bob about helping with the release activities,
> so I
> >> wasn't expecting this to land on you. :)
> >>
> >> I think that the biggest challenge would be getting the release notes
> and
> >> documentation ready. I would appreciate some feedback on areas that are
> >> lacking (if any) so that I can track it. Happy to open a ticket where we
> >> could capture a list if that makes sense.
> >>
> >> Thanks,
> >>
> >> Deni
> >>
> >>> On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet  wrote:
> >>>
> >>> Deni,
> >>>
> >>> Is it wise to rush out a 3.0 release prior to the holidays? I don't
> >>> think so. Practically speaking we have 2 weeks before people start
> >>> disappearing (including me, I'm gone as of Dec 18) and I don't think
> >>> we'll get either the critical mass for testing, nor the attention from
> >>> our release channels, if we rush to get it done before then.
> >>>
> >>> Consider this an informal desire to push off the RC/release process
> >>> until January 2020. If the rest of the PMC want to push ahead (knowing
> I
> >>> won't be here to help, and are ready to do it themselves), go for it.
> >>>
> >>> -Joan
> >>>
>  On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:
>  
> > On 4. Dec 2019, at 05:32, Denitsa Burroughs <
> >>> denitsa.burrou...@gmail.com> wrote:
> > Hi all,
> >
> > We are really close to merging the last few open PRs for CouchDB 3.0.
> >>> I'd
> > like to propose that we aim to merge all remaining changes *by the
> end
> >>> of
> > the week* (Dec 6th) and work on a first RC next week. Please let me
> >>> know if
> > you don't think you could meet that goal. Also, last call for any
> > additional change requests!
> > Here's the current status:
> >
> > *In progress:*
> > - 2167 Remove vestiges of view-based `_changes` feed
> >  *(Eric) **- PR
> >>> reviewed,
> > addressing comments*
> > - 1875 Update SpiderMonkey version
> >  *(Peng Hui)* *- PR
> > reviewed, addressing comments*
> > - 2171 Document new management subsystems (smoosh, ioq, ken)
> > -ioq left. *(Adam)
> **-
> >>> ioq
> > only, doc ticket, not a blocker*
> > - 1524 Per-document access control  #1524
> >  *(Jan)* -
> > *Need an ETA*
>  Def not before Christmas, but as stated, happy to leave this for 3.1
> or
> >>> later. EXCEPT for one patch to accept the _access member in docs.
>  Im travelling internationally until the end of *next* week, so I can't
> >>> promise that before Dec 13.
>  It is a relatively minor patch, though, so we might be okay with
> >>> sneaking it during the RC phase.
>  Best
>  Jan
>  —
> 
> > - 2249 Cluster setup does not create IOQ stats database
> >   *(Adam) **- ETA
> Dec 6
> >>> *
> > *Backlog:*
> > *- *2191 Tighten up security model
> >  *- **(TBD)** change
> db
> > security to admin_only, small change*
> > - Release Notes
> > - Blog posts (see Jan's email)
> >
> > Thanks!
> >
> > Deni
> >
> > --
> > Support Dept
> > Tiger Nassau, Inc.
> > www.tigernassau.com
> > 406-624-9310
> >
> >
> >
>
>

Re: CouchDB 3.0 Update - Dec 3rd

[Robert Newson]

Hi,

I’m fine with a release either side of Christmas but I agree with Joan’s point. 

I suggest a compromise of a code freeze. Only fixes for 3.0 to be merged until 
the new year then do the release dance. 

> On 4 Dec 2019, at 14:45, support-tiger  wrote:
> 
> fyi: Every year Ruby releases a new major version on Christmas - has become a 
> tradition with the user base - so no need to worry about holidays but 
> obviously must be ready to ship.
> 
> Do not forget about PR - I have seen little on the web about the upcoming 
> major version release.  What are the major new features ?  (not just a 
> changelog).  How about a review from someone trying out the beta or RC.
> 
> One more thing: node express crud example ?  (if you want to attract users to 
> a JSON database)
> 
> And one more thing:  are Fedora, Debian, Ubuntu pkgs ready ?
> 
> 
>> On 12/4/19 6:43 AM, Denitsa Burroughs wrote:
>> Hi Joan,
>> 
>> Point taken. Let's see what the rest of the PMC members thinks. Just to be
>> clear: I had spoken to Bob about helping with the release activities, so I
>> wasn't expecting this to land on you. :)
>> 
>> I think that the biggest challenge would be getting the release notes and
>> documentation ready. I would appreciate some feedback on areas that are
>> lacking (if any) so that I can track it. Happy to open a ticket where we
>> could capture a list if that makes sense.
>> 
>> Thanks,
>> 
>> Deni
>> 
>>> On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet  wrote:
>>> 
>>> Deni,
>>> 
>>> Is it wise to rush out a 3.0 release prior to the holidays? I don't
>>> think so. Practically speaking we have 2 weeks before people start
>>> disappearing (including me, I'm gone as of Dec 18) and I don't think
>>> we'll get either the critical mass for testing, nor the attention from
>>> our release channels, if we rush to get it done before then.
>>> 
>>> Consider this an informal desire to push off the RC/release process
>>> until January 2020. If the rest of the PMC want to push ahead (knowing I
>>> won't be here to help, and are ready to do it themselves), go for it.
>>> 
>>> -Joan
>>> 
 On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:
 
> On 4. Dec 2019, at 05:32, Denitsa Burroughs <
>>> denitsa.burrou...@gmail.com> wrote:
> Hi all,
> 
> We are really close to merging the last few open PRs for CouchDB 3.0.
>>> I'd
> like to propose that we aim to merge all remaining changes *by the end
>>> of
> the week* (Dec 6th) and work on a first RC next week. Please let me
>>> know if
> you don't think you could meet that goal. Also, last call for any
> additional change requests!
> Here's the current status:
> 
> *In progress:*
> - 2167 Remove vestiges of view-based `_changes` feed
>  *(Eric) **- PR
>>> reviewed,
> addressing comments*
> - 1875 Update SpiderMonkey version
>  *(Peng Hui)* *- PR
> reviewed, addressing comments*
> - 2171 Document new management subsystems (smoosh, ioq, ken)
> -ioq left. *(Adam) **-
>>> ioq
> only, doc ticket, not a blocker*
> - 1524 Per-document access control  #1524
>  *(Jan)* -
> *Need an ETA*
 Def not before Christmas, but as stated, happy to leave this for 3.1 or
>>> later. EXCEPT for one patch to accept the _access member in docs.
 Im travelling internationally until the end of *next* week, so I can't
>>> promise that before Dec 13.
 It is a relatively minor patch, though, so we might be okay with
>>> sneaking it during the RC phase.
 Best
 Jan
 —
 
> - 2249 Cluster setup does not create IOQ stats database
>   *(Adam) **- ETA Dec 6
>>> *
> *Backlog:*
> *- *2191 Tighten up security model
>  *- **(TBD)** change db
> security to admin_only, small change*
> - Release Notes
> - Blog posts (see Jan's email)
> 
> Thanks!
> 
> Deni
> 
> -- 
> Support Dept
> Tiger Nassau, Inc.
> www.tigernassau.com
> 406-624-9310
> 
> 
> 

Re: CouchDB 3.0 Update - Dec 3rd

[support-tiger]

fyi: Every year Ruby releases a new major version on Christmas - has 
become a tradition with the user base - so no need to worry about 
holidays but obviously must be ready to ship.


Do not forget about PR - I have seen little on the web about the 
upcoming major version release.  What are the major new features ?  (not 
just a changelog).  How about a review from someone trying out the beta 
or RC.


One more thing: node express crud example ?  (if you want to attract 
users to a JSON database)


And one more thing:  are Fedora, Debian, Ubuntu pkgs ready ?


On 12/4/19 6:43 AM, Denitsa Burroughs wrote:

Hi Joan,

Point taken. Let's see what the rest of the PMC members thinks. Just to be
clear: I had spoken to Bob about helping with the release activities, so I
wasn't expecting this to land on you. :)

I think that the biggest challenge would be getting the release notes and
documentation ready. I would appreciate some feedback on areas that are
lacking (if any) so that I can track it. Happy to open a ticket where we
could capture a list if that makes sense.

Thanks,

Deni

On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet  wrote:


Deni,

Is it wise to rush out a 3.0 release prior to the holidays? I don't
think so. Practically speaking we have 2 weeks before people start
disappearing (including me, I'm gone as of Dec 18) and I don't think
we'll get either the critical mass for testing, nor the attention from
our release channels, if we rush to get it done before then.

Consider this an informal desire to push off the RC/release process
until January 2020. If the rest of the PMC want to push ahead (knowing I
won't be here to help, and are ready to do it themselves), go for it.

-Joan

On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:



On 4. Dec 2019, at 05:32, Denitsa Burroughs <

denitsa.burrou...@gmail.com> wrote:

Hi all,

We are really close to merging the last few open PRs for CouchDB 3.0.

I'd

like to propose that we aim to merge all remaining changes *by the end

of

the week* (Dec 6th) and work on a first RC next week. Please let me

know if

you don't think you could meet that goal. Also, last call for any
additional change requests!
Here's the current status:

*In progress:*
- 2167 Remove vestiges of view-based `_changes` feed
 *(Eric) **- PR

reviewed,

addressing comments*
- 1875 Update SpiderMonkey version
 *(Peng Hui)* *- PR
reviewed, addressing comments*
- 2171 Document new management subsystems (smoosh, ioq, ken)
-ioq left. *(Adam) **-

ioq

only, doc ticket, not a blocker*
- 1524 Per-document access control  #1524
 *(Jan)* -
*Need an ETA*

Def not before Christmas, but as stated, happy to leave this for 3.1 or

later. EXCEPT for one patch to accept the _access member in docs.

Im travelling internationally until the end of *next* week, so I can't

promise that before Dec 13.

It is a relatively minor patch, though, so we might be okay with

sneaking it during the RC phase.

Best
Jan
—


- 2249 Cluster setup does not create IOQ stats database
  *(Adam) **- ETA Dec 6

*

*Backlog:*
*- *2191 Tighten up security model
 *- **(TBD)** change db
security to admin_only, small change*
- Release Notes
- Blog posts (see Jan's email)

Thanks!

Deni


--
Support Dept
Tiger Nassau, Inc.
www.tigernassau.com
406-624-9310

Re: CouchDB 3.0 Update - Dec 3rd

[Denitsa Burroughs]

Hi Joan,

Point taken. Let's see what the rest of the PMC members thinks. Just to be
clear: I had spoken to Bob about helping with the release activities, so I
wasn't expecting this to land on you. :)

I think that the biggest challenge would be getting the release notes and
documentation ready. I would appreciate some feedback on areas that are
lacking (if any) so that I can track it. Happy to open a ticket where we
could capture a list if that makes sense.

Thanks,

Deni

On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet  wrote:

> Deni,
>
> Is it wise to rush out a 3.0 release prior to the holidays? I don't
> think so. Practically speaking we have 2 weeks before people start
> disappearing (including me, I'm gone as of Dec 18) and I don't think
> we'll get either the critical mass for testing, nor the attention from
> our release channels, if we rush to get it done before then.
>
> Consider this an informal desire to push off the RC/release process
> until January 2020. If the rest of the PMC want to push ahead (knowing I
> won't be here to help, and are ready to do it themselves), go for it.
>
> -Joan
>
> On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:
> > 
> >> On 4. Dec 2019, at 05:32, Denitsa Burroughs <
> denitsa.burrou...@gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> We are really close to merging the last few open PRs for CouchDB 3.0.
> I'd
> >> like to propose that we aim to merge all remaining changes *by the end
> of
> >> the week* (Dec 6th) and work on a first RC next week. Please let me
> know if
> >> you don't think you could meet that goal. Also, last call for any
> >> additional change requests!
> >> Here's the current status:
> >>
> >> *In progress:*
> >> - 2167 Remove vestiges of view-based `_changes` feed
> >>  *(Eric) **- PR
> reviewed,
> >> addressing comments*
> >> - 1875 Update SpiderMonkey version
> >>  *(Peng Hui)* *- PR
> >> reviewed, addressing comments*
> >> - 2171 Document new management subsystems (smoosh, ioq, ken)
> >> -ioq left. *(Adam) **-
> ioq
> >> only, doc ticket, not a blocker*
> >> - 1524 Per-document access control  #1524
> >>  *(Jan)* -
> >> *Need an ETA*
> >
> > Def not before Christmas, but as stated, happy to leave this for 3.1 or
> later. EXCEPT for one patch to accept the _access member in docs.
> >
> > Im travelling internationally until the end of *next* week, so I can't
> promise that before Dec 13.
> >
> > It is a relatively minor patch, though, so we might be okay with
> sneaking it during the RC phase.
> >
> > Best
> > Jan
> > —
> >
> >> - 2249 Cluster setup does not create IOQ stats database
> >>   *(Adam) **- ETA Dec 6
> *
> >>
> >> *Backlog:*
> >> *- *2191 Tighten up security model
> >>  *- **(TBD)** change db
> >> security to admin_only, small change*
> >> - Release Notes
> >> - Blog posts (see Jan's email)
> >>
> >> Thanks!
> >>
> >> Deni
> >
>

Re: CouchDB 3.0 Update - Dec 3rd

[Joan Touzet]

Deni,

Is it wise to rush out a 3.0 release prior to the holidays? I don't 
think so. Practically speaking we have 2 weeks before people start 
disappearing (including me, I'm gone as of Dec 18) and I don't think 
we'll get either the critical mass for testing, nor the attention from 
our release channels, if we rush to get it done before then.


Consider this an informal desire to push off the RC/release process 
until January 2020. If the rest of the PMC want to push ahead (knowing I 
won't be here to help, and are ready to do it themselves), go for it.


-Joan

On 2019-12-04 12:47 a.m., Jan Lehnardt wrote:



On 4. Dec 2019, at 05:32, Denitsa Burroughs  wrote:

Hi all,

We are really close to merging the last few open PRs for CouchDB 3.0. I'd
like to propose that we aim to merge all remaining changes *by the end of
the week* (Dec 6th) and work on a first RC next week. Please let me know if
you don't think you could meet that goal. Also, last call for any
additional change requests!
Here's the current status:

*In progress:*
- 2167 Remove vestiges of view-based `_changes` feed
 *(Eric) **- PR reviewed,
addressing comments*
- 1875 Update SpiderMonkey version
 *(Peng Hui)* *- PR
reviewed, addressing comments*
- 2171 Document new management subsystems (smoosh, ioq, ken)
-ioq left. *(Adam) **- ioq
only, doc ticket, not a blocker*
- 1524 Per-document access control  #1524
 *(Jan)* -
*Need an ETA*


Def not before Christmas, but as stated, happy to leave this for 3.1 or later. 
EXCEPT for one patch to accept the _access member in docs.

Im travelling internationally until the end of *next* week, so I can't promise 
that before Dec 13.

It is a relatively minor patch, though, so we might be okay with sneaking it 
during the RC phase.

Best
Jan
—


- 2249 Cluster setup does not create IOQ stats database
  *(Adam) **- ETA Dec 6 *

*Backlog:*
*- *2191 Tighten up security model
 *- **(TBD)** change db
security to admin_only, small change*
- Release Notes
- Blog posts (see Jan's email)

Thanks!

Deni

Re: CouchDB 3.0 Update - Dec 3rd

[Jan Lehnardt]


> On 4. Dec 2019, at 05:32, Denitsa Burroughs  
> wrote:
> 
> Hi all,
> 
> We are really close to merging the last few open PRs for CouchDB 3.0. I'd
> like to propose that we aim to merge all remaining changes *by the end of
> the week* (Dec 6th) and work on a first RC next week. Please let me know if
> you don't think you could meet that goal. Also, last call for any
> additional change requests!
> Here's the current status:
> 
> *In progress:*
> - 2167 Remove vestiges of view-based `_changes` feed
>  *(Eric) **- PR reviewed,
> addressing comments*
> - 1875 Update SpiderMonkey version
>  *(Peng Hui)* *- PR
> reviewed, addressing comments*
> - 2171 Document new management subsystems (smoosh, ioq, ken)
> -ioq left. *(Adam) **- ioq
> only, doc ticket, not a blocker*
> - 1524 Per-document access control  #1524
>  *(Jan)* -
> *Need an ETA*

Def not before Christmas, but as stated, happy to leave this for 3.1 or later. 
EXCEPT for one patch to accept the _access member in docs.

Im travelling internationally until the end of *next* week, so I can't promise 
that before Dec 13.

It is a relatively minor patch, though, so we might be okay with sneaking it 
during the RC phase.

Best
Jan
—

> - 2249 Cluster setup does not create IOQ stats database
>   *(Adam) **- ETA Dec 6 *
> 
> *Backlog:*
> *- *2191 Tighten up security model
>  *- **(TBD)** change db
> security to admin_only, small change*
> - Release Notes
> - Blog posts (see Jan's email)
> 
> Thanks!
> 
> Deni

CouchDB 3.0 Update - Dec 3rd

[Denitsa Burroughs]

Hi all,

We are really close to merging the last few open PRs for CouchDB 3.0. I'd
like to propose that we aim to merge all remaining changes *by the end of
the week* (Dec 6th) and work on a first RC next week. Please let me know if
you don't think you could meet that goal. Also, last call for any
additional change requests!
Here's the current status:

*In progress:*
- 2167 Remove vestiges of view-based `_changes` feed
 *(Eric) **- PR reviewed,
addressing comments*
- 1875 Update SpiderMonkey version
 *(Peng Hui)* *- PR
reviewed, addressing comments*
- 2171 Document new management subsystems (smoosh, ioq, ken)
-ioq left. *(Adam) **- ioq
only, doc ticket, not a blocker*
- 1524 Per-document access control  #1524
 *(Jan)* -
*Need an ETA*
- 2249 Cluster setup does not create IOQ stats database
  *(Adam) **- ETA Dec 6 *

*Backlog:*
*- *2191 Tighten up security model
 *- **(TBD)** change db
security to admin_only, small change*
- Release Notes
- Blog posts (see Jan's email)

Thanks!

Deni