| *** hidekazu has joined #storyboard | 00:16 | |
| hidekazu | hello, storyboard developers. | 00:17 |
|---|---|---|
| *** gomarivera has quit IRC | 00:17 | |
| hidekazu | i am member of watcher project. | 00:18 |
| hidekazu | how can we know series and milestones? | 00:18 |
| *** gomarivera has joined #storyboard | 00:18 | |
| *** gomarivera has quit IRC | 00:19 | |
| hidekazu | it seems not possible. | 00:19 |
| *** gomarivera has joined #storyboard | 00:19 | |
| hidekazu | i want to know that is by design or not. | 00:19 |
| *** gomarivera has quit IRC | 00:29 | |
| diablo_rojo_phon | hidekazu I would suggest the use of tags? It's up to your project how you want to organize tasks. | 00:38 |
| *** gomarivera has joined #storyboard | 00:39 | |
| hidekazu | diablo_rojo_phon: thanks proposing. can we choose list by tags? | 00:48 |
| diablo_rojo_phon | Yep :) You can set up a list to pull in everything with a certain tag. | 00:49 |
| diablo_rojo_phon | hidekazu: ^^ | 00:53 |
| hidekazu | diablo_rojo_phon: hmm.. BTW, can i try storyboard? gerrit has sandbox. but i can not find in storyboard. | 00:55 |
| diablo_rojo_phon | hidekazu, Yes, storyboard has a sandbox too. Let me grab the link. | 00:57 |
| hidekazu | diablo_rojo_phon: nice! | 00:57 |
| diablo_rojo_phon | https://storyboard-dev.openstack.org/ | 00:57 |
| diablo_rojo_phon | There you go :) | 00:57 |
| hidekazu | diablo_rojo_phon: i will introduce this site to our members. | 00:58 |
| *** gomarivera has quit IRC | 01:00 | |
| *** diablo_rojo has joined #storyboard | 01:02 | |
| *** gomarivera has joined #storyboard | 01:04 | |
| *** gomarivera has quit IRC | 01:06 | |
| *** gomarivera has joined #storyboard | 01:07 | |
| *** gomarivera has quit IRC | 01:07 | |
| *** gomarivera has joined #storyboard | 01:08 | |
| *** diablo_rojo has quit IRC | 01:09 | |
| diablo_rojo_phon | hidekazu: that would be wonderful! Thank you :) | 01:16 |
| *** diablo_rojo has joined #storyboard | 01:26 | |
| *** gomarivera has quit IRC | 01:44 | |
| *** gomarivera has joined #storyboard | 01:44 | |
| *** gomarivera has quit IRC | 01:48 | |
| *** diablo_rojo has quit IRC | 02:10 | |
| *** gomarivera has joined #storyboard | 02:17 | |
| *** gomarivera has quit IRC | 02:32 | |
| *** gomarivera has joined #storyboard | 02:33 | |
| *** gomarivera has quit IRC | 02:45 | |
| *** gomarivera has joined #storyboard | 02:45 | |
| *** gomarivera has quit IRC | 02:50 | |
| *** diablo_rojo has joined #storyboard | 03:08 | |
| *** jamesmcarthur has joined #storyboard | 03:36 | |
| *** jamesmcarthur has quit IRC | 03:40 | |
| *** EmilienM has quit IRC | 04:30 | |
| *** EmilienM has joined #storyboard | 04:37 | |
| *** hidekazu has left #storyboard | 04:46 | |
| *** diablo_rojo has quit IRC | 05:15 | |
| *** diablo_rojo has joined #storyboard | 06:33 | |
| *** jamesmcarthur has joined #storyboard | 07:37 | |
| *** jamesmcarthur has quit IRC | 07:42 | |
| *** gomarivera has joined #storyboard | 07:46 | |
| *** gomarivera has quit IRC | 07:50 | |
| *** jamesmcarthur has joined #storyboard | 08:19 | |
| *** jamesmcarthur has quit IRC | 08:23 | |
| *** diablo_rojo has quit IRC | 08:51 | |
| *** Dobroslaw has quit IRC | 11:51 | |
| *** gomarivera has joined #storyboard | 13:14 | |
| *** gomarivera_ has joined #storyboard | 13:15 | |
| *** gomarivera has quit IRC | 13:15 | |
| *** gomarivera_ has quit IRC | 14:22 | |
| *** jamesmcarthur has joined #storyboard | 14:37 | |
| *** jamesmcarthur has quit IRC | 15:10 | |
| *** jamesmcarthur has joined #storyboard | 15:11 | |
| *** gomarivera has joined #storyboard | 16:36 | |
| *** jamesmcarthur has quit IRC | 16:58 | |
| *** bethwhite has quit IRC | 17:06 | |
| *** jamesmcarthur has joined #storyboard | 18:28 | |
| SotK | anyone around for a storyboard meeting today? | 19:00 |
| fungi | heh, i looked in #openstack-meeting but not in here | 19:06 |
| * SotK goes into there | 19:07 | |
| fungi | meant to double-check my facts on my reply to the release automation thread here: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118307.html | 19:09 |
| fungi | if anybody has time to skim that and maybe correct me | 19:10 |
| * SotK has a look | 19:10 | |
| fungi | thanks! | 19:10 |
| fungi | in particular, i suggested adding release details to task notes and pontificated about the possibility of creating another (closed) task state called "released" which the release tools can set | 19:12 |
| SotK | the facts you asserted are correct, and both of those ideas seem fairly sensible to me | 19:17 |
| SotK | if a "released" task status would be useful it would be trivial to add one | 19:18 |
| SotK | the only issue I could see is folk wondering "what is the difference between released and merged?", but I think that is easily explained and understood | 19:19 |
| SotK | (it also seems to me like it would be useful, since we have no nice support for anything like that in sb at the moment, and I suspect we should) | 19:19 |
| SotK | the task note thing seems a bit workaroundy too, but short of "redo the implementation of milestones to be something that matches an understanding of a release milestone" I don't see a better solution | 19:21 |
| fungi | well, the milestone mechanism in lp isn't so great either. the release team gave up using it because of the requirement to configure per-project series and the general terribleness of the lp api around it | 19:28 |
| fungi | apparently some projects still use it for manual signaling on (mostly non-bug-related) tasks | 19:29 |
| fungi | but there's no release integration to update task targets after release to the correct milestones or anything | 19:30 |
| SotK | heh, then given I have no good thoughts on how it should look in storyboard, I'll not contemplate it much further yet | 19:31 |
| fungi | so no guarantee it's correct | 19:31 |
| fungi | yup. basically what the release scripts _used_ to do was go through open bugs matching the milestone which was just tagged and retarget them to the next milestone | 19:32 |
| fungi | and some teams still do that themselves on an individual basis | 19:33 |
| fungi | but all the release tools do any longer is leave a bug comment if a commit claiming to close that bug merged between the previous tag and the new one | 19:33 |
| fungi | so for feature parity with how teams are using milestones in lp today, story tags are probably fine (you can't tag tasks right?) | 19:35 |
| SotK | yep, it certainly sounds like story tags are fine for this | 19:38 |
| SotK | (indeed you cannot tag tasks) | 19:38 |
| fungi | the way lp works, you can target each bugtask to a different milestone, but other than backports (which will generally just appear in the next point release after they merge) there's not much reason for multiple bugtasks since you can only have one per series (git branch in our case) | 19:43 |
| fungi | i expect the openstack projects that are actually using the milestone features of lp only target master branch tasks anyway | 19:44 |
| *** jamesmcarthur has quit IRC | 20:09 | |
| *** jamesmcarthur has joined #storyboard | 20:09 | |
| *** jamesmcarthur has quit IRC | 20:28 | |
| *** jamesmcarthur has joined #storyboard | 21:00 | |
| *** jamesmcarthur has quit IRC | 21:05 | |
| *** gomarivera has quit IRC | 21:34 | |
| *** jamesmcarthur has joined #storyboard | 22:14 | |
| *** jamesmcarthur has quit IRC | 22:18 | |
| *** jamesmcarthur has joined #storyboard | 23:12 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!