-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 04/28/2015 11:26 AM, Jeff Ortel wrote: > 1. Would this be acceptable in a Y release or does this need to > wait for the next major release?
The last_published being updated during failure could be arguably be considered a defect, so fixing the defect it OK in a Y (or even Z) release. As for the data type changing, I think so long as the API continues to present and accept it in the same format as it did before, this is also fine. I say go for it! > 2. Would it break anything? Not sure, but in theory nothing should be depending on this broken behavior anyway since it should not be documented that way. Either way, it's important to call attention to this change in release notes. - -- Randy Barlow -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJVP8MqAAoJEIyFaKUJtmpiF5EP/2e4iNEiAjytcAd9+JhZQTri c+pwhLPIXuid3qwpZWeMZ7AMGHgxK1hdJodLDNwBS9dNx2WOVKn5NEXq3a8+2/+q OxED6eTeILcQPuGc0AcbvOfmSe0CeCiRjvlsmc+CMcYFNVTKQ2ViucY5Ouq+MlYL jnlPl4j6dYAej5QufvAR1xkSZ2ZVipc3VUTvqnvaa+9U49XCXFf+qMfcpQHc7pFT PLsp99qtgyPWUMmZehkM0rNZPbxnA83buiXgBEYYAPtODx9QUv9VO+vei45Q/evh AjJB8sllUpM/VtXRglyFEDVhv9MnERu7fvplYjzrIv1xQXDfAEE29RbkgQak8wxe RsBRBR0fUC+wmzkUknhLcVvkwYUBLjgSg/gA0hHX6pua1TWlNUcPj3GujeKvFV9Q aj6xQkDciDI0JsNUu0IA9F3pjsTs2IhjlcEQSU68Nd/8GP4/fm6mAQUyKRizaMRW t6R+aw33DTMOPGtfPrdIel4caqrIn5xx3Yf4dxL+YFZsNcDTrcrMnjd346HsA9gm JQnQ4eh9yJKUdudydqG2gYWnoYyeyzTh246cPObIGT2CGv+DCzemUP4hUaLUNCUc iYwS6ihDLWyeZCx+DFlNP9ripA+E9B2z+b6pEF7ltRwjX8RG9V5QM8lFpDqHmiNH s/DGXUgQezF/+nkdJwiR =iwTw -----END PGP SIGNATURE----- _______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list