On the 0x223 day of Apache Harmony Geir Magnusson, Jr. wrote: > Egor Pasko wrote: > > On the 0x223 day of Apache Harmony Geir Magnusson, Jr. wrote: > >> Egor Pasko wrote: > >>> On the 0x222 day of Apache Harmony Geir Magnusson, Jr. wrote: > >>>> I thought we had it configured that when a JIRA is modified, the > >>>> reporter is notified directly... I'm not sure that really helps > >>>> though. I wonder if we should just open things up a bit and let any > >>>> user modify a JIRA and see what happens. > >>> reporters are notified, that's right > >>> But what if <reporter>=<patch publisher>? Then someone still needs to > >>> review. Sometimes, reporters are not familiar with the components > >>> fixed, someone needs to pick up a review in this case too. > >> That's why I watch things I'm interested in. > >> > >>> I just look at all Harmony JIRA notifications. There are a lot, but > >>> most can be safely skipped by subject. > >> Right - do a watch on the JIRAs you are interested in - they come to > >> you directly, not to the project JIRA stream. > > Is there any other way to be notified with new issues than to > > subscribe for the whole JIRA stream? I would love to use it. > > I want to be sure to get the whole stream, and then just filter for > things I want to look for. > > Unless this is something that lots of people need - having a separate > "new JIRA" mail stream, I think that you might want to try that :)
You knew that! I am like lots of people dying from a separate "new JIRA" stream desire. Thanks for suggestion, I should heve found that, pretty obvious. Now back to fighting this killing-me-outlook that has a limit-to-number-of-filters feature that I constantly suffer from. > geir > > > P.S: "watch" is a good feature, I have been using it. > > > >> geir > >> > >>>> geir > >>>> > >>>> Sian January wrote: > >>>>> Hi, > >>>>> I have just discovered that it's not possible for a contributor to > >>>>> set > >>>>> "Patch available" on a JIRA unless they reported it. (I'm not sure > >>>>> about > >>>>> committers as I'm not one...) I imagine this is to stop people coming > >>>>> in > >>>>> and editing other details on the JIRA, so I can see that it makes > >>>>> sense. My > >>>>> question is, what is the best thing to do if I attach a patch to a JIRA > >>>>> and > >>>>> I can't set "Patch available"? I can think of three alternatives at the > >>>>> moment: > >>>>> 1. Assume that the reporter will notice and set it themselves (or > >>>>> commit the > >>>>> fix if they're also a comitter) > >>>>> 2. E-mail the reporter privately > >>>>> 3. Post to the mailing list > >>>>> Or a fourth alternative would be a combination of the above where > >>>>> the person > >>>>> who contributed the patch waits a few days before doing either 2 or 3. > >>>>> Any > >>>>> thoughts on what would be best? > >>>>> Thanks, > >>>>> Sian > >>>>> > >>>> > > > -- Egor Pasko
