On 2014-08-21 06:20-0400 Hazen Babcock wrote: >> >> @Everybody: >> Instead of writing a rebase workflow document myself that we could >> use, I have been looking for something like that written by someone >> else. What do you think of adopting (the quite restrictive) rebase >> workflow outlined in >> <http://kevinold.com/2013/04/17/my-git-workflow.html> to start? No >> integration branches other than master. No published topic branches. >> But dead simple and very much like our previous svn-based workflow. > > Looks good to me. I think we should at least make a copy in the project, > which I volunteer to do once we can commit again. I'll update > README.developers unless someone thinks this is better somewhere else.
Yes, please! I think this deserves its own file. So I assume you will call that file README.git_workflow, and I will output that name to the user in the update hook logic I hope to test (in a mini-project) and then install in our SF repo later today. Once I get that installed, I will make the git repo pushable by all our developers, and we will be live! > Also, we need to update our web-page to point to the git repository and > not the svn repository. That should be on our ToDo list, but first all the scripts that update the website have to be changed from svn logic to equivalent git logic. I will likely let all this slide for a while (maybe even until we make our first post-git release several months from now) until I get a lot more used to using git. The alternative was asking you to do that website update, but when I took over the website update duty from you as release manager, there was a nasty permissions issue that took a lot of commands done by hand (deleting directory and contents at SF working up from the deepest subdirectories using sftp commands) to straighten out. So if we switch to you now (just for the website update) you would have to deal with that permissions issue again by hand. (I am pretty sure there is a way to overcome these permission issues in an automatic way (perhaps by playing with the group permissions), but I haven't figured that out.) 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 __________________________ ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
