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/db-wg@ripe.net/
[db-wg] forced remarks (Was: RIPE Database Release 1.73.1 deployed)
- Next message (by thread): [db-wg] forced remarks (Was: RIPE Database Release 1.73.1 deployed)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Fri Jun 13 11:50:04 CEST 2014
On Tue, May 27, 2014 at 04:24:45PM +0200, Denis Walker wrote: > RIPE Database software release 1.73.1 has now been deployed into production. > > The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:" > attribute. We have also modified all legacy INETNUM objects and set the > "status:" to 'LEGACY'. Is it possible to stop forcefully inserting this line: remarks: For information on "status:" attribute read <snip> in one of the next releases? To be more specific: disable enforceRemarksRightBeforeStatus() for remarks about the 'status' attribute. As a method to inform resource-holders that something has changed I think that one-shot inserting of remarks is a good method (next to informing mailing-lists, twitter, etc), but these messages should not be enforced too long. I'm fine with leaving the existing remarks in the DB, just don't enforce on new updates after four weeks or so. Kind regards, Job
- Next message (by thread): [db-wg] forced remarks (Was: RIPE Database Release 1.73.1 deployed)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]