The mimic branch is now forked off of master, and the first release candidate (13.1.0) is getting built. It's now possible to merge new stuff for nautilus into the master branch! As for how we manage the mimic branch going forward, we have two options: 1) Merge bug fixes to master and cherry-pick -x them to mimic. This is a bit of extra work, but it's what we're used to doing for the stable releases after they're out. 2) Merge bug fixes to mimic and periodically merge mimic back into master. At some point we'll switch back to option 1 (e.g., when we declare vistory and release 13.2.0). This is a bit less work now, but means we'll switch "modes" for how we're managing branches again in a few weeks and confuse people. I retargetted all the mimic branches at the mimic branch (i.e., option 2) but I'm sort of thinking option 1 is less confusing. Any strong opinions? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
