On 4 June 2010 02:34, Bryce Harrington <[email protected]> wrote: > On Thu, Jun 03, 2010 at 08:37:39AM -0000, Abel Deuring wrote: >> I think the term "upstream" does not cover all situations where more >> than one bugtask makes sense. Other scenarios are a bug that affects a >> client and a server, or one that affects a library (maintained as a >> separate project) and an application that uses the library. > > Ah, that's a good point. What would you suggest as a more complete > wording?
I would say "Add task for project" or "Add project task" or something like that. mpt expressed reluctance in another bug to exposing the internal term "task" to users unnecessarily. However this is a concept people need to know about for intermediate-advanced use of Launchpad: having them just call it "a row in that table at the top of the bugs" isn't really helping anyone. To me the key concepts here are: * you're going to add a new dimension to the bug * it's about a project, rather than a distro package or series * to track some work that needs to be done there "Affects" is a bad word because it's overloaded by "affects me too": we see people getting confused by saying that a bug in gcc affects mysql, which is literally true but doesn't mean it needs a task against mysql. -- Martin <http://launchpad.net/~mbp/> -- "Also affects project" doesn't provide any instructions https://bugs.launchpad.net/bugs/117460 You received this bug notification because you are a member of Launchpad Documentation Team, which is subscribed to Launchpad Documentation. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-doc Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-doc More help : https://help.launchpad.net/ListHelp
