Hi, On Wed, 2011-01-26 at 15:01 -0700, Sage Weil wrote: > 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 > FWIW, master/stable/next makes sense to me. > Does anyone see value in having a branch that has the last release? They > can see that with the git tags. Also FWIW, I think tags should be enough for releases. -- Jim > > 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 > -- 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
