On Thu, Jan 11, 2018 at 12:38 AM, Shyam Ranganathan <srangana@xxxxxxxxxx> wrote: > Hi, (GD2 team, packaging team, please read) > > Here are some things we need to settle so that we can ship/release GD2 > along with Gluster 4.0 release (considering this is a separate > repository as of now). > > 1) Generating release package (read as RPM for now) to go with Gluster > 4.0 release > > Proposal: > - GD2 makes github releases, as in [1] > > - GD2 Releases (tagging etc.) are made in tandem to Gluster releases > - So, when an beta1/RC0 is tagged for gluster release, this will > receive a coordinated release (if required) from the GD2 team > - GD2 team will receive *at-least* a 24h notice on a tentative > Gluster tagging date/time, to aid the GD2 team to prepare the required > release tarball in github Sounds good. > > - Post a gluster tag being created, and the subsequent release job is > run for gluster 4.0, the packaging team will be notified about which GD2 > tag to pick up for packaging, with this gluster release > - IOW, a response to the Jenkins generated packaging job, with the > GD2 version/tag/release to pick up > > - GD2 will be packaged as a sub-package of the glusterfs package, and > hence will have appropriate changes to the glusterfs spec file (or other > variants of packaging as needed), to generate one more package (RPM) to > post in the respective download location > > - The GD2 package version would be the same as the release version > that GD2 makes (it will not be the gluster package version, at least for > now) I prefer if GD2 follows gluster versioning. Keeps things simpler. Anyone packaging will have to just pick the same version of GD2. We already version our perview releases as v4.0dev. > > - For now, none of the gluster RPMs would be dependent on the GD2 RPM > in the downloads, so any user wanting to use GD2 would have to install > the package specifically and then proceed as needed Yes. The glusterfs-server package will not depend on GD2 right now. This will be changed later when GD2 becomes the default. > > - (thought/concern) Jenkins smoke job (or other jobs) that builds RPMs > will not build GD2 (as the source is not available) and will continue as > is (which means there is enough spec file magic here that we can specify > during release packaging to additionally build GD2) The glusterfs spec file can be updated to include building GD2 from its release tarball. I don't remember exactly but, rpmbuild might have ways to automatically download sources/dependencies. We can check if this is true. > > 2) Generate a quick start or user guide, to aid using GD2 with 4.0 > > @Kaushal if this is generated earlier (say with beta builds of 4.0 > itself) we could get help from the community to test drive the same and > provide feedback to improve the guide for users by the release (as > discussed in the maintainers meeting). We will do this. > > Thanks, > Shyam > > [1] github GD2 releases: https://github.com/gluster/glusterd2/releases > _______________________________________________ > packaging mailing list > packaging@xxxxxxxxxxx > http://lists.gluster.org/mailman/listinfo/packaging _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
