[db-wg] RIPE Database Release 1.76 Deployed to Production
- Previous message (by thread): [db-wg] RIPE Database Release 1.76 Deployed to Production
- Next message (by thread): [db-wg] RIPE Database Release 1.76 Deployed to Production
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Wed Nov 12 17:22:00 CET 2014
Dear colleagues, apologies, this release was deployed to production today, Wednesday 12 *November*. Regards Ed Shryane RIPE NCC > On 12 Nov 2014, at 17:17, Edward Shryane <eshryane at ripe.net> wrote: > > Dear colleagues, > > RIPE Database software release 1.76 was deployed to the production server on Wednesday, 12 October 2014. > > Regards > > Ed Shryane > RIPE NCC > >> On 14 Oct 2014, at 18:14, Tim Bruijnzeels <tim at ripe.net <mailto:tim at ripe.net>> wrote: >> >> Dear colleagues, >> >> The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.76 to the Release Candidate (RC) environment. >> >> Detailed information about features, changes and how this release might affect your operations, are available in the release notes: >> https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.76 <https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.76> >> >> This release includes many small bug fixes and feature improvements. Notably, we have addressed the following issues: >> - Issue #221: It is now possible to change the name of a PERSON or ROLE object >> - Issue #256: Abuse contact information is now shown when using web lookups >> - Issue #220: Failed update notifications now include a diff of the attempted change >> >> A number of users requested the notification of a failed update to include a diff showing what was attempted to be changed. A consequence of this change is that, if you mistype the password pseudo-attribute (eg "pasword: clear_password"), the notification will include your clear text password. >> >> This is a good time for all maintainers of data in the RIPE Database to review to whom these notifications are sent. The "upd-to:" attribute in a MNTNER object should only include the email address of a person or team in your organisation who deals with security issues. If this team receives such a notification, they should advise the user to change their password. >> >> We invite all users of the RIPE Database to review the new release in the RC environment: >> https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment <https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment> >> >> We look forward to any questions or comments you might have. >> >> Kind regards, >> >> Tim Bruijnzeels >> >> Assistant Manager Software Engineering >> RIPE NCC > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20141112/ab963b28/attachment.html>
- Previous message (by thread): [db-wg] RIPE Database Release 1.76 Deployed to Production
- Next message (by thread): [db-wg] RIPE Database Release 1.76 Deployed to Production
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]