Revised schedule and milestones

36 views
Skip to first unread message

Edward K. Ream

unread,
Mar 1, 2020, 7:26:21 AM3/1/20
to leo-editor
I have been dithering about what to put in Leo 6.2. At last the guiding principle is clear:

    Better to live with bugs than live with dubious bug fixes

As a result, I am declaring that 6.2 is code complete. I have assigned #1516 to Matt. He can fix this issue or defer it, as he chooses.

I have just reassigned issues to the 6.3, 6.4 and 6.5 milestones as follows:

Leo 6.3

This will contain fixes for all serious known bugs. Expect a period of at least a month between the last bug fix and 6.3b1.

Leo 6.4

This is scheduled for the end of this year. It will contain the most important remaining enhancements, including two big projects relating to key bindings:

#1269: [Likely]: table-based key handling.

#1235: [Experimental]: support for neovim.

Leo 6.5

This will contain everything else. Some may be promoted to 6.4, depending on demand and schedule.

Summary

Leo 6.2 is code complete. Expect 6.2 b1 in a day or two.

Leo 6.3 will fix all remaining bugs. It will go out the door only after at least a month of testing.

Leo 6.4 will focus on key-handling. It is scheduled for December 1, 2020.

Leo 6.5 contains everything else. If something on this list seems important to you, feel free to do it yourself :-)

Finally, I have cleared the milestones for all delegated projects. This simply means that I don't know when, or if, any of these projects will happen. The delegates can tell us when their work is done.

Edward

Edward K. Ream

unread,
Mar 1, 2020, 7:31:57 AM3/1/20
to leo-editor
Here are the links to the various milestones:


And here is the link to Leo's milestones themselves.

Edward

Edward K. Ream

unread,
Mar 2, 2020, 7:06:29 AM3/2/20
to leo-editor
On Sunday, March 1, 2020 at 6:26:21 AM UTC-6, Edward K. Ream wrote:

I have been dithering about what to put in Leo 6.2. At last the guiding principle is clear:

    Better to live with bugs than live with dubious bug fixes

As a result, I am declaring that 6.2 is code complete.

There have been several bugs reported recently. They all seem minor, so it should be safe to fix them all before Leo 6.2.b1.

Edward
Reply all
Reply to author
Forward
0 new messages