Currently there are plans to update release deliverables more formally post Fedora 24 GA. These aren't all going to happen immediately following the release but work will be done to enable them ASAP.
Some of these we've already decided on in the past but a couple still need decisions. The goal here is to simply determine what we would like to see as an ideal release cadence of updated deliverables. Technical implementation and details will be outside this scope.
More information around the request for a 2-week atomic repo cadence as discussed during the meeting 2016-05-04 https://fedorahosted.org/rel-eng/ticket/6313
We discussed this in a fedora cloud mtg on Jul 20 (https://meetbot.fedoraproject.org/fedora-meeting-1/2016-07-20/fedora_cloud_wg.2016-07-20-17.00.log.html).
Currently, bodhi updates the testing and stable ostree repos when there are new testing or stable pkgs. There's a desire, expressed in the issue that Adam referenced above (https://fedorahosted.org/rel-eng/ticket/6313) for an ostree commit that coincides with the two week releases.
The requested changes, as summarized by Colin Walters, who filed the bug:
Colin's executive summary: Create a new additional ref:
Allow users to rebase to this who want it.
More detail, from another comment (https://fedorahosted.org/rel-eng/ticket/6313#comment:12) some months later:
== Next Actions: ==
"I have a [https://firstname.lastname@example.org/thread/B73P6EDFVKZCMHJ75LBOWUMOJTI34N7N/ proposal out to the rel-eng mailing list] that we're currently hashing out now."
to comment on this ticket.