On 06/17/2016 06:41 PM, Rich Freeman wrote: > On Fri, Jun 17, 2016 at 12:00 PM, Kristian Fiskerstrand <k...@gentoo.org> > wrote: >> On 06/17/2016 03:58 PM, Rich Freeman wrote: >>> >>> That could actually be generalized. I could see many types of bugs >>> where the issue is with upstream, and we might want to track the >>> progress as upstream implements a fix, releases it, and then it is >>> stabilized on Gentoo. So, maybe we need another state to track in >>> upstream's VCS vs the Gentoo repo. >> >> For a great deal of this we have UPSTREAM keyword, and also combination >> with PATCH keyword if we've submitted an own patch. > > Usually we mean UPSTEAM to mean that the issue is an upstream issue, > and should be pursued there. Usually we don't use it to mean that the > issue IS resolved upstream but we're waiting for a release/etc. I'm
Well, the issue is still upstream in that case, so I don't see that necessarily being different, we're still waiting for a release upstream to make a new downstream ebuild and stabilize it, so it fits with UPSTREAM > not sure how important the distinction is in practice. The portage > team could of course use it differently. Yeah, I'm talking ebuilds here, not portage and similar bugs, I think your point of having own keyword for portage and the likes makes sense to distinguish it. -- Kristian Fiskerstrand OpenPGP certificate reachable at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
