On Wed, Aug 17, 2011 at 9:19 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> I would like to see us maintain a projected release date for 1.7 once we
> have moved to the RC phase. Most likely place to put it would be here:
> I think including this date in the RC announcement would make the
> announcement stronger and encourage testing, although I am fine with just
> maintaining it on our dev@ list and website.
> We have a good idea when the release date will be, based on our defined
> policies. I think publicizing when we anticipate rolling the final release
> tarball and likely release the signed version will simply eliminate
> confusion by letting everyone know in advance when these events are going to
> happen. This also makes it easier for our downstream ecosystem, such as
> TortoiseSVN, Subclipse, AnkhSVN etc. to know when to expect the release so
> that they can better plan their own releases.
> If we need to create a new RC and restart the soak period, then we can just
> update the date to reflect this but at least we can all be on the same page
> about it and give our downstream a proper heads-up on the change and what
> that means for the new date.
> Based on my math, if we roll RC1 this week and release on Monday, then add 4
> weeks for the soak and we have Sept. 19. Assuming we roll final tarball on
> Weds (Sept 21) we would then expect to release on Monday Sept 26.
IIRC, we can roll the final before the end of the soak, so as to
release when the 4-week soak is up.
but +1 on the general idea of being more communicative to our users
and publicizing our anticipated release dates.
uberSVN: Apache Subversion Made Easy
Received on 2011-08-17 16:43:19 CEST