Hi folks, Daniel Gryniewicz wrote on Mon, Apr 24, 2017 at 09:48:33AM -0400: > After a discussion with Matt, here's my thoughts. > > 1. We want -dev versions of Ganesha to track Master versions of Ceph. > This makes development much easier for us, and shouldn't cause problems, > since -dev versions aren't packaged. This also makes upstream Ceph > happier, with is CI integration.
A quick note on that, is that when the ceph requirement is bumped up the CEA bot will likely fail builds as well until someone here updates it -- but I guess as it currently says it's OK we might already have given up on that... > 2. Matt doesn't want to maintain a compatibility layer. I can > understand this. > > 3. Once Ganesha enters -rc, we suddenly care about what is shipping in > distros, since test packages have to be made. > > Our proposal is this: > > Branch when Ganesha goes into -rc, rather than on .0 release. This > allows us to modify the -rc version of Ganesha to build and work against > the then-extant versions of Ceph in the distros, and not have to worry > about syncing dev cycles between Ceph and Ganesha. Forking at -rc makes sense for me, as we can then only land fixes there and continue with regular development on next. The only black spot there is that it will give Frank more work (as there will have to be two merges for a few weeks), so I guess ultimately it's down to him. -- Dominique ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
