On Wed, Jan 5, 2022 at 1:39 PM Daniel Sahlberg <daniel.l.sahlb...@gmail.com> wrote: > > Hi, > > We need to start thinking about if/how/when we can do a new release. Nathan > and I started talking about this last August but for work issues neither of > us had the time then. > > There is one issue resolved by Stefan Sperling (r1894734) which would be good > to have released. It is nominated for backport to 1.14.x and 1.10.x but no > review yet. > > If we release now we should release at least 1.10.8 (we are three months > short of the "end of support date" and I think we should release one last > version with the current fixes) and 1.14.2. > > In trunk there are also a bunch of improvements that themselves could > probably justify releasing 1.15. Then there are also a number of patches > flying around on the dev@, as well as one or two feature branches (the > non-pristine-wc being a prime example) that would be interesting to merge > before 1.15. > > 1: Can anyone volunteer to be RM? > 2: Can we drum up some support for approving the candidate changes - at least > for 1.14.2 but, depending on the time line also for 1.10.8. > 3: What about 1.15? And that probably bring up the larger question about > future release policy in general - we are NOT following the twice-per-year > policy at the moment. > > Kind regards, > Daniel Sahlberg >
Thanks for bringing this up. For the moment, let's wait on the question of who can RM. I know that without paid staff, this is a mental block to discussing releases, so let's ignore it. Let's decide *what* we want first. (A clear plan may make it possible to raise funds, etc.) I have been pondering the question of which release(s) and in what order. I think 1.14.2 and 1.10.8 first, then 1.15.x later. Rationale: various, some of which are: * unwieldy to release all three simultaneously * better for the community to have 1.10.8 rather than not have it * being patch releases, lower barrier to release as compared to 1.15 Because of this difference, I think it is better for the community not to mix, say, 1.14.2 and 1.15.0, in one simultaneous effort. Also, I think 1.15 is a more interesting release if it includes items you mentioned and is released separately so its announcement is not diluted by the other releases. Of course, if there are good reasons to do things differently, I'm certainly open to that. For example, previously discussed TortoiseSVN features that were waiting for a Subversion release; for that purpose, is there a difference between 1.14.2 and 1.15.0? Is one "better" than the other? That could be a factor to consider. Regarding drumming up support for the backports: I will make an effort to review items and look for other good candidates that aren't nominated yet. Cheers, Nathan
