Re: [DISCUSS] improving visibility for CouchDB-maintained independent Erlang apps

2021-10-29 Thread Joan Touzet
On 29/10/2021 09:52, Adam Kocoloski wrote: Ah! That .asf.yaml configuration is neat, thanks for pointing it out. Good point on the source releases — do you have anything in particular in mind when you talk about making it simpler for the community at large? Sorry, that . should be a , :

[DISCUSS] Handle libicu upgrades better

2021-10-29 Thread Nick Vatamaniuc
Hello everyone, CouchDB by default uses the libicu library to sort its view rows. When views are built, we do not record or track the version of the collation algorithm. The issue is that the ICU library may modify the collation order between major libicu versions, and when that happens, views

Re: [DISCUSS] improving visibility for CouchDB-maintained independent Erlang apps

2021-10-29 Thread Nick Vatamaniuc
Good idea, Adam. Some of those are pretty nice applications. Technically there are difficulties around rebar3 compatibility for NIFs. It might be easier to make them developer friendly after we switched the whole CouchDB project to rebar3. The non-NIF apps can be used already as source

Re: [DISCUSS] improving visibility for CouchDB-maintained independent Erlang apps

2021-10-29 Thread Adam Kocoloski
Ah! That .asf.yaml configuration is neat, thanks for pointing it out. Good point on the source releases — do you have anything in particular in mind when you talk about making it simpler for the community at large? Adam > On Oct 28, 2021, at 10:48 PM, Joan Touzet wrote: > > On 28/10/2021