This is a good question and I think it's fair to say that we could
use STATUS. There are sections for showstoppers as well as a wish list
section. Obviously, looking at trunk STATUS, there's some stuff in there
that can be cleaned up a bit, but it seems to have all of the sections
needed. Prioritization can be difficult since we are a workforce of
volunteers, but I'm a fan of lists. As I bet is the case for most, I
tend to knock things out at the top of the list before moving down the
list. Perhaps the sections (like WISH LIST) can be sorted by order of
times users report things or we come across it in our own testing?
Resending to dev list
On 11/4/2017 5:46 AM, Luca Toscano wrote:
> I have a question for you about how do we plan to collect/list the
> 'known issues' in trunk, in order to address them properly in the next
> iterations of the 2.5.0 process to become a stable release.
> For example, there is this thread that I'd really think is important:
> I also believe that other people have pointers to things that would
> need some love in trunk, but of course nobody has the overall complete
> picture (I think). Would a section in STATUS be a starting point? I've
> read it this morning and I found a ton of things to improve and a lot
> of suggestions, that would probably require a big workforce to be
> completed (in parallel to keeping 2.4.x up to date with bug fixes
> etc..). Do we have an idea how to prioritize the work (or simply
> decide the 'must' vs 'nice to have')?