HI Alex I have quite a few concerns about this new release that I have listed below. Cheers denis On 02/11/2015 11:25, Alex Band wrote:
Dear colleagues,
We are happy to announce the deployment of RIPE Database software release 1.83 to the Release Candidate (RC) environment, which has gone live on Friday 30 October.
Is this a new policy to deploy releases on a Friday with only 24/7 engineers keeping an eye on it over the weekend? Then announce it on the Monday so if anything did go wrong over the weekend users may not realise they are using a new software release?
This release is still focussed on seamlessly integrating RIPE NCC Access (SSO) into the webupdates user interface. In addition, several other changes have been made, such as:
I don't see any detailed Release Notes for 1.83 with any references to GitHub issues or links to the new documentation. In fact the Release Notes web page still shows 1.82 as the current release. Release 1.83, shown as a future release for December, refers to deprecating the "changed:" attribute. But that is not mentioned below. Was that done in this release?
- Webupdates will show full object details by default - Partial route object creation has been greatly improved, indicating which maintainer needs to complete the authorisation
Who is this indicated to, the creator of the partial object or the party/parties who need to complete the update? How is it indicated?
- When deleting a person object, you will be prompted to also delete the associated maintainer if it has no other dependencies
Is this just a prompt? I may have plans to use the MNTNER for something else later.
- When trying to delete an object that is still referenced, you will get a list of blocking objects
So if I try to delete a PERSON object referenced in 10,000 INETNUM objects do I get a list of all 10,000 objects?
- Auto-complete of person, role and organisation attributes is now available throughout the interface - The TEST database now has its own URL instead of having to be selected with a radio button
I don't see any of the above changes referenced in the database documentation. Neither are the changes from 1.82 or 1.81 reflected in the documentation. So is the documentation now considered out of date again?
Please let us know if you have any questions or comments.
Kind regards,
Alex Band Product Manager RIPE NCC