The problem in the trac.kodi from - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222) +--- Forum: Website and Forum Issues or Suggestions (https://forum.kodi.tv/forumdisplay.php?fid=35) +--- Thread: The problem in the trac.kodi from (/showthread.php?tid=293890) |
The problem in the trac.kodi from - ymca - 2016-10-15 I saw that the bug track from here was changed from "Future / Pending " to "Pending (DO NOT CHANGE)". http://forum.kodi.tv/showthread.php?tid=262144&page=3 Can someone tell me what does it mean? Thanks. RE: The problem in the trac.kodi from - Kib - 2016-10-15 The description of the different milestones was changed to make it clear to people submitting a bug that they should not set the milestones themselves. The description for the 'Future / Pending' milestone was first changed to 'Pending (DO NOT CHANGE)' but later changed to 'Pending (only Team-Kodi changes this)' because it is more clear. I think this was done because there were quite a few people making bugs or feature requests and then assigning them to the workload of Krypton, which is not possible anymore: Krypton is already past beta so only real fixes for bugs currently present are considered for this milestone. The management of milestones is normally done by the release manager. RE: The problem in the trac.kodi from - Martijn - 2016-10-15 Or changed/managedby any team developer as they know it's feasible RE: The problem in the trac.kodi from - ymca - 2016-10-26 (2016-10-15, 12:27)Martijn Wrote: Or changed/managedby any team developer as they know it's feasible So the problem in the subtitle download button will be fixed in Kodi 17 or in the 18 version? RE: The problem in the trac.kodi from - Kib - 2016-10-28 Which trac ticket are you referring to specifically? RE: The problem in the trac.kodi from - ymca - 2016-10-28 (2016-10-28, 07:05)Kib Wrote: Which trac ticket are you referring to specifically? http://trac.kodi.tv/ticket/16811 I have looked again now at the ticket and saw they commented there about the problem, so I guess they are working on fixing it. |