17:00:58 <sergmelikyan> #startmeeting murano
17:00:59 <openstack> Meeting started Tue Dec  8 17:00:58 2015 UTC and is due to finish in 60 minutes.  The chair is sergmelikyan. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:02 <openstack> The meeting name has been set to 'murano'
17:01:22 <sergmelikyan> o/
17:01:24 <freerunner> o/
17:01:25 <kzaitsev_mb> o/
17:01:30 <sergmelikyan> Welcome to our weekly meeting :)
17:03:04 <kzaitsev_mb> shame enthurohini is not here today. Gotta ping her to see if she actually can make it to this meeting. wonder which TZ she lives in
17:03:11 <stan_lagun> o/
17:03:29 <sergmelikyan> kzaitsev_mb: I believe its UTC +5:30
17:04:13 <sergmelikyan> https://wiki.openstack.org/wiki/Meetings/MuranoAgenda - our agenda for todays meeting
17:04:25 <sergmelikyan> #topic Action Items Review
17:05:06 <kzaitsev_mb> I've finished mine with the bps
17:05:21 <kzaitsev_mb> superceeded one with the other and updated description on the 2d one
17:05:32 <kzaitsev_mb> #link https://blueprints.launchpad.net/murano/+spec/better-package-dependency-ui
17:05:42 <ativelkov> o/
17:06:10 <sergmelikyan> kzaitsev_mb: thank you :)
17:06:16 <freerunner> I've finished investigation of rtfd hooks ;)
17:06:34 <freerunner> Now we have rtfd post job on review
17:06:46 <freerunner> #link https://review.openstack.org/#/c/254855/
17:07:29 <kzaitsev_mb> wow, great!
17:08:02 <sergmelikyan> awesome!
17:08:05 <freerunner> kzaitsev_mb: It turned out, it's easier than I thought
17:08:22 <ativelkov> cool!
17:08:51 <sergmelikyan> #topic Dropping Milestones and Blueprints
17:09:05 <sergmelikyan> kzaitsev_mb: next topic is added by you - proceed please )
17:10:14 <kzaitsev_mb> so the idea is — many projects start abandoning using milestones and blueprints.
17:11:04 <kzaitsev_mb> The general direction is that launchpad will no longer be used to track what has been done
17:11:23 <kzaitsev_mb> by openstack projects — just to track what is about to be done
17:11:40 <kzaitsev_mb> for tracking what has been done we would use RENO anyway
17:12:04 <kzaitsev_mb> #link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081435.html
17:12:26 <stan_lagun> kzaitsev_mb: it is hard to use list of bugs without understanding if they were fixed already on not
17:12:27 <kzaitsev_mb> here is the thread from Ironic guys, where they discuss the same idea
17:12:56 <kzaitsev_mb> stan_lagun: as soon as the commit lands the bug is going to be moved to Fix Released
17:12:59 <kzaitsev_mb> starting today
17:13:17 <sergmelikyan> this does have sense, tho I am sure that we should not do that in Mitaka
17:13:35 <kzaitsev_mb> sergmelikyan: yep. I'm not pushing this, tbh.
17:14:09 <kzaitsev_mb> I just wanted for you guys to be aware of the direction openstack and it's release tracking tools are heading.
17:16:09 <kzaitsev_mb> I'm not 100% sure on the milestones part of the idea. But I kind of like the blueprints part. We use/have specs anyway
17:16:36 <sergmelikyan> kzaitsev_mb: I think this is logical continuation of the idea of moving train
17:17:06 <kzaitsev_mb> So a feature either requires a spec or does not require a blueprint and can be tracked as a bug..
17:17:31 <sergmelikyan> kzaitsev_mb: I actually like idea of stop using milestones - what the reason to have them?
17:17:34 <kzaitsev_mb> Well what I want is to make you think a bit on these 2 ideas =)
17:17:48 <sergmelikyan> kzaitsev_mb: Already do :)
17:17:55 <ativelkov> So, does this mean that every landed patch will result in a tar all?
17:17:56 <ativelkov> Tarball*
17:18:01 <stan_lagun> blueprints currently are the only way to track dependencies between features
17:18:27 <kzaitsev_mb> ativelkov: for stable branches starting with liberty this is the case
17:18:44 <kzaitsev_mb> stan_lagun: fair point. but do we use this feature?
17:18:48 <sergmelikyan> ativelkov: it's already happening - on each commit there is a tarball
17:19:01 <sergmelikyan> I mean there is only one tarball which is rebuilt on each commit
17:19:02 <ativelkov> I see
17:19:17 <stan_lagun> kzaitsev_mb: I do. For complex features with a lot of tasks it make sense to use
17:19:26 <kzaitsev_mb> sergmelikyan: ativelkov: well actually I haven't released one for L. Plan to do, maybe this week =) We had a number of patches land there
17:19:50 <stan_lagun> also blueprint is the place where you can save a link to etherpad
17:22:10 <freerunner> kzaitsev_mb: What about for tracking new tests, for example? Test is not a feature...
17:23:11 <kzaitsev_mb> Let's do it this way — I'd write an email to ML, summarising pros and cons of both of these ideas and we'll have a discussion there. Then after we have a couple of opinions I'll add the same item to our meeting agend again, to finalise the decision? What do you think?
17:23:51 <freerunner> kzaitsev_mb: Agreed.
17:25:06 <kzaitsev_mb> #action kzaitsev_mb outline pros and cons of abandoning milestones & bps in ML
17:27:27 <kzaitsev_mb> k, so we kind of like the idea of not using milestones and kind of dislike the idea of not using BPs =)
17:33:43 <kzaitsev_mb> sergmelikyan: let's move to open discussion maybe? =)
17:33:54 <sergmelikyan> I thought we already there )
17:34:00 <sergmelikyan> #topic Open Discussion
17:36:25 <kzaitsev_mb> seems a bit slow today =)
17:43:09 <kzaitsev_mb> I suggest we end the meeting early today =)
17:44:09 <freerunner> + ;)
17:45:14 <kzaitsev_mb> sergmelikyan: ^^
17:56:18 <sergmelikyan> #endmeeting