-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please tag/push new Fauxton release for CouchDB 3.0.1/3.1.0 #1271
Comments
@popojargo FYI, I'd like to cut the RC tomorrow, let people test, then we can push to the mirrors Monday announce Tuesday. Fauxton is the very last thing we're waiting on. If the notification change isn't ready, can you release/tag without it? Thanks. |
Travis is green but tests are still flaky. I will merge and tag. Test improvements are being worked on. |
That's fine, we don't need the tests fixed for cutting a CouchDB release. Please tag a 1.2.4 (and if you can, push a new release to npm) and we'll get moving on CouchDB 3.0.1/3.1.0. |
1.2.4 released on github and npm |
Hello @popojargo @Antonio-Maranhao etc.
I intend to cut the CouchDB 3.0.1 and 3.1.0 releases in the next 48 hours. Right now, v1.2.3 is the latest tag available.
I know some patches have landed that were intended to go into the next CouchDB release. Can I get a v1.2.4 tag laid down please?
I know there are some features you'd like to include, such as #1265 . This is the final call - if those can land quickly (and reliably!) I'll include them.
Thanks!
The text was updated successfully, but these errors were encountered: