Re: [PLANNING] CouchDB 2.1
Hi Joan, Having done some work with the Windows build in the past, I'm happy to try to help with automating it. If you think there's anything I can do, maybe we could have a separate discussion on the steps needed to make it better. Nick > On 16 Dec 2016, at 19:20, Joan Touzet wrote: > > The Windows build process is not 100% automatable right now, nor > has it ever been. There's a bunch more work necessary to make that > happen. Ideally, someone would offer to help me with this. > > The actual *publish* of an approved final build should still be a > manually invoked process, especially because it requires individual > credentials to be used to push the release to the Apache mirrors, > and for the Windows binary, there is a manual Symantec signing > process (though I'm informed the latter can be automated through a > SOAP API [ugh]). We also need to manually say "this is the one" > after the lists have gone through acceptance testing. > > -Joan > > - Original Message - >> From: "Robert Kowalski" >> To: dev@couchdb.apache.org >> Sent: Friday, December 16, 2016 1:55:45 PM >> Subject: [PLANNING] CouchDB 2.1 >> >> Hi, >> >> I wanted to test the waters regarding a CouchDB 2.1 release. Since >> 2.0 >> a few new features and many bug fixes have landed. >> >> I know its holiday season soon and I wanted to kick off the >> discussion >> about a release date for 2.0.1 or 2.1.0. >> >> One thing that worries me (correct me if I am wrong): I think >> releasing CouchDB depends much on Joan and Jan right now, which is >> bad >> (bus factor etc). >> >> I don't know much about the internals of the build process for our >> releases, but I would volunteer to automate the (jenkins?-)build for >> snaps. >> >> Best, >> Robert >>
Re: Publisher account for CouchDB snap
On 12/16/2016 02:10 PM, Eli Stevens (Gmail) wrote: > Very cool. We've been wanting a packaged version of 2.0 for a while. > You can try the snap I built, it's on http://people.ubuntu.com/~mhall119/snaps/ Download it and run "snap install --dangerous couchdb_2.0_amd64.snap" (assuming you're on Ubuntu 16.04 or later) > 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? > There isn't a generic mechanism for the dpkg->snap migration. You could provide tools for that, or just recommend snaps for new installs. Likewise there isn't a generic mechanism for migrating and reverting data in the common (non-versioned) directory, because it would have to be app-specific. There is a new "hook" feature that could be used to run a script on install/update/revert that could then run whatever migration would be needed. > 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? > I would encourage having people test the snap in production-like environments for a while first. I used a very basic configuration and there might need to be more work done to allow it to work for all use cases. The Snap technology is stable enough for production use, but I'd like to see each individual app tested thoroughly before telling people to replace their existing package installs. Michael Hall mhall...@gmail.com > Thanks! > Eli > > On Fri, Dec 16, 2016 at 10:56 AM, Robert Kowalski 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 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 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
Re: [PLANNING] CouchDB 2.1
The Windows build process is not 100% automatable right now, nor has it ever been. There's a bunch more work necessary to make that happen. Ideally, someone would offer to help me with this. The actual *publish* of an approved final build should still be a manually invoked process, especially because it requires individual credentials to be used to push the release to the Apache mirrors, and for the Windows binary, there is a manual Symantec signing process (though I'm informed the latter can be automated through a SOAP API [ugh]). We also need to manually say "this is the one" after the lists have gone through acceptance testing. -Joan - Original Message - > From: "Robert Kowalski" > To: dev@couchdb.apache.org > Sent: Friday, December 16, 2016 1:55:45 PM > Subject: [PLANNING] CouchDB 2.1 > > Hi, > > I wanted to test the waters regarding a CouchDB 2.1 release. Since > 2.0 > a few new features and many bug fixes have landed. > > I know its holiday season soon and I wanted to kick off the > discussion > about a release date for 2.0.1 or 2.1.0. > > One thing that worries me (correct me if I am wrong): I think > releasing CouchDB depends much on Joan and Jan right now, which is > bad > (bus factor etc). > > I don't know much about the internals of the build process for our > releases, but I would volunteer to automate the (jenkins?-)build for > snaps. > > Best, > Robert >
Re: Publisher account for CouchDB snap
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 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 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 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
[PLANNING] CouchDB 2.1
Hi, I wanted to test the waters regarding a CouchDB 2.1 release. Since 2.0 a few new features and many bug fixes have landed. I know its holiday season soon and I wanted to kick off the discussion about a release date for 2.0.1 or 2.1.0. One thing that worries me (correct me if I am wrong): I think releasing CouchDB depends much on Joan and Jan right now, which is bad (bus factor etc). I don't know much about the internals of the build process for our releases, but I would volunteer to automate the (jenkins?-)build for snaps. Best, Robert
Re: Publisher account for CouchDB snap
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 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 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
Re: Publisher account for CouchDB snap
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 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
