Ok, here's a roadmap. Let me know if you need some more detail or anything.


Feb:
* [rhel6.8] Test phase:
    * Test phase always brings a bunch of bugs, so I expect a decent
    amount of time will be allocated to fielding or fixing some of
    those. (I know, not s390x-specific, but it'll eat some time.)

* [master/f24] zFCP out of blivet/into libblockdev:
    * Most of this work has been done for a while, it's just testing
    that's a pain. Not sure I'll ever be able to test every code path,
    so maybe I should just give up on that and post the patches. If you
    have any opinion, feel free to share. They've literally been stashed
    away for about a month now, so I feel a little dumb about that.

* [rhel7-branch] 7.3 assigned bugs:
    * Not all are s390x-related, but I'm going to try to knock out some
    of the easier 7.3 bugs I have first. Some of the s390x-specific
    fixes though:
        - kernel cmd line limit bug (1260934)
        - dir install on s390x (1269207)
        - ECKD display dialog on successful add (1259016)
    (These'll all make their way upstream as well.)

Mar:
* [master/f24/rhel7.3] LDL+CDL DASD formatting:
    * Broken from 7.2; have ~80% of work done for master/f24 branch, but
    lots of problems testing (not with my code for once, just s390x
    problems, e.g. network issues fetching ks files on devel and rtt
    LPARs even though updates.img's download just fine -- stuff like
    this. I've reverted to just testing off of 7.2.)

        - A lot of 7.3 bugs that are assigned to me are related to this:
        1233438, 1269174, 1269955, 1266151, 1259437, 1170653, 1269863
        I expect these will all be fixed in 7.3.

    * Depends on: https://bugzilla.redhat.com/show_bug.cgi?id=1244833
    It is crucial this bug is fixed -- I've already spent a lot of time
    on it in and out of the office, and we really need IBM to help. I
    pinged Georg about this (again) in last week's s390x call. It makes
    testing manual installations with LDL and/or CDL DASDs almost
    impossible.
    1244833 is a race condition and so won't present sometimes, but it
    almost always does. I can't reliably _not_ reproduce it either, to
    ease the burden of testing that way. This exists in Fedora and RHEL.

    * Due to how much testing is required to verify even base
    functionality (LDL, CDL, LDL+CDL in manual gui+tui and ks gui+tui),
    and how long it takes, I expect this'll take me a lot of time,
    probably 02 - 03 weeks. Especially since I'll have to rebase patches
    from rhel7-branch on to master again. Those will, unfortunately,
    only be able to get minimal testing.

Apr:
* [master] A low priority item that's always on my list: some s390x
  tests. It might (should?) be possible to simulate DASDs, which should
  enable us to do some at least basic form of ks tests, and we (I) could
  also expand upon the s390x tests that currently exist in libblockdev.


Beyond (AKA items we can't do right now, and why):
* FBA DASD && EDEV stuff:
    https://bugzilla.redhat.com/show_bug.cgi?id=1214407
    https://bugzilla.redhat.com/show_bug.cgi?id=1271742
    - Target? 7.4
    - Reasoning: I've got a lot for 7.3 already, and if I have to fix
    these now, it probably won't be done well/accurately. I think [hope]
    this is ok to defer since FBA DASDs and EDEV are not all *that*
    common. In fact I see more cases of people using LDL DASDs than
    either of these.

* HyperPAV stuff:
    https://bugzilla.redhat.com/show_bug.cgi?id=1031589
    - Target? No idea
    - Reasoning: I need access to these devices so I can actually debug
    and test, since I have no idea why my fix for 7.2 didn't work, and
    it was my only idea (though quite sound -- 4b136269 in blivet).
    jstodola filed an issue with Arlinton to get access to these devs,
    and we both ping him from time to time, but no dice so far.