--------- Original Message --------- Subject: RE: official repository vs forks, and fixes From: "Salz, Rich" <[email protected]> Date: 8/26/14 4:13 pm To: "[email protected]" <[email protected]>
Think of this as pre-release software. The changes are too large to disrupt the 1.0.2 release, which is already in beta. We haven't yet figured out how to make early-access to branches available, so for now I just did it via Akamai. At some point, I'd expect that branch to “move” over to openssl's repo, but we're not there yet. Make sense? FWIW, most of us picking up 1.0.2 will be in it for the long haul, I wouldn't expect many to shift from 1.0.2 again to 1.0.3 over the course of a year or several. It might be worth rethinking the 1.0.2 release plan to pick up corrections, especially if they improve the trust in the code that ships, even if this means resetting the 1.0.2 scope or API? It also ensures that some platforms being kicked off the bus will stall at 1.0.1, rather than leaving that code around for years in a 1.0.2 release. If the decision's been made to drop them, then the sooner, the better. Just food for thought.
