-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 +1 to this idea. +1 to drawing the upgrade line at 2.5.X.
Is there some way we can halt the user's upgrade using the spec file so that they know they need to upgrade to 2.5.0 first? Maybe in one of the pre stages? Would we do this for all the plugin spec files also since it will be the same problems there? I wrote up a first-pass of a Redmine story to track this work [0], and aligned it to 2.8.0. Feel free to edit or comment. [0]: https://pulp.plan.io/issues/1305 - -Brian On 10/07/2015 03:06 PM, Michael Hrivnak wrote: > I propose that we do not facilitate upgrading directly to pulp 2.8 > from any release earlier than 2.4. I could easily be talked into > drawing the line at 2.5. > > With the tremendous amount of refactor work going on in 2.8, > maintaining those old migrations is more challenging than ever. > Many used code that is now being heavily modified or deprecated. We > will save a lot of time and headache by removing migrations from > 2.8 that were introduced prior to 2.4. > > The small number of users who may still be on 2.3 or earlier can > upgrade to 2.4 - 2.7 first, and then upgrade to 2.8+. > > Feedback? Concerns? > > Michael > > > _______________________________________________ Pulp-list mailing > list [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWFndDAAoJEK48cdELyEfyhgsH/3RHowvAjeMgfclQPiN9o8JA 7JuygFD74KDrc+We4/e/NF67qWSyh/GDBDbYVNWN/hyQOKQ3LLnTjczczbadAXsH jIJeUBl6xI3EAsfdWjeSzLd1SNRAu7pNm/vxnAhoHIAC8A7Rv0yqL3iRj0wEyQvo ZCxdgFTNQEHzCkn56deXiVM1IPXGkw1ioHyve6/lhNfe+7ItsFa6Ubog/Il80+iz jeIDSK4ob++C3SpjCeR1Oxwh2MfcAqAa1bhGIX30cVYoMBTVs0+gGP++HzCm2G7C 1yEHbHVFd1MEEGboN3r8fvYN8jwfbzmavvWmpMey7PNBVCQavlKG7M6ju4VCn5c= =+j/o -----END PGP SIGNATURE----- _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
