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 <woh...@apache.org> 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 > >> <https://github.com/apache/couchdb/issues/2167> *(Eric) **- PR > reviewed, > >> addressing comments* > >> - 1875 Update SpiderMonkey version > >> <https://github.com/apache/couchdb/issues/1875> *(Peng Hui)* *- PR > >> reviewed, addressing comments* > >> - 2171 Document new management subsystems (smoosh, ioq, ken) > >> <https://github.com/apache/couchdb/issues/2171>-ioq left. *(Adam) **- > ioq > >> only, doc ticket, not a blocker* > >> - 1524 Per-document access control #1524 > >> <https://github.com/apache/couchdb/issues/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 > >> <https://github.com/apache/couchdb/issues/2249> *(Adam) **- ETA Dec 6 > * > >> > >> *Backlog:* > >> *- *2191 Tighten up security model > >> <https://github.com/apache/couchdb/issues/2191> *- **(TBD)** change db > >> security to admin_only, small change* > >> - Release Notes > >> - Blog posts (see Jan's email) > >> > >> Thanks! > >> > >> Deni > > >
