When to mark a bug as STAGED

Rosanne DiMesio dimesio at earthlink.net
Tue Nov 7 12:42:42 CST 2017


On Tue, 7 Nov 2017 15:28:11 +0330
Henri Verbeet <hverbeet at gmail.com> wrote:

> On 7 November 2017 at 14:27, KKing <kicking177 at gmail.com> wrote:
> > IMO: If not in staging, then there should be an alternative place for such
> > hacks or patches, ideally that the AppDb can point to.
> Traditionally we've just attached those kinds of hacks to the
> corresponding bug report.
> 
> 
There was also the old repo at http://repo.or.cz/wine/hacks.git, which had the advantage of making it clear to users that they were hacks. The problem I have with marking hacks as STAGED is that will create an endless procession of users asking when the fix that has been STAGED for x years is finally going to be included in Wine. The distinction Sebastian has been trying to make between hacks and patches being worked on has not been made clear enough to users--they should not have to hunt through an outside website to find that out--but IMO it is a useful distinction. 

-- 
Rosanne DiMesio
dimesio at earthlink.net



More information about the wine-devel mailing list