Can some git guru here advise me what I need to do to publish a bug fix release (in case during this release cycle some bug fix is so urgent that we need to make a bug-fix 5.13.1 release to propagate that fix to our users)?
I assume I would branch a private topic branch called "release" for this bug-fix release at the plplot-5.13.0 tag (to minimize post-5.13.0 work that goes into this "release" branch), and I would need to create a small number of bug-fix commits on that topic branch (either by hand or with git cherry pick) to complete all development for that private release topic branch. But what is the best way to publish that work? Here is a scenario I think might work. Tag that last commit on that private "release" branch as (signed) "plplot-5.13.1" Propagate that tag to SF using git push origin plplot-5.13.1 Is that sufficient? i.e., will that propagate that tag (and presumably its small number of parents back to plplot-5.13.0) to SF? No new branches at SF would be ideal since development on that "release" branch should not proceed past plplot-5.13.1 Or do I need to push the "release" branch to a new "release" branch at SF, e.g., with git push -u origin release before pushing the tag, and then follow up with deleting the branch (which should not delete the tag and its parents) which would allow me to reuse the "release" branch name if I have to do this again and also discourage anyone from attempting to use the "release" branch at SF for further development. Or if neither of these ideas end up with the plplot-5.13.1 tag and all its parents being permanently stored and accessible at SF without a corresponding branch, can someone advise me of a better procedure for publishing my plplot-5.13.1 tag (and presumably its immediate parents)? Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
