1.11 release preparation [was: Feature freeze for 1.11]

[Julian Foad <ju...@apache.org>]

Julian Foad wrote:
> James McCoy wrote:
> > I could still use some help getting the Java 10 support finalized [...]
> 
> For my planning of the 1.11 branch, could you please tell/remind me [...]

That was answered on IRC: it does not block the 1.11 branching or release.

I will plan to release 1.11 on 2018-10-17 which is a Wednesday 5 weeks from today. I have to enter a planned release date in the CHANGES file, so I needed to pick something. Is that reasonable?

-- 
- Julian

Re: 1.11 release preparation

[Julian Foad <ju...@apache.org>]

The 1.11 release notes:

  http://subversion.apache.org/docs/release-notes/1.11.html

now contain everything I think they need to, including very brief descriptions of the most notable items from CHANGES. *Very* brief, I'm telling you, in some cases. Can anybody review it and/or expand any sections?

-- 
- Julian

Re: 1.11 release preparation [was: Feature freeze for 1.11]

[Julian Foad <ju...@apache.org>]

Daniel Shahaf wrote:
> Julian Foad wrote on Wed, 12 Sep 2018 20:39 +0100:
> > I will plan to release 1.11 on 2018-10-17 which is a Wednesday 5 weeks 
> > from today. I have to enter a planned release date in the CHANGES file, 
> 
> I'm not sure you do, not yet. [...]

Technically you're right about the CHANGES file, but I'm really asking about planning the date. The CHANGES file was just the trigger that caused me to think right now about planning a specific date.

> > so I needed to pick something. Is that reasonable?

We decided to go for timed releases and we need to plan this release. I hope we (all of us) are willing to set a date now and attempt to release on that date, on condition that I get the RM tasks done in time.

"Why do we need to set a specific date?", we might ask. We know we can't *guarantee* to release on the chosen date because we won't release anything that hasn't passed certain checks and procedures. But I need to decide when to roll the release candidate, and so on. And one of the reasons why we chose to follow a scheduled release plan is so that consumers of the release can make their own plans around our releases. For that reason I think we should make the planned date public.

I propose 2018-10-17 for the release. That's about 6 months after the 1.10 release date 2018-04-13. Working backward 4 weeks, that means an RC must be rolled by 2018-09-19 (next Wednesday) at the latest.

Any other thoughts about this? 

- Julian

Re: 1.11 release preparation [was: Feature freeze for 1.11]

[Daniel Shahaf <d....@daniel.shahaf.name>]

Julian Foad wrote on Wed, 12 Sep 2018 20:39 +0100:
> I will plan to release 1.11 on 2018-10-17 which is a Wednesday 5 weeks 
> from today. I have to enter a planned release date in the CHANGES file, 

I'm not sure you do, not yet.  The tarball you'll soon be rolling will
be called 1.11.0-rc1, not 1.11.0. The latter will have to be rolled
separately to reset SVN_VER_TAG, so that will be an opportunity to fix
the first line of CHANGES.

> so I needed to pick something. Is that reasonable?

Cheers,

Daniel