Magit: Onward to the next major version

Created on 22 Feb 2017  路  5Comments  路  Source: magit/magit

Over the last few weeks I have opened many new issues outlining new features I intend to implement and/or describing limitations of the current implementation and my plans to address those.

Some of these issues are still a bit vague in their present form. For the most part each these issues "translates" a one-line entry in my magit-todo.org file to something more suitable for others to think about and comment on. I intend to improve these issues over time (by editing the original post in many cases).

Even though development has slowed over the last few months I am not out of ideas at all. I was just busy outlining my future work!

Most helpful comment

As much as I like closing issues - this isn't quite done yet.

I also like shiny things and round numbers, so guess what - #3000 stays open until v3.0.0 is released. I might even tag it as v3.0.0.0, just because. :stuck_out_tongue_winking_eye:

All 5 comments

I'm impressed by the sheer quantity of feature request issues you've created for yourself, when you could well be resting on your laurels.

Magit clearly isn't in danger of dropping off of anyone's list of favourite packages...

I've now also roughly categorized those and other issues in a "project".

Should this issue be closed?

As much as I like closing issues - this isn't quite done yet.

I also like shiny things and round numbers, so guess what - #3000 stays open until v3.0.0 is released. I might even tag it as v3.0.0.0, just because. :stuck_out_tongue_winking_eye:

Is it a coincidence that this issue is #3000 and the version is v3.0.0? :)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mrkkrp picture mrkkrp  路  5Comments

razzmatazz picture razzmatazz  路  3Comments

garvinguan picture garvinguan  路  3Comments

mrmagooey picture mrmagooey  路  4Comments

ninrod picture ninrod  路  4Comments