-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/15/2015 04:03 PM, Salvatore Orlando wrote:
Do you reckon that the process that led to creating a migration
like [1] should also be documented in devref?
https://review.openstack.org/202534
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Do you reckon that the process that led to creating a migration like [1]
should also be documented in devref?
That might be helplful for developers, unless that process is already
documented elsewhere.
Salvatore
[1] https://review.openstack.org/#/c/202013/1
On 15 July 2015 at 15:54, Mike Bayer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/15/2015 04:03 PM, Salvatore Orlando wrote:
Do you reckon that the process that led to creating a migration
like [1] should also be documented in devref? That might be
helplful for developers, unless that process is already documented
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
since it's a high impact change in the migration tree, I wanted to
drop an email to everyone affected (basically, anyone who wants to
introduce a new migration from now on).
So there was a proposal to split migration rules into independent
On 7/15/15 9:26 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
since it's a high impact change in the migration tree, I wanted to
drop an email to everyone affected (basically, anyone who wants to
introduce a new migration from now on).
So there was a
