dynpmc and dynop: Seek clarification re order of deprecation

[James E Keenan]

In DEPRECATED.pod, I see this entry:

    moved to dynpmc [eligible in 1.1]
        AddrRegistry, CodeString, Env, Eval, File, OS, PCCMETHOD_Test,
        StringHandle, and Timer.

       <https://trac.parrot.org/parrot/ticket/448>

... as well as this entry:

    moved to dynop [eligible in 1.1]
        Parts or all of: bit.ops, debug.ops, io.ops, math.ops, obscure.ops,
        set.ops (the obscure and rarely used parts), sys.ops.

        <https://trac.parrot.org/parrot/ticket/449>

... but then I also see this:

    tools/build/dynoplibs.pl and tools/build/dynpmc.pl [eligible in 1.1]
        Replaced with makefiles.

        <https://trac.parrot.org/parrot/ticket/338>

Do TT 448 and TT 449 have to be done before TT 338 can be begun?  Or is 
there no relationship between the first two and the third?

Clarification sought.  Thank you very much.

kid51