On 2016-11-20 10:10-0000 Tom Schoonjans wrote: > Hi Alan,
> Github supports exactly the workflow you want as shown in the attached screen shot. All that needs to be done is uncheck all except “Allow rebase merging”. Hi Tom: Thanks for letting us know about this ability of github to enforce our rebase-only workflow. @Hazen: Could you please check out the above possibility at github and test it by attempting some merge commits? If that test confirms as expected such commits are rejected at github with the above setup, then that means any PLplot developer can use the PLplot github server in confidence that those results can be pushed to our definitive server at SF without any issues so long as the precautions mentioned in README.developers are followed. Note the "definitive" designation means the server used by our release manager (currently me), and the git server we advertise on our website. By the way, I can honestly say you did a great job as release manager years ago (better than I am doing now in terms of how many releases per year you got out the door), and if you wanted to take on that role again (after I get 5.12.0 is out the door) that would give me more time to do PLplot development and testing which would make me quite happy. :-) And assuming you can prove to your own satisfaction that our rebase-only workflow is enforced properly at github, then as release manager you could designate the github server as the definitive one which would make SF git server users like me responsible for pushing our results to github (which again should be easy to do if the same workflow is enforced by both servers). By the way. My understanding is github does not support file releases, but that still means you can synchronize your local git server with the github one, create the release tarball from that local server version (as I do now where my local server is synchronized with the SF one), and then follow up by using sftp to copy that tarball release to SF (as I do now). In other words, file releases are completely independent of what git server is the designated as the definitive one, but it makes sense for the definitive server to be the one that the current release manager prefers for his convenience so long as users are well-informed (e.g., on our website and on this mailing list) which git server is definitive. 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 __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general
