| *** gomarivera has joined #storyboard | 01:51 | |
| *** gomarivera has quit IRC | 02:29 | |
| *** jamesmca_ has joined #storyboard | 03:05 | |
| *** jamesmca_ has quit IRC | 03:09 | |
| *** Dobroslaw has joined #storyboard | 06:12 | |
| *** jamesmca_ has joined #storyboard | 07:06 | |
| *** jamesmca_ has quit IRC | 07:10 | |
| *** jamesmca_ has joined #storyboard | 09:06 | |
| *** jamesmca_ has quit IRC | 09:11 | |
| *** persia_ has quit IRC | 09:38 | |
| *** persia has quit IRC | 09:38 | |
| *** persia has joined #storyboard | 09:39 | |
| *** persia_ has joined #storyboard | 09:41 | |
| *** jamesmca_ has joined #storyboard | 10:05 | |
| *** jamesmca_ has quit IRC | 10:10 | |
| *** kamil_ has left #storyboard | 10:41 | |
| *** Dobroslaw has quit IRC | 12:30 | |
| *** jdandrea_ has joined #storyboard | 13:38 | |
| jdandrea_ | Q: Is there a consistent way for me to look at "bugs fixed in release XYZ" for a given project? | 13:40 |
|---|---|---|
| persia | jdandrea_: Do you mean to query for bugs that were open, had a task against some specific release, and had that task closed, or do you mean determine what bugs were fixed by all the changes between one release and the next? | 13:42 |
| jdandrea_ | Something along these lines: https://launchpad.net/heat/pike/pike-1 | 13:43 |
| *** jdandrea_ is now known as jdandrea | 13:43 | |
| jdandrea | This is really handy! (Spoiler: We're already in Launchpad now. Brandy new. Yaaaay!) | 13:43 |
| jdandrea | (Correction, we're already in *Storyboard* now!) | 13:44 |
| persia | So, "no". | 13:44 |
| persia | There is limited API support for "milestone" in Storyboard, but I keep intending to submit a patch to make it go away (I am having some issues with the migrations) | 13:45 |
| jdandrea | Ah. | 13:45 |
| persia | Do you usually use that report to plan a milestone, or after a milestone has been released? | 13:46 |
| persia | If the former, I suspect you'll find that creating a worklist in Storybord achieves most of what you need. | 13:46 |
| persia | If the latter, I would recommend querying the git history (either with relno or something else, depending on what sort of output you need). | 13:47 |
| jdandrea | I use it for both. Better yet, I don't create it. It's automagic, and I can direct folks to it without having to use lower level tools. | 13:47 |
| jdandrea | Hmm. Maybe there's something I can do with tagging. | 13:47 |
| persia | You don't create the milestone names? | 13:47 |
| jdandrea | Someone creates the milestone names, yep. But the list is populated automatically and then folks can just look at it. I'm trying to think of a way to do that in Storyboard. | 13:48 |
| persia | Indeed. You could tag things with something like "milestone-heat-pike-1" and set up an automatic worklist that would be similar to the LP repor. | 13:48 |
| jdandrea | Maybe I just tag it? | 13:48 |
| jdandrea | Ahh. | 13:49 |
| jdandrea | That's good! | 13:49 |
| persia | And if anyone wants to add something, they just add that tag to a story, and it automatically joins the worklist. | 13:49 |
| jdandrea | Bam. | 13:49 |
| jdandrea | Er, um, I mean boom. :) | 13:49 |
| persia | The only inconvenient bit is that when things are resolved, they won't display on the worklist by default. | 13:49 |
| jdandrea | Ohh, if they aren't complete. Oops. Hmm ... | 13:50 |
| *** gomarivera has joined #storyboard | 13:50 | |
| persia | So if you want a retroactive report showing not only what needs doing, but what has already been achieved, I suspect you'll need to play with the view settings a little. | 13:50 |
| jdandrea | Aye. | 13:50 |
| jdandrea | Fun things to ponder... thx! | 13:50 |
| persia | I don't beleive that resolved tasks are removed from the worklist, just not shown by defaut, so it ought be easy to find them, although maybe less easy to share a URL that shows them. | 13:51 |
| jdandrea | *nodnod* | 13:51 |
| SotK | merged/completed things should appear in the worklist I think, unless you explicitly filter by only active stories/unmerged tasks | 13:51 |
| persia | SotK: Ah, cool. Thanks for the clarification. | 13:52 |
| jdandrea | That would be superb. :) | 13:52 |
| SotK | if they don't, I'd class it as a bug :) | 13:53 |
| jdandrea | *reading the Boston Summit slides* "Automatic Lanes" - checking those out. | 13:53 |
| persia | Note that the semantics are a bit confusing. If you use Storyboard in a similar way to launchpad (one task per project per story), then the report will be very similar (filter for tasks in your project that have the appropriate tag). If you use Storyboard with many tasks per story, and want to have different tasks in the same story in different milestones, that might be harder to do. | 13:53 |
| *** diablo_rojo has joined #storyboard | 13:53 | |
| jdandrea | persia: Makes sense. I'm wanting to exploit the features that make Storyboard awesome while still having some of that automatic list fu I see in Launhpad, basically. | 13:54 |
| persia | jdandrea: I'm sure you'll find the right balance over time: in my mind, tools should be flexible enough to let anyone do what they want, mostly how they want, and still share data with people who do it the other way. | 13:55 |
| persia | Unfortunately, this means the tools I like tend not to have much in the way of "the way to do it". | 13:56 |
| persia | I know that some teams that use Storyboard have found the UI limiting for some of the reports they want, etc., and have written small clients to extract data from the API directly. I don't think you need that now, but you might keep it in mind if you end up reaching the limitations of automatic worklists. | 13:57 |
| *** jamesmca_ has joined #storyboard | 14:10 | |
| *** diablo_rojo has quit IRC | 14:11 | |
| jdandrea | Right, flexibility is paramount! Where "the way to do it" helps me is I can use aspects of what I already know in other projects. It may be that this naturally evolves over time so that it's a non-issue, and without hampering flexibility. | 14:19 |
| jdandrea | And the API-first thinking is great. | 14:20 |
| *** gomarivera has quit IRC | 14:35 | |
| *** jamesmca_ has quit IRC | 14:42 | |
| *** jamesmca_ has joined #storyboard | 14:42 | |
| *** jamesmca_ has quit IRC | 15:17 | |
| *** gomarivera has joined #storyboard | 16:32 | |
| *** jamesmca_ has joined #storyboard | 17:17 | |
| *** jamesmca_ has quit IRC | 17:21 | |
| fungi | persia: jdandrea: discussion from today's release team meeting is timely... http://lists.openstack.org/pipermail/openstack-dev/2017-June/117868.html | 17:26 |
| fungi | basically there is work underway to get the same integration in the release tools as we have leaving comments on lp bugs right now when commits appear in a new release and indicate in their commit messages that they close specific bugs (those "fix released in version <blah>" comments on lp bugs) | 17:27 |
| fungi | so hopefully in the very near future, projects under release management will be getting those comments in their stories automatically where some task is covered in a commit appearing in a new release | 17:28 |
| fungi | and the release management tooling is freely available for others to run independently as well | 17:28 |
| persia | Hmm... This is another case where the semantics are tricky. | 17:30 |
| persia | That functionality seems like it will update a *story* when the story is referenced properly in a commit performed in the milestone (unless I misunderstand the tool in question). | 17:30 |
| persia | But if anyone has a story where there are multiple tasks against the same project in different milestones, it is confusing. | 17:31 |
| fungi | yes, the data model will need some tweaking for storyboard to identify which specific tasks were merged in a release | 17:31 |
| persia | (launchpad didn't allow that, which is one of the complaints against launchpad, but it seems we rely on it in some ways) | 17:31 |
| fungi | the data model for the release tooling will need tweaking, i mean | 17:31 |
| persia | I suppose that as long as developers include task numbers in the commit messages, the tooling can extract that, and provide a summary of which tasks are included in a milestone release. | 17:32 |
| fungi | right, and including task numbers is encouraged anyway since that's what drives the gerrit its-storyboard plugin automation to automagically transition task states for you | 17:32 |
| persia | Heh, yeah, and now you have filled my mind with schemes to store useful task activity metadata in ways that allow post-commit manual adjustment to be comprehended by external tooling (e.g. release tooling), which I fear is a larger problem than I can comprehend on a Friday afternoon. | 17:36 |
| *** gomarivera has quit IRC | 17:41 | |
| *** gomarivera has joined #storyboard | 18:36 | |
| *** jamesmca_ has joined #storyboard | 18:39 | |
| *** jamesmca_ has quit IRC | 18:43 | |
| *** gomarivera has quit IRC | 19:00 | |
| *** jamesmca_ has joined #storyboard | 19:14 | |
| *** jamesmca_ has quit IRC | 19:19 | |
| *** diablo_rojo has joined #storyboard | 19:39 | |
| jdandrea | @fungi thx! | 20:39 |
| *** gary_perkins has quit IRC | 22:40 | |
| *** gary_perkins_ has joined #storyboard | 22:40 | |
| *** gary_perkins_ is now known as gary_perkins | 22:40 | |
| *** diablo_rojo has quit IRC | 23:08 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!