Hello Denis and all, Any chance the new feature broke multiple object updates via a single email (without using the dry-run option, ofc.)? We seem to be getting error messages when trying to do that, I've already notified auto-dbm@ about it. Aris Lambrianidis AMS-IX B.V. Tel.+31 (0)6 23 59 41 58 http://www.ams-ix.net/ On Sep 23, 2013, at 15:50 , Denis Walker <denis@ripe.net> wrote:
Dear colleagues,
Release 1.69 of the RIPE Database has now been fully deployed.
Regards,
Denis Walker Business Analyst RIPE NCC Database Team
-------- Original Message -------- Subject: [db-wg] RIPE Database Release 1.69 Available Soon Date: Mon, 09 Sep 2013 15:27:50 +0200 From: Denis Walker <denis@ripe.net> Organization: RIPE NCC To: Database WG <db-wg@ripe.net>, NCC Services WG <ncc-services-wg@ripe.net>
Dear colleagues,
The RIPE NCC is pleased to announce that we have deployed a new release of the RIPE Database to the TEST Database environment. Detailed information about the new release, including dates and information about the changes can be found here: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.69
Of special note in this release is the inclusion of "dry-run". Using the dry-run function you can test whether an update would succeed or not. The update procedure runs as normal except that no change is made to the database. Find out more about the dry-run function here: https://labs.ripe.net/Members/denis/dry-run-testing-in-the-ripe-database
Due to recent issues with the REST API, we've extended the migration period up until the 1.70 release. This release is currently scheduled for the end of October.
If you have any questions or comments, we look forward to hearing them!
Regards,
Denis Walker Business Analyst RIPE NCC Database Team