Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

2018-07-05 Thread Alexander Shorin
1.x, you was good and we'll never forget you, but it's time to move forward to better CouchDB future. +1, bury it! -- ,,,^..^,,, On Wed, Jul 4, 2018 at 11:51 PM, Joan Touzet wrote: > DISCLAIMER: This is a non-technical proposal to make a project decision. > Per our Bylaws[1], this means that it

[NEWS] The CouchDB weekly news for July 5th is out!

2018-07-05 Thread Emily Daves
Hello hello! The Apache CouchDB weekly news is now live at: http://blog.couchdb.org/2018/07/05/couchdb-weekly-news-july-5-2018 Highlights include new releases in the CouchDB universe, some tutorials on Hyperledger Fabric, and a great idea to reduce wildfires caused by firework displays--dron

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

2018-07-05 Thread Paul Davis
+1 On Thu, Jul 5, 2018 at 5:18 AM Andy Wenk wrote: > > +1 > > -- > Andy Wenk > Hamburg - Germany > RockIt! > > GPG public key: > http://pgp.mit.edu/pks/lookup?op=get&search=0x45D3565377F93D29 > > > > > On 5. Jul 2018, at 11:21, Garren Smith wrote: > > > > +1 to this as well. We just don't have en

Re: Call for "Must-fix" issues

2018-07-05 Thread Jan Lehnardt
> On 5. Jul 2018, at 13:54, Mad, Pink and Dangerous to Know > wrote: > > This isn't really a "fix" per se, but one of the reasons I still use > CouchDB 1.x is the change log. I have a homemade local syncing library for > Livecode that I use that is heavily dependent on the old _changes api. I

Re: Call for "Must-fix" issues

2018-07-05 Thread Mad, Pink and Dangerous to Know
This isn't really a "fix" per se, but one of the reasons I still use CouchDB 1.x is the change log. I have a homemade local syncing library for Livecode that I use that is heavily dependent on the old _changes api. I've been working on changing it for 2.x, but it involves having to add my own versi

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

2018-07-05 Thread Andy Wenk
+1 -- Andy Wenk Hamburg - Germany RockIt! GPG public key: http://pgp.mit.edu/pks/lookup?op=get&search=0x45D3565377F93D29 > On 5. Jul 2018, at 11:21, Garren Smith wrote: > > +1 to this as well. We just don't have enough dev's to do this, and I would > rather see us focusing on CouchDB 2.x >

Re: Call for "Must-fix" issues

2018-07-05 Thread Kai Griffin
Thanks, Garren, I’ll look for that in the latest release. But for this, I’d certainly prefer us to migrate to 2.x Cheers, Kai On 5 July 2018 at 11:16:11, Garren Smith (gar...@apache.org(mailto:gar...@apache.org)) wrote: > Hi Kai, > > Fauxton now supports a table view which allows you to se

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

2018-07-05 Thread Garren Smith
+1 to this as well. We just don't have enough dev's to do this, and I would rather see us focusing on CouchDB 2.x On Thu, Jul 5, 2018 at 10:26 AM, Robert Samuel Newson wrote: > +1 > > I am also for the proposal to officially deprecate couchdb 1.x. > > I would not want to see back-porting or new

Re: Call for "Must-fix" issues

2018-07-05 Thread Garren Smith
Hi Kai, Fauxton now supports a table view which allows you to see many documents at once as well as choosing which key values to see in the table. Its been out for a while so I'm sure its in the current release but will definitely be in the next. Cheers Garren On Thu, Jul 5, 2018 at 9:32 AM, Kai

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

2018-07-05 Thread Robert Samuel Newson
+1 I am also for the proposal to officially deprecate couchdb 1.x. I would not want to see back-porting or new feature work in 1.x even if a theoretical 3 person team were to materialise. Of course any such team that does appear could fork couchdb 1.x and work on it independently (the only cav

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

2018-07-05 Thread Jan Lehnardt
Hi Johs, while I understand that corporate policies involved with saying a version is end-of-life (e.g. “we must migrate off it”), there is nobody stopping anyone from continuing to run 1.x in a setup where it is already running fine and security updates are not a concern. In fact we have a numbe

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

2018-07-05 Thread Jan Lehnardt
> On 4. Jul 2018, at 22:51, Joan Touzet wrote: > > DISCLAIMER: This is a non-technical proposal to make a project decision. > Per our Bylaws[1], this means that it should "normally be made with lazy > consensus, or by the entire community using discussion-led > consensus-building, and not thro

Re: Call for "Must-fix" issues

2018-07-05 Thread Kai Griffin
As developers who spend a lot of time in the CouchDB web interface, we have held back moving to CouchDB 2.x only because of the change from Futon to Fauxton.  We feel that Fauxton simply does not meet the needs of developers as well as Futon did. It seems to be targeted more at non-devs: it’s ve

Call for "Must-fix" issues

2018-07-05 Thread Johs Ensby
This thread reach out to CouchDB 1.x users to generate a list of "must-fix" issues that is preventing users to upgrade to the latest version of CouchDB. It is in response to Joan's comment below regarding the non-technical proposal to make a project decision to terminate official Apache suppor