This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Whois Release 1.113
- Previous message (by thread): [db-wg] So what happened last night to the DB?
- Next message (by thread): [db-wg] RIPE Policy document updated “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” (ripe-826)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Mon Jun 17 17:34:57 CEST 2024
Dear colleagues, RIPE Database release 1.113 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Monday 1st July. The 1.113 release has the following main changes: * Inetnum AGGREGATED-BY-LIR status (implements RIPE-822 policy) (#1467) * Enable Client Auth Certificate for REST API lookup (#1475) * ROA Overlapping INVALID ROA and VALID ROA fix (#1470) * Java 21 Support (#1440) The release notes are on the website: https://apps.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-113 More information on the Release Candidate environment can be found on our website: https://apps.db.ripe.net/docs/Release-Notes/ The data in the RC environment is a dummified copy of production from 12th June. Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC
- Previous message (by thread): [db-wg] So what happened last night to the DB?
- Next message (by thread): [db-wg] RIPE Policy document updated “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” (ripe-826)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]