Dear colleagues, RIPE Database release 1.112 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Thursday 16th May. The 1.112 release has the following main changes: * NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432) * Set Charset Flag (#1450) * Don't allow "mnt-lower" on assignments (#1452) * Fixed Syncupdates HELP Bug (#1453) * RDAP Link Title is a String not List (#1445) * Route ROA checker (#1416) * Allow inverse query for sponsoring-org from all addresses (#1431) * Return 404 on invalid NRTMv4 notification file path (#1422) The release notes are on the website: https://rc.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-112 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 30th April. Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC
Dear colleagues, We have now deployed Whois 1.112 to production. Regards Ed Shryane RIPE NCC
On 2 May 2024, at 13:20, Edward Shryane <eshryane@ripe.net> wrote:
Dear colleagues,
RIPE Database release 1.112 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Thursday 16th May.
The 1.112 release has the following main changes:
* NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432) * Set Charset Flag (#1450) * Don't allow "mnt-lower" on assignments (#1452) * Fixed Syncupdates HELP Bug (#1453) * RDAP Link Title is a String not List (#1445) * Route ROA checker (#1416) * Allow inverse query for sponsoring-org from all addresses (#1431) * Return 404 on invalid NRTMv4 notification file path (#1422)
The release notes are on the website: https://rc.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-112
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 30th April.
Please let us know if you find any issues with this release in the RC environment.
Regards Ed Shryane RIPE NCC
* NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432)
Hey folks, I tried to just set one of my allocations with this, but I can't see the option on webupdates. am I missing something or is there more things needed before I can set this? Cheers Ben On Thu, 16 May 2024 at 10:05, Edward Shryane via db-wg <db-wg@ripe.net> wrote:
Dear colleagues,
We have now deployed Whois 1.112 to production.
Regards Ed Shryane RIPE NCC
On 2 May 2024, at 13:20, Edward Shryane <eshryane@ripe.net> wrote:
Dear colleagues,
RIPE Database release 1.112 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Thursday 16th May.
The 1.112 release has the following main changes:
* NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432) * Set Charset Flag (#1450) * Don't allow "mnt-lower" on assignments (#1452) * Fixed Syncupdates HELP Bug (#1453) * RDAP Link Title is a String not List (#1445) * Route ROA checker (#1416) * Allow inverse query for sponsoring-org from all addresses (#1431) * Return 404 on invalid NRTMv4 notification file path (#1422)
The release notes are on the website: https://rc.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-112
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 30th April.
Please let us know if you find any issues with this release in the RC environment.
Regards Ed Shryane RIPE NCC
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
Hi Ben,
On 20 May 2024, at 15:53, Ben Cartwright-Cox <ripencc@benjojo.co.uk> wrote:
* NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432)
Hey folks, I tried to just set one of my allocations with this, but I can't see the option on webupdates. am I missing something or is there more things needed before I can set this?
Cheers Ben
Apologies, this is a bug. You should be allowed to change between ALLOCATED PA and ALLOCATED-ASSIGNED PA on the modify inetnum page, but ALLOCATED-ASSIGNED PA is missing. A workaround is to paste the inetnum object into Syncupdates and change the status there: https://apps.db.ripe.net/db-web-ui/syncupdates Regards Ed Shryane RIPE NCC
Hello Ben,
On 20 May 2024, at 18:37, Edward Shryane <eshryane@ripe.net> wrote:
... Apologies, this is a bug. You should be allowed to change between ALLOCATED PA and ALLOCATED-ASSIGNED PA on the modify inetnum page, but ALLOCATED-ASSIGNED PA is missing.
We've now deployed a fix for this bug, it's now possible to change between ALLOCATED PA and ALLOCATED-ASSIGNED PA on the modify inetnum page. Apologies for any inconvenience. Regards Ed Shryane RIPE NCC
Thanks! I've managed to set this now, For what it's worth, it is still not possible to set this from the "Update Object" button from the "My Resources" flow, but if I use the "Ripe Database" button and search for my object, press update object from there, then I can do it :) On Tue, 21 May 2024 at 09:25, Edward Shryane <eshryane@ripe.net> wrote:
Hello Ben,
On 20 May 2024, at 18:37, Edward Shryane <eshryane@ripe.net> wrote:
... Apologies, this is a bug. You should be allowed to change between ALLOCATED PA and ALLOCATED-ASSIGNED PA on the modify inetnum page, but ALLOCATED-ASSIGNED PA is missing.
We've now deployed a fix for this bug, it's now possible to change between ALLOCATED PA and ALLOCATED-ASSIGNED PA on the modify inetnum page.
Apologies for any inconvenience.
Regards Ed Shryane RIPE NCC
participants (2)
-
Ben Cartwright-Cox -
Edward Shryane