On Wed, Aug 31, 2011 at 9:33 AM, Mark Phippard <markp...@gmail.com> wrote: > On Wed, Aug 31, 2011 at 10:17 AM, Hyrum K Wright <hyrum.wri...@wandisco.com> > wrote: >> >> There will be a little bit of delay by the mirroring system, but Mike >> and I were discussing the possibility of releasing before the mirrors >> have caught up and just warning our users of this fact in the release >> announcement. That would compress things a bit, but I'm generally >> indifferent. > > To be clear, I am not trying to compress the release or push up the release > date. What I am really interested in is having a projected exact date for > the release. It might even be nice to have a time planned. Something like > the release will be announced and available on Sept 28th at Noon Pacfic. If > on the 26th something has come up that is going to delay it a day or so, > that is fine. Just let us know and we can adjust, but I want to be able to > plan ahead of time around a specific date when the release is out without > needing to know what is going on with your travel plans or whatever else > might be going on.
Oh, I didn't interpret your comments as an attempt to rush or speed up the release cycle. It was more my own thoughts about ways we can improve. As for a specific date, I'm hesitant to commit to something. While I certainly appreciate the utility, my crystal ball just isn't that clear. I guess it boils down to the fact that I've been telling people my guess about 1.7's release date for *years*, and I'd rather under promise and over deliver on this one than vice versa. Maybe I'm getting commitment fatigue. :) You mention being flexible with the date if something comes up. In which case, why even set a date at all? It feels a lot like releasing a release candidate that isn't really a candidate for release. ;) -Hyrum -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/
