[PDB Announce] Call for testing your network record in advance of upcoming v2.22.0 release at 2020-08-26 04:00 UTC

[Stephen McManus]

All,

The next release of PeeringDB will involve the re-enabling of the IX-F JSON Importer - a tool which syncs data from IXes into PeeringDB programatically. There's quite a few new features, and we haven't seen the volume of testing from the community we'd hope for such a major feature change.

We would like the help of all network operators to perform the below steps to help test the IX-F JSON Importer.

1) Login at https://beta.peeringdb.com/

2) Search for the network you manage and go to the page.

3) If your page contains "Review suggestions", please review the suggestions and test accepting them or dismissing them as appropriate.

4) Please report any bugs or other problems with this new feature to support at peeringdb.com. 


IX Operators - if you have an IX-F JSON export, please configure your URL, and to share this call for testing with your members.  There may be instances where members are able to provide feedback regarding problems with your IX-F JSON export.  The more these are 
discovered and corrected in advance of the production release, the better.

We are making this explicit call for testing because we need your help to ensure wide testing coverage *before* the release hits production and potentially causes problems. Please take a few minutes today to perform the steps above.

Note: The beta site's data is not written to production - feel free to alter it and edit it as much as you'd like, without fear of it reaching production. Similarly, do not expect the data to match the current production data set 100%. There will be differences.

Details on these changes are up at:

 https://youtu.be/mtT_HojbIPs
 https://docs.peeringdb.com/presentation/20200817-dtf-implementation.pdf

Steve McManus on behalf of PeeringDB ProductCom



> On Aug 6, 2020, at 4:27 PM, Stephen McManus <smcmanus at peeringdb.com> wrote:
> 
> Apologies for the multiple reschedules, but we continue to find room for improvement in the major feature changes happening in this release. 
> 
> The production deployment is now scheduled for 2020-08-26 04:00 UTC. 
> 
> We appreciate the continued feedback from the community to keep PeeringDB running well!
> 
> -Steve
> 
> 
> 
> 
>> On Jul 23, 2020, at 1:52 PM, Stephen McManus <smcmanus at peeringdb.com> wrote:
>> 
>> Due to issues found after the beta release, we have rescheduled this release to give us more time to address those issues. A new beta will be deployed by 2020-07-27.
>> 
>> The production deployment is now scheduled for 2020-08-12 04:00 UTC. 
>> 
>> Thanks to everyone who gave feedback on the beta release, it really helps ensure high quality features in PeeringDB. 
>> 
>> -Steve
>> 
>> 
>> 
>> 
>>> On Jul 15, 2020, at 10:42 AM, Stephen McManus <smcmanus at peeringdb.com> wrote:
>>> 
>>> On Wednesday, July 29th at 04:00 UTC, the current beta site will be deployed unless any critical issues are found. This release contains several major changes to PeeringDB, so we are adding an extra week for beta testing. 
>>> 
>>> Your help in verifying that the upgrade went well by thoroughly testing https://beta.peeringdb.com would be greatly appreciated. Please review the changes and test against the beta site as necessary to prepare for a production roll out. In addition, we will also release the language packs that have reached maturity since our last release.
>>> 
>>> Preview of the release is at: 
>>> https://beta.peeringdb.com
>>> 
>>> Release notes for v2.22.0 are here: 
>>> https://docs.peeringdb.com/release_notes/#release-2220
>>> 
>>> Highlights for this release include:
>>> * Implementations of recommendations from the Data Ownership Task Force. This significantly changes how PeeringDB handles data from IX-F imports.
>>> * Data integrity and safety checks at multiple levels (application and database)
>>> 
>>> We will be holding a webinar on July 21st to explain some of these changes to the community in more detail. Look forward to an announcement about that shortly. 
>>> 
>>> As always, let us know at support at peeringdb.com with any comments/questions/concerns.
>>> 
>>> Steve McManus on behalf of PeeringDB ProductCom
>>> 
>>> 
>>> 
>>> 
>> 
>