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 t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
+1
On 10/07/2015 02: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
>
> 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.
Somewhat related - and looking for advice.
I am still on 2.3.1, but had planned to either upgrade or build a new Pulp
server in the
