|
| 1 | +# Roadmap |
| 2 | + |
| 3 | +This document describes the roadmap for coverlet showing priorities. |
| 4 | +Maintain coverlet means like any other project two things, answer/resolve soon as possible new issues that are blocking our users an second improve product with new features and enhancements in different areas. |
| 5 | +All coverlet issues are labeled and categorized to better support this activites. |
| 6 | + |
| 7 | +As soon as an issue is open is labeled with `untriaged` if not immediately solvable(we need to do some debugging/PoC to understand where is the issue). |
| 8 | +After triage a final correct label is applied and will be taken into account depending on priority order. |
| 9 | +We use `needs more info` if we're waiting for answers. |
| 10 | + |
| 11 | +Default priority order "should" be: |
| 12 | + |
| 13 | +1) Bugs: we should fix bugs as soon as possible and for first bugs related to coverage because this is the goal of coverlet. |
| 14 | + |
| 15 | +Coverage bugs: https://github.com/tonerdo/coverlet/issues?q=is%3Aissue+is%3Aopen+label%3Abug+label%3Atenet-coverage |
| 16 | +Other bugs: https://github.com/tonerdo/coverlet/issues?q=is%3Aissue+is%3Aopen+label%3Abug |
| 17 | + |
| 18 | +2) New features: analyze and add new features, we have three drivers so features could be related to one of these. |
| 19 | + |
| 20 | +Feature requests: https://github.com/tonerdo/coverlet/issues?q=is%3Aissue+is%3Aopen+label%3Afeature-request |
| 21 | + |
| 22 | +3) Performance: we never worked on performance aspect of coverlet, it makes sense for a "new project with some hope", but today coverlet is the facto the dotnet coverage tool, so we HAVE TO approach this aspect. |
| 23 | + |
| 24 | +Performance issues: https://github.com/tonerdo/coverlet/issues?q=is%3Aissue+is%3Aopen+label%3Atenet-performance |
| 25 | + |
| 26 | +Some new features have got a `Discussion` label if we don't have and agreement yet on semantics. |
| 27 | +Discussions: https://github.com/tonerdo/coverlet/issues?q=is%3Aissue+is%3Aopen+label%3Adiscussion |
| 28 | + |
| 29 | +## New features roadmap |
| 30 | + |
| 31 | +This is the list of features we should develop soon as possible: |
| 32 | + |
| 33 | +### High priority |
| 34 | + |
| 35 | +- https://github.com/tonerdo/coverlet/issues/328 Option to ignore field/property initializers and auto-implemented properties |
| 36 | + |
| 37 | +- Allow merge reports solution wide on all flavours https://github.com/tonerdo/coverlet/issues/662 https://github.com/tonerdo/coverlet/issues/357 |
| 38 | + |
| 39 | +- https://github.com/tonerdo/coverlet/issues/804#issuecomment-611487750 Some perf improvements |
| 40 | + |
| 41 | +### Low priority |
| 42 | + |
| 43 | +- https://github.com/tonerdo/coverlet/issues/808 Rethink hits reports strategy |
| 44 | +- https://github.com/tonerdo/coverlet/issues/705 Support coverage on netfx for collectors integration |
| 45 | + |
| 46 | +## Maintainers discussion channel |
| 47 | + |
| 48 | +[As maintainers we should try to find a way to keep in synch, we could use a chat where we can "take note" of progress and if possible answer to questions/doubt, I know this is OSS, but it's hard keep project at high level without "more ideas".] |
| 49 | + |
| 50 | + |
0 commit comments