Hi everyone, Yesterday during the doc sprint, the question of what to do about branches post-3.0 came up. Currently there are three branches, which correspond to different names on the front page of the yt homepage. * Stable => The branch into which bug fixes are merged, but not a lot of active development occurs. * yt => The 2.x development branch, which has slowed almost to a halt * yt-3.0 => The 3.0 development branch It seems there is broad consensus that after the release, the yt-3.0 branch would be merged into the yt branch. (I would like to hold off on "closing" the yt-3.0 branch for a while, however.) But, what is then to be done about the "stable" branch? My thought was: * stable => will be on 2.x for at least one release, until 3.1 * yt => 3.0 * yt-3.0 => we try to migrate development onto the yt branch, which is 3.0, but don't force yet The alternate idea was: * stable => 3.0 * yt => 3.0 * yt-3.0 => closed I think we need a longer migration time for 2.x, though. I will update YTEP-0008 with whatever we come up with, but is there a strong opinion for either of these options? Option 1: stable stays 2.x for now, Option 2, stable becomes 3.0. -Matt