Yeah. Currently: master - last release (but I forgot to update it) unstable - unstable testing - bug fixes to last release, will become next stable release rc - will become next major release
I agree that's not optimal. I think moving unstable to work to master makes sense. How about something like: master - unstable (and get rid of 'unstable' branch) testing or stable - bug fixes to last release. rc or next - what will be the next major release Does anyone see value in having a branch that has the last release? They can see that with the git tags. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
