Re: branching 1.14.x

> On Mar 14, 2020, at 7:47 AM, Stefan Sperling <stsp_at_elego.de> wrote:
>
> On Tue, Mar 10, 2020 at 12:23:49PM +0100, Stefan Sperling wrote:
>> As previously discussed, I would like to create the 1.14.x branch
>> soon in order to begin the release process for 1.14.0.
>>
>> There are two changes being worked on which look important and
>> which, I believe, could only be introduced in a dot zero release
>> since they violate our patch release compatibility guarantees:
>>
>> 1. The 'decouple-shelving-cli' branch
>>
>> 2. The editor path fixes which don't yet work on Windows.
>>
>> Did I miss anything?
>>
>> I'm wondering if we should wait with creating the 1.14.x branch
>> until the above changes have settled.
>>
>> Alternatively, we could create the branch now and allow these
>> changes to be merged before 1.14.0; beyond that point these
>> changes could miss the boat and might have to wait until 1.15.
>
> Since nobody has responded: Should I just make a decision by myself? :)

Speaking for myself, it is hard to know whether to respond when you are not really helping and contributing.

The Python3 stuff seems like a big deal to me, and I assume we already missed the next Ubuntu LTS release window because of it. I have to assume SVN in all of the major distros is a real mess today because of this issue.

I'd like to see us get the 1.14 release out there. I thought we left it that this would be the last release unless contributions start to appear that warrant a 1.15 etc.

What should we do? If no one has chimed in they are doing the work then maybe we should branch. We can always merge or rebranch before we release. If it spurs action it would be worth it.

Personally, I do not care at all about experimental features and shelving. I would favor ripping it all out and let it come back in a future release if someone wants to finish and turn it into a feature that we are willing to support forever. Right now, I cannot foresee a scenario where this feature ever becomes finished. I do not see why we are even doing the work to include it. I realize ripping it out would be work that someone has to do too though.

I do not fully understand the editor path bug. But if you are saying it cannot be fixed in an existing release because of API changes, then that sounds like the priority. Unless Bert has time, I am not sure where we get Windows help now though.

Anyway, I have a small window here where I have been able to maybe get our SVN support updated from 1.8 to a newer version. 1.14 is the only one I am interested in, so I am hoping the release process starts soon.

Mark
Received on 2020-03-14 13:03:36 CET