On 2015-07-22 22:24-0700 Alan W. Irwin wrote: > @Phil: how is it going with your bug fix? The sooner the better, > please, so we know what sort of fix is required, and whether we should > put it in the release or wait until post release. In light of your > progress do the plans below make sense? > > On 2015-07-21 10:22-0700 Alan W. Irwin wrote: > >> IMPORTANT. I am declaring now that a complete freeze on any pushes to >> our SF repository will be in effect once SF staff restores our >> repository from their backups and makes it available to us. The reason >> for this freeze is I need some time to check that restored repository >> against my local repository using similar extensive checking >> procedures that I originally used when converting from svn to git. > > According to <http://sourceforge.net/blog/> git service is back up so > I plan to start the detailed checking process early tomorrow > (Thursday) consisting of comparison of the working directory of my old > repository at various key release tags with a freshly cloned > repository. I also plan to do a detailed comparison of log results > between the two repositories to make sure those are identical. > > Once that checking process is completed I will let you all know here > and at that point set the release date for about a week later. So if > I can get that detailed checking process done in a timely manner (i.e. > by this weekend) with no issues showing up, then I will plan to > release 5.11.1 on August 1st (i.e., 10 days from now). > > And from the date when the repository check is completed to the > release date ~1 week later, we will move from the above hard freeze to > a slightly slushy freeze more typical of the last week before a > release. That slightly slushy freeze will still allow substantial > epa_build and documentation updates, and also no-brainer bug fixes to > our code with no side effects. However, more complicated bug fixes to > our code should be discussed/negotiated here before pushing, and, of > course, merging of major code updates to master are not allowed (since > those are not allowed in any case after the first month of a release > cycle).
I have just thoroughly checked (see details in commit id 9b86385) the git repository that was restored by SF staff after their "great outage" against my own local repository. All is well, which should let us all breathe a huge sigh of relief! As a result of this git repository testing success, the hard freeze has now been changed to the slightly slushy freeze described above, and I have pushed the 5 commits I had accumulated since this SF outage started (all of which qualify under the above slighly slushy freeze rules). Phil has not yet responded to the important question above so I assume his bug-fix progress has been slow, and therefore, unless I hear further objections from him or anyone else here who would really like to get their completed bug fix into this release, I plan to go ahead with the release of PLplot-5.11.1 on Saturday, August 1st. 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-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
