Benjamin Young created COUCHDB-2029:
---
Summary: Consolidate CSS/LESS class name usage to minimize
custom-ness
Key: COUCHDB-2029
URL: https://issues.apache.org/jira/browse/COUCHDB-2029
Project:
[
https://issues.apache.org/jira/browse/COUCHDB-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870734#comment-13870734
]
Benjamin Young commented on COUCHDB-2029:
-
This is already in progress on this
[
https://issues.apache.org/jira/browse/COUCHDB-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith reassigned COUCHDB-2029:
-
Assignee: Garren Smith
Consolidate CSS/LESS class name usage to minimize custom-ness
Simon Metson created COUCHDB-2030:
-
Summary: Duplicate doc button fails when form is submitted via
enter
Key: COUCHDB-2030
URL: https://issues.apache.org/jira/browse/COUCHDB-2030
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Metson updated COUCHDB-2030:
--
Priority: Minor (was: Major)
Skill Level: New Contributors Level (Easy)
Duplicate
[
https://issues.apache.org/jira/browse/COUCHDB-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870739#comment-13870739
]
Simon Metson commented on COUCHDB-2030:
---
Fix for this up in
[
https://issues.apache.org/jira/browse/COUCHDB-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith resolved COUCHDB-2030.
---
Resolution: Fixed
Duplicate doc button fails when form is submitted via enter
[
https://issues.apache.org/jira/browse/COUCHDB-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith reassigned COUCHDB-2030:
-
Assignee: Garren Smith
Duplicate doc button fails when form is submitted via enter
GitHub user BigBlueHat opened a pull request:
https://github.com/apache/couchdb/pull/132
made couchserver configurable via settings.json
Making couchserver configurable via settings.json means you can have
Fauxton work against a proxy of a CouchDB-compatible server hosted elsewhere
GitHub user BigBlueHat opened a pull request:
https://github.com/apache/couchdb/pull/133
added release to test task list
Simplest possible fix. :grin:
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BigBlueHat/couchdb
[
https://issues.apache.org/jira/browse/COUCHDB-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-2002:
Summary: Implement a hard cap on OS process count in couch_proc_manager
(was: Implement
GitHub user BigBlueHat opened a pull request:
https://github.com/apache/couchdb/pull/134
Fauxton tests on travis
@Kxepal this hopefully gets Travis running working Fauxton tests.
It's branched off of my other branch that's pending in #133, so merging
this obviates the need
[
https://issues.apache.org/jira/browse/COUCHDB-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson resolved COUCHDB-2004.
Resolution: Fixed
fixed on 1843-feature-bigcouch.
Remove references to missing modules
Dear community,
Please join our weekly IRC meeting, Wednesday 2013-01-15 at 20:00 UTC.
Everyone is welcome to attend this meeting.
If you have anything to put on the agenda, please reply to this email
or mention it at the start of the meeting.
The meeting will take place in:
I've recently been having discussions about how to handle the
repository configuration for various bits of CouchDB post-merge. The
work that Benoit has been doing on the rcouch merge branch have also
touched on this topic as well.
The background for those unfamiliar is that the standard operating
On Jan 14, 2014, at 3:22 PM, Paul Davis paul.joseph.da...@gmail.com wrote:
I'd like to propose that we move to having a repository for each
application/dependency that we use to build CouchDB. Each repository would be
hosted on ASF infra and mirrored to GitHub as expected.
Good idea. It's
+1. The monolithic design makes development and pull requests easier, one
vs many for some features, but I think this is generally outweighed by the
pros outlined. I think a broken-out design makes it easier to add
alternate functionality in places, or swap in/out things to test with.
I agree
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis paul.joseph.da...@gmail.comwrote:
I've recently been having discussions about how to handle the
repository configuration for various bits of CouchDB post-merge. The
work that Benoit has been doing on the rcouch merge branch have also
touched on
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis paul.joseph.da...@gmail.comwrote:
I would also point out that even though our main repo would need to
fetch other dependencies from the internet to build the final output,
we fully intend that our release tarballs would *not* have this
Just a quick status about the work has been done since the last status. I
had to pause the merge during the last 2 days, but it should be finished
tomorrow now.
Since the last status I made the following changes:
- After toying with the sources and looked/discussed around, I put back
everything
On Jan 14, 2014, at 8:47 PM, Benoit Chesneau bchesn...@gmail.com wrote:
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis
paul.joseph.da...@gmail.comwrote:
I would also point out that even though our main repo would need to
fetch other dependencies from the internet to build the final
[
https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871736#comment-13871736
]
Nathan Caza commented on COUCHDB-1946:
--
So, I've been experiencing this, I've had a
On Jan 14, 2014, at 8:37 PM, Benoit Chesneau bchesn...@gmail.com wrote:
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis
paul.joseph.da...@gmail.comwrote:
I've recently been having discussions about how to handle the
repository configuration for various bits of CouchDB post-merge. The
23 matches
Mail list logo
