Hello,
as Mike said, here my proposal for handling bugs for the upcoming release:
i) Every bug will get a difficulty assigned either Easy, Difficult, or
Impossible, this is to ensure that new people, and people that don't
know the subsystem or context very well can also help bugfixing.
ii) I am going to create 4 new workboards:
- primitives: Stuff that has its root problems in eina, eo, (low in our
software stack)
- interfaces: A Bug is caused due to the movement to a different
namespace, refactoring into new classes, or changes related to new efl_*
code / classes.
- rendering: A Bug is located in the engine code for some protocol/platform
- widgets: Your usage of elm widgets broke somewhere between efl-1.20
and the current state.
iii) If you work on a bug, claim it for you. If a other bug sneaks in
between, or there is no time in the next week or so: Document your
findings, and remove your name from the assignee field on phabricator,
so someone else might work on the bug.
Any objections ? For Monday I am planning to go through the bugtracker
trying to assign difficulities, and workboards.
Greetings,
bu5hm4n
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
