From grizz at 20c.com  Wed Jul  1 07:44:05 2020
From: grizz at 20c.com (Matt Griswold)
Date: Wed, 1 Jul 2020 14:44:05 +0000
Subject: [PDB Announce] PeeringDB 2.21.0 release at 2020-07-01T0400Z
In-Reply-To: <89EBD586-00FB-425B-9383-C4F962A55AE4@peeringdb.com>
References: <89EBD586-00FB-425B-9383-C4F962A55AE4@peeringdb.com>
Message-ID: <20200701144405.11706968@segv>

This has been released, let us know with any issues.

Please note, for doing a local sync with the python client, this
requires updating to django-peeringdb 2.1.

* Stephen McManus <smcmanus at peeringdb.com> [200624 16:24 -0400]:
> On Wednesday, July 1st at 0400Z, the current beta site will be
>   deployed unless any critical issues are found. 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.21.0 are here: 
> https://docs.peeringdb.com/release_notes/#release-2210
> 
> Highlights for this release include:
> * Two Factor Auth (2FA) support being added to better secure user
>   accounts
> * Several improvements for updates and delete actions, including
>   better error handling and hints to users
> * Some usability and UI improvements
> 
> As always, let us know at support at peeringdb.com with any
>   comments/questions/concerns.
> 
> Steve McManus on behalf of PeeringDB ProductCom
> _______________________________________________
> Pdb-announce mailing list
> Pdb-announce at lists.peeringdb.com
> https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce


From Jan.Boogman at swisscom.com  Wed Jul  1 08:09:58 2020
From: Jan.Boogman at swisscom.com (Jan.Boogman at swisscom.com)
Date: Wed, 1 Jul 2020 15:09:58 +0000
Subject: [PDB Announce] PeeringDB 2.21.0 release at 2020-07-01T0400Z
In-Reply-To: <20200701144405.11706968@segv>
References: <89EBD586-00FB-425B-9383-C4F962A55AE4@peeringdb.com>,
 <20200701144405.11706968@segv>
Message-ID: <GV0P278MB0130B949FB802F602C27C5DA956C0@GV0P278MB0130.CHEP278.PROD.OUTLOOK.COM>

Hi Matt

I have upgraded  to Django-peeringdb 2.1, but it doesn't play well:

pdb at pdb2:~$ peeringdb sync
Traceback (most recent call last):
  File "/usr/local/bin/peeringdb", line 11, in <module>
    sys.exit(main())
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/cli.py", line 62, in main
    return handler(config=cfg, **vars(options))
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/commands.py", line 20, in _wrapped
    r = func(*a, **k)
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/commands.py", line 212, in handle
    client = Client(config, **kwargs)
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/client.py", line 44, in __init__
    peeringdb.initialize_backend(orm_name, **orm_config)
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/__init__.py", line 84, in initialize_backend
    B = supportmod.load_backend(**kwargs)
  File "/home/pdb/.local/lib/python3.6/site-packages/django_peeringdb/client_adaptor/load.py", line 46, in load_backend
    backend.Backend().migrate_database()
  File "/home/pdb/.local/lib/python3.6/site-packages/django_peeringdb/client_adaptor/backend.py", line 211, in migrate_database
    call_command("migrate", interactive=False, verbosity=verbosity)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/__init__.py", line 148, in call_command
    return command.execute(*args, **defaults)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
    res = handle_func(*args, **kwargs)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
    fake_initial=fake_initial,
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/operations/fields.py", line 249, in database_forwards
    schema_editor.alter_field(from_model, from_field, to_field)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 535, in alter_field
    old_db_params, new_db_params, strict)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 648, in _alter_field
    old_default = self.effective_default(old_field)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 233, in effective_default
    return field.get_db_prep_save(self._effective_default(field), self.connection)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/models/fields/related.py", line 937, in get_db_prep_save
    return self.target_field.get_db_prep_save(value, connection=connection)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 789, in get_db_prep_save
    return self.get_db_prep_value(value, connection=connection, prepared=False)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 958, in get_db_prep_value
    value = connection.ops.validate_autopk_value(value)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/mysql/operations.py", line 181, in validate_autopk_value
    raise ValueError('The database backend does not accept 0 as a '
ValueError: The database backend does not accept 0 as a value for AutoField.

pdb at pdb2:~$ pip3 freeze | grep peeringdb
django-peeringdb==2.1.0
peeringdb==1.0.0
pdb at pdb2:~$


Anything I am missing?

Best regards
Jan

________________________________
Von: Pdb-announce <pdb-announce-bounces at lists.peeringdb.com> im Auftrag von Matt Griswold <grizz at 20c.com>
Gesendet: Mittwoch, 1. Juli 2020 16:44
An: Stephen McManus <smcmanus at peeringdb.com>
Cc: pdb-announce at lists.peeringdb.com <pdb-announce at lists.peeringdb.com>
Betreff: Re: [PDB Announce] PeeringDB 2.21.0 release at 2020-07-01T0400Z

This has been released, let us know with any issues.

Please note, for doing a local sync with the python client, this
requires updating to django-peeringdb 2.1.

* Stephen McManus <smcmanus at peeringdb.com> [200624 16:24 -0400]:
> On Wednesday, July 1st at 0400Z, the current beta site will be
>   deployed unless any critical issues are found. Your help in
>   verifying that the upgrade went well by thoroughly testing
>   https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbeta.peeringdb.com%2F&amp;data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&amp;sdata=5DW7w18DHEK0MKkH25xO5Bc0Jq4NC18ZfBkvJMQZFas%3D&amp;reserved=0 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbeta.peeringdb.com%2F&amp;data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&amp;sdata=5DW7w18DHEK0MKkH25xO5Bc0Jq4NC18ZfBkvJMQZFas%3D&amp;reserved=0
>
> Release notes for v2.21.0 are here:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.peeringdb.com%2Frelease_notes%2F%23release-2210&amp;data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&amp;sdata=uyr9afhTNwdiHTmgzc8b5COde2H2CffrPAG6wvIH98c%3D&amp;reserved=0
>
> Highlights for this release include:
> * Two Factor Auth (2FA) support being added to better secure user
>   accounts
> * Several improvements for updates and delete actions, including
>   better error handling and hints to users
> * Some usability and UI improvements
>
> As always, let us know at support at peeringdb.com with any
>   comments/questions/concerns.
>
> Steve McManus on behalf of PeeringDB ProductCom
> _______________________________________________
> Pdb-announce mailing list
> Pdb-announce at lists.peeringdb.com
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.peeringdb.com%2Fcgi-bin%2Fmailman%2Flistinfo%2Fpdb-announce&amp;data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&amp;sdata=iurTCB9sypoZZENT9cOdgowqIFMkjO4mT%2FqJVz7eV08%3D&amp;reserved=0

_______________________________________________
Pdb-announce mailing list
Pdb-announce at lists.peeringdb.com
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.peeringdb.com%2Fcgi-bin%2Fmailman%2Flistinfo%2Fpdb-announce&amp;data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&amp;sdata=iurTCB9sypoZZENT9cOdgowqIFMkjO4mT%2FqJVz7eV08%3D&amp;reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-announce/attachments/20200701/cfc56d4c/attachment-0001.htm>

From grizz at 20c.com  Wed Jul  1 08:45:25 2020
From: grizz at 20c.com (Matt Griswold)
Date: Wed, 1 Jul 2020 15:45:25 +0000
Subject: [PDB Announce] PeeringDB 2.21.0 release at 2020-07-01T0400Z
In-Reply-To: <GV0P278MB0130B949FB802F602C27C5DA956C0@GV0P278MB0130.CHEP278.PROD.OUTLOOK.COM>
References: <89EBD586-00FB-425B-9383-C4F962A55AE4@peeringdb.com>
 <20200701144405.11706968@segv>
 <GV0P278MB0130B949FB802F602C27C5DA956C0@GV0P278MB0130.CHEP278.PROD.OUTLOOK.COM>
Message-ID: <20200701154525.46716895@segv>

* <Jan.Boogman at swisscom.com> [200701 15:09 +0000]:
> Hi Matt
> 
> I have upgraded  to Django-peeringdb 2.1, but it doesn't play well:
- snip -
> 
> pdb at pdb2:~$ pip3 freeze | grep peeringdb
> django-peeringdb==2.1.0
> peeringdb==1.0.0
> pdb at pdb2:~$
> 
> 
> Anything I am missing?

Looks to be a MySQL specific issue, we've made issues #45 and #46 [0]
-- should have a fix for #45 out shortly.

Thanks for the report.


[0] https://github.com/peeringdb/django-peeringdb/issues/45
[1] https://github.com/peeringdb/django-peeringdb/issues/46

From smcmanus at peeringdb.com  Wed Jul 15 07:42:23 2020
From: smcmanus at peeringdb.com (Stephen McManus)
Date: Wed, 15 Jul 2020 10:42:23 -0400
Subject: [PDB Announce] PeeringDB 2.22.0 release at 2020-07-29 04:00 UTC
Message-ID: <8755FB38-6F4C-4F53-A2C2-790BC1A7C89E@peeringdb.com>

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





From filiz at peeringdb.com  Wed Jul 15 08:20:29 2020
From: filiz at peeringdb.com (Filiz Yilmaz)
Date: Wed, 15 Jul 2020 17:20:29 +0200
Subject: [PDB Announce] SAVE the date: Peering DB Data Ownership Policy
 Implementation Webinar
Message-ID: <C6310BA9-CF2F-40CF-995D-D4238E5834AB@peeringdb.com>

[Apologies for multiple posts]


Dear PeeringDB Community, 


You may remember Peering DB Data Ownership Policy was adopted in April 2020 and was handed over to Product Committee for implementation <https://lists.peeringdb.com/pipermail/pdb-announce/2020-May/000149.html>. 


As noted by Steve McManus, beta for 2.22.0 <https://docs.peeringdb.com/release_notes/#release-2220> is now out and this release is packed with issues relating to the Peering DB Data Ownership Policy implementation.
https://lists.peeringdb.com/pipermail/pdb-announce/2020-July/000155.html <https://lists.peeringdb.com/pipermail/pdb-announce/2020-July/000155.html>


In order to raise awareness about this important release and to explain the upcoming changes to the community in more detail we are organising a Webinar.
It will take place on 21 July 16:00 CEST. You can find the details below. 


During this Webinar we will cover how PeeringDB will soon begin to handle IX-F import data, creating, changing or deleting netixlan objects and other upcoming changes relating to the implementation of PeeringDB Data Ownership Policy. 


Please join us if you can but if you cannot, please note we also plan to record the Webinar and place it on the PeeringDB website for future reference. 


Kind regards
Filiz Yilmaz
PeeringDB 
Product Manager


——

PeeringDB DataOwnership Policy Implementation Webinar 
Tue, Jul 21, 2020 4:00 PM - 5:00 PM (CEST) 

Please join the meeting from your computer, tablet or smartphone. 
https://global.gotomeeting.com/join/211130373 <https://global.gotomeeting.com/join/211130373> 

You can also dial in using your phone. 
United States: +1 (646) 749-3117 <tel:+16467493117,,211130373#> 

Access Code: 211-130-373 

More phone numbers 
Australia: +61 2 8355 1038 <tel:+61283551038,,211130373#> 
Austria: +43 7 2081 5337 <tel:+43720815337,,211130373#> 
Belgium: +32 28 93 7002 <tel:+3228937002,,211130373#> 
Brazil: +55 11 4118-4898 <tel:+551141184898,,211130373#> 
Bulgaria: +359 2 906 0606 <tel:+35929060606,,211130373#> 
Canada: +1 (647) 497-9373 <tel:+16474979373,,211130373#> 
Chile: +56 2 3214 9681 <tel:+56232149681,,211130373#> 
Colombia: +57 1 600 9954 <tel:+5716009954,,211130373#> 
Czech Republic: +420 2 96 21 62 28 <tel:+420296216228,,211130373#> 
Denmark: +45 32 72 03 69 <tel:+4532720369,,211130373#> 
Finland: +358 923 17 0556 <tel:+358923170556,,211130373#> 
France: +33 170 950 590 <tel:+33170950590,,211130373#> 
Germany: +49 721 6059 6510 <tel:+4972160596510,,211130373#> 
Greece: +30 21 0 300 2693 <tel:+302103002693,,211130373#> 
Hungary: +36 1 933 3700 <tel:+3619333700,,211130373#> 
Ireland: +353 15 360 756 <tel:+35315360756,,211130373#> 
Israel: +972 3 376 3071 <tel:+97233763071,,211130373#> 
Italy: +39 0 230 57 81 80 <tel:+390230578180,,211130373#> 
Luxembourg: +352 34 2080 9220 <tel:+3523420809220,,211130373#> 
Malaysia: +60 3 7724 4060 <tel:+60377244060,,211130373#> 
Mexico: +52 55 4624 4518 <tel:+525546244518,,211130373#> 
Netherlands: +31 202 251 001 <tel:+31202251001,,211130373#> 
New Zealand: +64 9 282 9510 <tel:+6492829510,,211130373#> 
Norway: +47 21 93 37 37 <tel:+4721933737,,211130373#> 
Panama: +507 308 4337 <tel:+5073084337,,211130373#> 
Peru: +51 1 642 9425 <tel:+5116429425,,211130373#> 
Romania: +40 31 780 1159 <tel:+40317801159,,211130373#> 
South Africa: +27 11 259 4925 <tel:+27112594925,,211130373#> 
Spain: +34 932 75 1230 <tel:+34932751230,,211130373#> 
Sweden: +46 853 527 818 <tel:+46853527818,,211130373#> 
Switzerland: +41 225 4599 60 <tel:+41225459960,,211130373#> 
Turkey: +90 212 900 4812 <tel:+902129004812,,211130373#> 
United Kingdom: +44 330 221 0097 <tel:+443302210097,,211130373#> 

New to GoToMeeting? Get the app now and be ready when your first meeting starts: 
https://global.gotomeeting.com/install/211130373 <https://global.gotomeeting.com/install/211130373> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-announce/attachments/20200715/da19f983/attachment-0001.htm>

From filiz at peeringdb.com  Mon Jul 20 00:48:48 2020
From: filiz at peeringdb.com (Filiz Yilmaz)
Date: Mon, 20 Jul 2020 09:48:48 +0200
Subject: [PDB Announce] CANCELLED (was Re: SAVE the date: Peering DB Data
 Ownership Policy Implementation Webinar)
In-Reply-To: <B13EEF6D-B627-422C-9C85-EB1AE9356AC9@peeringdb.com>
References: <B13EEF6D-B627-422C-9C85-EB1AE9356AC9@peeringdb.com>
Message-ID: <0D82594C-2DE7-47ED-B55D-5ED388C8174D@peeringdb.com>


Dear PeeringDB Community, 

We have seen a number of issues reported since the beta announcement for v2.22.0 last week. 

Product Committee and Admin Committee Chairs have decided that previously announced webinar will be cancelled and rescheduled to a new date in about two weeks time, after majority of these issues are resolved. 

We will make an announcement once the new date for the webinar is set. 

Kind regards
Filiz Yilmaz



> On 15 Jul 2020, at 17:41, Filiz Yilmaz <filiz at peeringdb.com> wrote:
> 
> [Apologies for multiple posts]
> 
> 
> Dear PeeringDB Community, 
> 
> 
> You may remember Peering DB Data Ownership Policy was adopted in April 2020 and was handed over to Product Committee for implementation <https://lists.peeringdb.com/pipermail/pdb-announce/2020-May/000149.html>. 
> 
> 
> As noted by Steve McManus, beta for 2.22.0 <https://docs.peeringdb.com/release_notes/#release-2220> is now out and this release is packed with issues relating to the Peering DB Data Ownership Policy implementation.
> https://lists.peeringdb.com/pipermail/pdb-announce/2020-July/000155.html <https://lists.peeringdb.com/pipermail/pdb-announce/2020-July/000155.html>
> 
> 
> In order to raise awareness about this important release and to explain the upcoming changes to the community in more detail we are organising a Webinar.
> It will take place on 21 July 16:00 CEST. You can find the details below. 
> 
> 
> During this Webinar we will cover how PeeringDB will soon begin to handle IX-F import data, creating, changing or deleting netixlan objects and other upcoming changes relating to the implementation of PeeringDB Data Ownership Policy. 
> 
> 
> Please join us if you can but if you cannot, please note we also plan to record the Webinar and place it on the PeeringDB website for future reference. 
> 
> 
> Kind regards
> Filiz Yilmaz
> PeeringDB 
> Product Manager
> 
> 
> ——
> 
> PeeringDB DataOwnership Policy Implementation Webinar 
> Tue, Jul 21, 2020 4:00 PM - 5:00 PM (CEST) 
> 
> Please join the meeting from your computer, tablet or smartphone. 
> https://global.gotomeeting.com/join/211130373 <https://global.gotomeeting.com/join/211130373> 
> 
> You can also dial in using your phone. 
> United States: +1 (646) 749-3117 <tel:+16467493117,,211130373#> 
> 
> Access Code: 211-130-373 
> 
> More phone numbers 
> Australia: +61 2 8355 1038 <tel:+61283551038,,211130373#> 
> Austria: +43 7 2081 5337 <tel:+43720815337,,211130373#> 
> Belgium: +32 28 93 7002 <tel:+3228937002,,211130373#> 
> Brazil: +55 11 4118-4898 <tel:+551141184898,,211130373#> 
> Bulgaria: +359 2 906 0606 <tel:+35929060606,,211130373#> 
> Canada: +1 (647) 497-9373 <tel:+16474979373,,211130373#> 
> Chile: +56 2 3214 9681 <tel:+56232149681,,211130373#> 
> Colombia: +57 1 600 9954 <tel:+5716009954,,211130373#> 
> Czech Republic: +420 2 96 21 62 28 <tel:+420296216228,,211130373#> 
> Denmark: +45 32 72 03 69 <tel:+4532720369,,211130373#> 
> Finland: +358 923 17 0556 <tel:+358923170556,,211130373#> 
> France: +33 170 950 590 <tel:+33170950590,,211130373#> 
> Germany: +49 721 6059 6510 <tel:+4972160596510,,211130373#> 
> Greece: +30 21 0 300 2693 <tel:+302103002693,,211130373#> 
> Hungary: +36 1 933 3700 <tel:+3619333700,,211130373#> 
> Ireland: +353 15 360 756 <tel:+35315360756,,211130373#> 
> Israel: +972 3 376 3071 <tel:+97233763071,,211130373#> 
> Italy: +39 0 230 57 81 80 <tel:+390230578180,,211130373#> 
> Luxembourg: +352 34 2080 9220 <tel:+3523420809220,,211130373#> 
> Malaysia: +60 3 7724 4060 <tel:+60377244060,,211130373#> 
> Mexico: +52 55 4624 4518 <tel:+525546244518,,211130373#> 
> Netherlands: +31 202 251 001 <tel:+31202251001,,211130373#> 
> New Zealand: +64 9 282 9510 <tel:+6492829510,,211130373#> 
> Norway: +47 21 93 37 37 <tel:+4721933737,,211130373#> 
> Panama: +507 308 4337 <tel:+5073084337,,211130373#> 
> Peru: +51 1 642 9425 <tel:+5116429425,,211130373#> 
> Romania: +40 31 780 1159 <tel:+40317801159,,211130373#> 
> South Africa: +27 11 259 4925 <tel:+27112594925,,211130373#> 
> Spain: +34 932 75 1230 <tel:+34932751230,,211130373#> 
> Sweden: +46 853 527 818 <tel:+46853527818,,211130373#> 
> Switzerland: +41 225 4599 60 <tel:+41225459960,,211130373#> 
> Turkey: +90 212 900 4812 <tel:+902129004812,,211130373#> 
> United Kingdom: +44 330 221 0097 <tel:+443302210097,,211130373#> 
> 
> New to GoToMeeting? Get the app now and be ready when your first meeting starts: 
> https://global.gotomeeting.com/install/211130373 <https://global.gotomeeting.com/install/211130373>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-announce/attachments/20200720/a864dda0/attachment-0001.htm>

From smcmanus at peeringdb.com  Thu Jul 23 10:52:31 2020
From: smcmanus at peeringdb.com (Stephen McManus)
Date: Thu, 23 Jul 2020 13:52:31 -0400
Subject: [PDB Announce] PeeringDB 2.22.0 release - rescheduled to
 2020-08-12 04:00 UTC
In-Reply-To: <8755FB38-6F4C-4F53-A2C2-790BC1A7C89E@peeringdb.com>
References: <8755FB38-6F4C-4F53-A2C2-790BC1A7C89E@peeringdb.com>
Message-ID: <4DD86E96-5FCB-4927-B179-01A108A9014C@peeringdb.com>

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
> 
> 
> 
>