Okay, that should not be a problem (provided that debs and rpms are enough). But would be good to get early access to pgdg beta1 packages then so that we can build pglogical against them in time. I admit I have not much idea of how the release packaging is coordinated.
I've prepped pglogical rpms for 9.6 and uploaded to the main pglogical repo Petr linked to earlier. I had to base them on temporary home-brewed Pg 9.6 rpms pending release of the official ones.
It looks like beta1 Debian/Ubuntu packages for Pg are still a WIP and we can't really build pglogical packages before they're ready.
RPM detail: There are no rpm tree changes in git yet, but I've prepped my own beta1 RPMs to build pglogical against. I've had to guess about the version scheme, so it's not ideal. Past beta RPM releases have used a scheme where the Version is "9.5" and the Release is "beta1_1PGDG" but I don't know if that'll be maintained since it's not really correct according to packaging guidelines (and I mailed Devrim about it).
Once PGDG 9.6beta1 rpms are live on yum.postgresql.org (or some private repo I can access) it takes about 20 mins to build pglogical rpms. I'll want rebuild them once the official packages go up no matter what, just to make 100% sure I'm building against exactly the same packages that'll be deployed, but it's not that important unless the version doesn't match.
Anyway, once the required Pg packages are on PGDG repos it's very quick to rebuild the debs and rpms for pglogical. If I'm not awake (+0800 Western Australia time) Petr will be so one of us can kick off a build and we'll have packages something like half an hour later.