Hi Joan, > On 7 Sep 2019, at 00:59, Joan Touzet <woh...@apache.org> wrote: > More accurately, the current plan is they won't be re-implemented for 4.0, > since the existing implementations won't work in 4.0 against FoundationDB.
About the discussions on dropping the functions that make design documents so useful to many of us: Thanks again for clarifying. This provides predictability for a group of users that might otherwise feel like a week minory. Together with Jan's LTS commitment in the August report below, this predictability is highly appreciated. > On 19 Aug 2019, at 11:51, Jan Lehnardt <j...@apache.org> wrote: > > 3.0 > will include the best version of the current, mostly Erlang-based project, > with many new features contributed by various project partners (but notably > IBM). This will be the LTS version for people who won’t be able to migrate to > the newer technology foundation. There are a number of technical limitations > that we are happy to adopt as a project going forward, but that might be deal- > breakers for some users. As such, we’ll serve those users best with an > excellent > edition of the original technology stack. LTS-timelines are TBD. > Johs PS > On 7 Sep 2019, at 00:59, Joan Touzet <woh...@apache.org> wrote: > We've already dropped the 'couchapp' term in the documentation, over a year > ago. There is a single reference to them in the docs that states these > functions should not be used for new designs: As for the discussion about CouchDB as a catch-all platform (node.js, haproxy, and nginx etc) – it is lost and buried. Thanks to @ermouth for narrowing down this to "prossesing endpoints" and "data pre/post prossessing", useful terms in redirecting the discussion towards the usefulness of design documents that sync can with the data.
