Please hold commits to devel until the 6.2 branch exists

12 views

Skip to first unread message

Edward K. Ream

unread,

Mar 11, 2020, 6:43:30 AM3/11/20

to leo-editor

Matt, this does not apply to you.

This is a side effect of the new release plan:

1. The code base isn't complete now, so creating a 6.2 branch would be premature. It would imply merging devel into 6.2, or cherry-picking code from devel.

2. We don't want last-minute code to become part of 6.2, except for code that I personally approve.

Edward

Edward K. Ream

unread,

Mar 11, 2020, 7:53:03 AM3/11/20

to leo-editor

On Wed, Mar 11, 2020 at 5:43 AM Edward K. Ream <edre...@gmail.com> wrote:

1. The code base isn't complete now, so creating a 6.2 branch would be premature. It would imply merging devel into 6.2, or cherry-picking code from devel.

Actually not. I could fix any last-minute bugs in the 6.2 branch, then merge the branch into devel.