This is probably the worst time of year to try and coordinate a release, what
with people taking time off work and going away, but I'm going to try anyway
since we really need to get R3.14.10 out soon — it's well over 500 days since
we last produced a 3.14 release, which is the longest period between major
base releases ever.
Our ideal timescale for a final release date would be in early-middle August
[the sounds of screaming horror come through the ether...] which is at the
start of a 6.5 week APS shutdown. If we don't make this date, Eric is likely
to sulk. Personally I'll be on vacation the week of July 14-18th, and for a
few days at the beginning of August.
Working backwards from Release Approval on August 8th and assuming we find no
show-stopping bugs, that puts 3.14.10-RC1 on August 1st and 3.14.10-pre1 on
July 25th. I'd like some lee-way for finding and fixing issues though, so I'd
prefer to bring that forward another week which hits my vacation week. That
leaves just 2 weeks to finish up any remaining commits and bug fixes [more
screaming is heard, louder this time].
How does this hit the other core developers, do we have any chance of making
this timescale? I still have a number of uncommitted changes in my working
area (64-bit IOC, startup/shutdown + redundancy hooks) and submitted patches
for errlog and devLib that I haven't applied yet.
If you think this message applies to you, please discuss...
- Andrew