(warning, grumpy rant forthcoming...)
On Wed, Mar 6, 2013 at 7:14 PM, Noah Slater nsla...@apache.org wrote:
Thoughts?
It seems to me that a lot of this hinges on releases. Releases
generate publicity and therefore developer interest, thus developer
engagement. Releases make sure that work
On Mar 7, 2013, at 12:04 , Dirkjan Ochtman dirk...@ochtman.nl wrote:
(warning, grumpy rant forthcoming...)
Dirkjan,
understood, loud and clear. And I think we all agree with you :)
In fact, we made a few changes to the way we manage the code and releases
to improve all of that, but I think
Agreed. Thanks for the honest feedback. Massively appreciated.
I have been very frustrated with the 1.3.0 release. It was, and still is,
supposed to be the first of our regular releases. Unfortunately, the
release was mired with a raft of CVEs that came first, and then some thorny
blockers. Not
+1. We are conscious of our release process failings but it's great to
see an uninhibited reminder like this.
We're aiming for regular, frequent releases after this one, as Noah
says. I want to see that process so regular that it becomes boring.
You should come to expect that a fix is out within
There's a lot of work that could be done to a lot of the internals of
CouchDB to clean things up and put us back in a place where we can be
quicker to innovate.
1. Rewrite the HTTP layer to not be a gobbledygook function call
spiderweb for request dispatching. Whether we use something like
Devs,
We now have a new Git repository:
https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git
The purpose of this repository will be for collecting scripts, and other
sundry items, as needed by the PMC and the committers for the
administration of the project.
The repository is public.
Clone from https://git-wip-us.apache.org/repos/asf/couchdb-admin.git
On Thu, Mar 7, 2013 at 11:50 AM, Noah Slater nsla...@apache.org wrote:
Devs,
We now have a new Git repository:
https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git
The purpose of this repository will be for
Updated Branches:
refs/heads/master [created] d110c3332
Initial commit
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/d110c333
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-admin/tree/d110c333
Email template tweeks
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/04160c5f
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-admin/tree/04160c5f
Diff:
Remove clipboard operations
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/f5283339
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-admin/tree/f5283339
Diff:
Updated Branches:
refs/heads/master d110c3332 - 419d52ac3
Add license information
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/419d52ac
Tree:
Updated Branches:
refs/heads/master 419d52ac3 - b530ddcc8
Copy and paste error, removed irrelevent licenses from LICENSE
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/b530ddcc
Tree:
Updated Branches:
refs/heads/master b530ddcc8 - 02caf3639
Fix up license headers and add minimal documentation
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/02caf363
Tree:
Updated Branches:
refs/heads/master 02caf3639 - 4007779db
Add vote_committer.txt template
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/4007779d
Tree:
On Mar 7, 2013, at 20:50 , Noah Slater nsla...@apache.org wrote:
Devs,
We now have a new Git repository:
https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git
The purpose of this repository will be for collecting scripts, and other
sundry items, as needed by the PMC and the
I figured we should leave commits@couchdb for changes to CouchDB.
We were already sending wiki diffs, and dist dir changes to dev, so this
seemed like a natural move.
Again, this is just for a few admin scripts, email templates, etc.
On 7 March 2013 21:06, Jan Lehnardt j...@apache.org wrote:
Can someone help me out with this please?
(This is NOT blocking the release, I am just going through my task list.)
Thanks,
On 27 February 2013 19:41, Noah Slater nsla...@apache.org wrote:
Devs,
Can one of you see to the 1.1.1 entry in CHANGES please? (Please announce
you're about to do
Thanks for calling this to action Noah!
My personal list for this year:
-1. Get people excited to contribute to CouchDB.
0. Help remove roadblocks for any sort of contribution, docs, code, tests,
bugs, whatever it takes.
1. A bunch of features that I’d like to rally some activity around, as
On Mar 7, 2013, at 22:10 , Noah Slater nsla...@apache.org wrote:
I figured we should leave commits@couchdb for changes to CouchDB.
We were already sending wiki diffs, and dist dir changes to dev, so this
seemed like a natural move.
Again, this is just for a few admin scripts, email
done.
On Mar 7, 2013, at 22:13 , Noah Slater nsla...@apache.org wrote:
Can someone help me out with this please?
(This is NOT blocking the release, I am just going through my task list.)
Thanks,
On 27 February 2013 19:41, Noah Slater nsla...@apache.org wrote:
Devs,
Can one of
Danke!
On 7 March 2013 21:30, Jan Lehnardt j...@apache.org wrote:
done.
On Mar 7, 2013, at 22:13 , Noah Slater nsla...@apache.org wrote:
Can someone help me out with this please?
(This is NOT blocking the release, I am just going through my task list.)
Thanks,
On 27 February
Google received a request to start sending Alerts for the search
[ CouchDB ] to dev@couchdb.apache.org.
Verify this Google Alert request:
http://www.google.ie/alerts/verify?hl=engl=ies=AB2Xq4i-W3zk2bmj3ODVDws-gMWOEOaYKGc7DIg
Cancel this Google Alert request:
Devs,
I have asked Sally to forward us any PR news about CouchDB.
I've also just set up a weekly Google Alert for CouchDB that will post
news to the dev list. Now, this might be a really terrible idea. But it
might also be a really good idea. And I guess we won't know until we
receive a few of
Okay, so the Google Alerts thing got cancelled. Thanks whoever that was! ;)
Had a chat with Infra, and they don't like this sort of thing being sent to
a list for exactly that reason.
I will have them sent to me and just forward interesting bits for now.
On 7 March 2013 21:33, Noah Slater
Author: nslater
Date: Thu Mar 7 21:47:52 2013
New Revision: 1528
Log:
Renaming to fit into new dist dir heirarchy
Added:
dev/couchdb/binary/
dev/couchdb/source/
Removed:
dev/couchdb/packages/
dev/couchdb/releases/
Author: nslater
Date: Thu Mar 7 21:52:39 2013
New Revision: 1530
Log:
Update KEYS with new sigs
Modified:
release/couchdb/KEYS
Modified: release/couchdb/KEYS
==
--- release/couchdb/KEYS (original)
+++
Updated Branches:
refs/heads/master 4007779db - 462dc2bda
Some incremental improvements
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/462dc2bd
Tree:
My goals right now for CouchDB are focused around how users interact with
the system.
Specifically, I want to see fauxton fully functional with a vibrant plugin
ecosystem.
The other big area is how users extend functionality of CouchDB with
javascript. I think the first big step is switching to
Updated Branches:
refs/heads/master 462dc2bda - c718864a6
Add tag_candidate.sh and fix up other files
Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/c718864a
Tree:
Hello devs,
I would like to propose a new release procedure:
http://wiki.apache.org/couchdb/Release_Procedure
This proposal will pass on lazy consensus, so speak up if you want to
object.
How this differs from the old release procedure:
1) Code level tests (CLI, etap, etc) have been removed.
On 03/07/2013 05:42 PM, Noah Slater wrote:
Hello devs,
I would like to propose a new release procedure:
http://wiki.apache.org/couchdb/Release_Procedure
This proposal will pass on lazy consensus, so speak up if you want to
object.
How this differs from the old release procedure:
1) Code
It means that the only testing that I will do before calling a vote on the
candidate will be basic build system tests. Once the candidate is published
and vote has started, I will download the candidate and test it properly
along with everyone else.
Please remember that I will be calling a
Not sure it'll make the Google alert threshold, but I got Bob to the
bowling alley:
http://twitter.com/davisp/status/309824109905321984
Hooray midwest!
On Thu, Mar 7, 2013 at 3:41 PM, Noah Slater nsla...@apache.org wrote:
Okay, so the Google Alerts thing got cancelled. Thanks whoever that was!
33 matches
Mail list logo
