Re: [PROPOSAL] Official roadmap, and merge procedure

2012-06-16 Thread Marco Monteiro
On 16 June 2012 17:45, Noah Slater wrote: > 1. We'd like to proposed formal time-based releases > http://wiki.apache.org/couchdb/Roadmap_Process > > This is a big improvement, but... :) If the QA is good enough, it would be a little better to have feature releases every month or two, support

Re: [PROPOSAL] Official roadmap, and merge procedure

2012-06-16 Thread Martin Hewitt
This is an excellent idea, more predictability is always a Good Thing, regardless of how "big" each release is. Being able to schedule downtime for upgrades on a predictable schedule is a massive tick. Martin Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Saturday, 16 June 2012 at

Re: Rapt about Couch Hack Vienna, June 16 & 17

2012-06-16 Thread Kurt Milam
Just got your tweet - Would appreciate it if you can let me know when a good time to come by the Burggarten is - I can make that this evening. Best Regards, Kurt Milam VP, Software & Internet Services xioup - Stuff that works! http://xioup.com On Sat, Jun 16, 2012 at 7:37 PM, Kurt Milam wrote

Re: Rapt about Couch Hack Vienna, June 16 & 17

2012-06-16 Thread Kurt Milam
Hi Dave, What's the schedule for tonight? I'd like to come by in about an hour or so if it's still going on, or else meet up if you're all going somewhere afterwards. Couldn't make it during the day today, and tomorrow during the day will also be tough. Would love to hear back from you. Best Reg

Re: [PROPOSAL] Official roadmap, and merge procedure

2012-06-16 Thread Dirkjan Ochtman
On Sat, Jun 16, 2012 at 6:45 PM, Noah Slater wrote: > 1. We'd like to proposed formal time-based releases Love it. In fact, I think I proposed it before. I think this will be a much better way of making CouchDB administration easy. > Details of these proposals can be found here: > > http://wiki.

[PROPOSAL] Official roadmap, and merge procedure

2012-06-16 Thread Noah Slater
Devs, A few of us met in Dublin recently, and we discussed the project roadmap. Key takeaways from that meeting: 1. We'd like to proposed formal time-based releases 2. Branch and hack all you like, but if you want to ship something, you have to submit a merge request to an active release branc

couchdb pull request: Fix type logging status codes

2012-06-16 Thread Git at Apache
GitHub user daleharvey opened a pull request: https://github.com/apache/couchdb/pull/27 Fix type logging status codes You can merge this pull request into a Git repository by running: $ git pull https://github.com/daleharvey/couchdb typo-fix Alternatively you can review and a

couchdb pull request: Typo fix

2012-06-16 Thread Git at Apache
Github user daleharvey closed the pull request at: https://github.com/apache/couchdb/pull/26

couchdb pull request: Typo fix

2012-06-16 Thread Git at Apache
GitHub user daleharvey opened a pull request: https://github.com/apache/couchdb/pull/26 Typo fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/daleharvey/couchdb typo-fix Alternatively you can review and apply these changes as

[jira] [Resolved] (COUCHDB-1470) Futon missing/deleted document error popup does not appear

2012-06-16 Thread Jan Lehnardt (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Lehnardt resolved COUCHDB-1470. --- Resolution: Fixed > Futon missing/deleted document error popup does not appear > --

[jira] [Closed] (COUCHDB-1470) Futon missing/deleted document error popup does not appear

2012-06-16 Thread Jan Lehnardt (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Lehnardt closed COUCHDB-1470. - > Futon missing/deleted document error popup does not appear >