couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <>
Subject Re: [DISCUSS] Fauxton Release 1.x / 2.0
Date Mon, 12 May 2014 01:18:23 GMT
HI Robert,

thanks for raising this question (instead of me)!

I'd like to add one moment about releasing Fauxton in one of CouchDB
1.x: currently with Futon we ships not web admin interface, but also a
couple of JavaScript libraries that was traditionally been used by
various couchapps: jquery, jquery.couch, jquery.ui and others client
library which is very handy for making rich and interactive show and
list functions. That becomes common practice to reuse them in own
couchapp instead of shipping them separately. So, if we tends to
replace Futon in 1.x we have to keep all these libraries at all their
current locations - otherwise we'll introduce breaking change.

Releasing Fauxton with BigCouch as 2.0 gives us green light to remove
all these JS batteries from CouchDB without guilty that we've broke
something (since BigCouch already introduces some breaking changes

So I'm +1 for release Fauxton as 2.0: this gives more time to make it
better, this removes headaches with keeping our JS batteries, this
makes 2.0 release more awesome. Seems like it would be much more easy
way to go. For 1.x users Fauxton also remains available and we can (we
should) provide instructions how to keep it up-to-dated (e.g.
replicate it from or build from


On Mon, May 12, 2014 at 1:40 AM, Robert Kowalski <> wrote:
> The BigCouch Merge is doing well and there was the topic regarding the
> Fauxton Release during the last meeting on Wednesday. I think there was
> agreement, that Fauxton will be definitly replacing Futon in 2.0.
> After reading the log I had a short chat with Joan regarding the topic and
> the BigCouch merge is from a gut feeling more a matter of weeks and not
> months.
> Basically we can:
>  - Release Fauxton as a 1.x
>  - Release Fauxton with BigCouch as 2.0
> I would like to get with you into the discussion how we should release
> Fauxton (1.7 or 2.0 - or maybe even on a patchlevel like 1.6.1), how far
> the development of Fauxton is and what is definitely missing for a release
> or blocking it, like "Clarify Futon/Fauxton transition" (
> Best,
> Robert

View raw message