and release the (pull requests with code destined for) kraken! One question: we moved from a 'next' branch to 'jewel' branch for the development period to represent the 'frozen' bugfix branch before each development checkpoint release. Should we 1) Use a 'kraken' branch, just like we did with jewel. After each dev release, merge in the next lump of new stuff from master. 2) Go back to a 'next' branch, like we did pre-jewel. 3) Give up on the delayed dev checkpoint release thing we've been doing (where we send bug fixes to next or kraken for 2 weeks before release) and just release regular checkpoints of master (as 11.0.z). 4) Stop doing development checkpoint releases entirely and let testers pull automated builds from gitbuilder or jenkins. Thoughts? 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
