Very cool. We've been wanting a packaged version of 2.0 for a while. This might be jumping the gun, but I'm curious to know what the story is for upgrading from previous, non-snap versions is, and how post-snap upgrades will be handled. At first glance, it seems like there is a trade off between having to copy the entire DB per version upgrade, or losing the ability to revert if compaction modifies the DB in a non-backwards-compatible way. How are you handling those situations?
Also, would you consider the snap package to be stable enough for production install once the logistics get sorted out, or is it still experimental? Thanks! Eli On Fri, Dec 16, 2016 at 10:56 AM, Robert Kowalski <r...@kowalski.gd> wrote: > Everything set up, I think we have to figure out when the next release > happens. > > On Fri, Dec 16, 2016 at 2:04 PM, Robert Kowalski <r...@kowalski.gd> wrote: >> Hi Micheal, >> >> thank you so much! You are doing awesome work! >> >> I registered an account: https://cldup.com/1cbKxu0igy.png >> >> Let's chat on IRC regarding the next steps, I don't know how to use >> snap on my Mac. >> >> Best, >> Robert >> >> >> On Fri, Dec 16, 2016 at 3:04 AM, Michael Hall <mhall...@gmail.com> wrote: >>> Over the past few months, with help from rnewsom, jan and others, we've >>> been able to create a Snap[1] package for CouchDB 2.x that I would like >>> to make available through the Snap Store. >>> >>> The Snap Store encourages upstreams to publish their packages >>> themselves, rather than depending on distro developers to do so. >>> Registering a package in the store is currently limited to individual >>> accounts, there's no support yet for teams, which means that someone >>> would need to register "apache-couchdb" as a developer account in the >>> store. They can then share upload rights for the couchdb snap with other >>> individuals, but it needs to be owned by someone to start with. >>> >>> On IRC there was some discussion about how to approach this, with the >>> suggestion that someone on the PMC could register the owning account, >>> using the ASF mailing address[2] and their own email. This should >>> require very little work to setup, and almost no work after the initial >>> setup. So I'm asking if anyone on the PMC would be willing to take this >>> up and help us get the snap package published to users. >>> >>> [1] http://snapcraft.io >>> [2] yes it's asked for, and I agree it shouldn't be needed >>> >>> -- >>> Michael Hall >>> mhall...@gmail.com
