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] Proposal: DB object syntax change
- Previous message (by thread): [db-wg] Suggestion of change for inverse query of notify
- Next message (by thread): [db-wg] Proposal: DB object syntax change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Tue Mar 25 21:42:14 CET 2014
On Thu, Feb 06, 2014 at 03:16:26PM +0100, Denis Walker wrote: Dear Denis > The RIPE Database release 1.71 that was deployed to production this week > was prepared in the beginning of December. Any issues reported > afterwards that were not critical for the user were scheduled to be > fixed in version 1.72, which we were working on at that time. Right now, another 1.5 month after your mail and 3 months after my initial raport I have read about the new release of RIPE Database. As pointed above, the release 1.72 should contain any issues reported in the meantime that were not critical for the user and due to that fact were not included in the 1.71 release. It seems that the mistake with person-name is still not corrected. That's why I was then so sceptical about this kind of statements. :( I have to admit that this error is probably still not corrected due to the fact that the patch was only applied to the whois-client/src/main/java/net/ripe/db/whois/common/rpsl/AttributeSyntax.java file (https://github.com/RIPE-NCC/whois/commit/09fbbab3676a39a905b7972822596f1f75fc6ab4) and has not been applied to the whois-client/src/main/java/net/ripe/db/whois/common/rpsl/AttributeType.java file. If this is the case, this means that there is a flaw in the testing procedure and no-one have checked if the patch (hope that only this one) is correct. Moreover - the community was assured that the mistake with description of Error 108 will be fixed shortly. It seems that it hasn't been fixed yet. Best regards, Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [db-wg] Suggestion of change for inverse query of notify
- Next message (by thread): [db-wg] Proposal: DB object syntax change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]