Tuesday, 2016-03-22

*** thinrichs has quit IRC00:01
*** thinrichs has joined #openstack-release00:03
*** thinrichs has quit IRC00:15
*** daemontool_ has joined #openstack-release00:26
*** daemontool has quit IRC00:27
*** gordc has joined #openstack-release00:30
*** dims has joined #openstack-release00:57
*** kzaitsev_mb has quit IRC01:04
*** sdake has quit IRC01:06
*** sdake has joined #openstack-release01:08
*** sdake_ has joined #openstack-release01:11
*** sdake has quit IRC01:14
*** mriedem has quit IRC01:17
*** sigmavirus24_awa is now known as sigmavirus2401:21
*** sigmavirus24 is now known as sigmavirus24_awa01:22
openstackgerritAdam Gandelman proposed openstack/releases: Astara mitaka release candidate  https://review.openstack.org/29558901:31
openstackgerritMerged openstack/releases: ironic-python-agent 1.2.0  https://review.openstack.org/29555901:35
*** gordc has quit IRC02:26
*** _amrith_ is now known as amrith02:26
*** dims has quit IRC02:28
*** sdake_ is now known as sdake03:08
*** amrith is now known as _amrith_03:44
prometheanfiresomeone brought up doing uncapped (package version wise) gate jobs to catch badness in the stable branches, is any of that doc'd anywhere?04:37
prometheanfirecould be non-voting periodic with maintainers (distro) being the particular benifiting parties04:40
prometheanfiretonyb: here04:40
prometheanfirenot -stable04:40
tonybAh okay04:40
prometheanfire-stable is dead iirc, long live -releases04:40
tonybprometheanfire: nope, I'm in stable all the time it is a good place to talk about stable specific stuff04:41
prometheanfireshould I be asking that there then?04:41
clarkbfwiw thats basically how the constraints update jobs work04:41
tonybprometheanfire: do you mean pip install without constraints?04:41
prometheanfireyes, without04:42
tonybprometheanfire: here is fine.04:42
prometheanfireI've been told that deps of openstack serices (nova/cinder/keystone/etc) should be supported uncapped for two releases04:43
prometheanfireI'd like tests for that04:43
clarkbwe do test it whenever we update constraints04:43
prometheanfirethen I could just pay attention to requirements.txt and dev-reqs.txt updates instead of upper-reqs04:43
clarkbalso I dont know that openstack has ever made that promise04:43
prometheanfireI've been told that in here, it wasn't a promise yet, but more of an expectation04:44
prometheanfireif I leave my deps uncapped, where can I get updates as to when I need to cap them for a particular project?04:44
prometheanfirefor instance only nova if only it had a problem would be optimal04:45
clarkbwhen the constraint update changes fail04:45
prometheanfirewhich are which file?04:45
prometheanfireso only when that job fails?04:45
prometheanfireI am monitoring gerrit for that file already04:45
clarkbevery day we bump them to the newest version allowed and push that to requirwments, this runs a bunch of tests04:46
prometheanfireso it'll be somewhat easy to follow04:46
clarkbif that fails there is a good chance dep doesnt work04:46
prometheanfiremy current plan (packaging wise) is to leave mitaka uncapped and cap as needed04:46
prometheanfirethen I'll update oslo on every release instead of ignoring most of them (and other deps in openstack)04:47
prometheanfiredoes that sound sane?04:47
prometheanfirealso, my 'as needed' is defined as watching for fails in upper-reqs update jobs04:47
prometheanfireso, how are those fails handled04:47
prometheanfirea seperate commit to the same file?04:48
clarkbya usually requires human intervention to bump a subset or fix then bump04:48
prometheanfireok, then I'll only watch for updates to upper-reqs that are NOT automated04:48
prometheanfirethat'll make it easier04:49
prometheanfirewonder if I can get gerrit to only email me when something is merged04:49
prometheanfireis it the 'Submitted Changes' notification?04:50
prometheanfireguess I'll test04:50
prometheanfireclarkb: tonyb that plan sound sane btw?04:50
* prometheanfire needs to package heat this release04:51
tonybprometheanfire: +1 to adding heat04:52
clarkbI woukd watch for jenkins -1 on openstack/requirementa04:52
tonybprometheanfire: I'd need to think harder about the problem to really evaluate if that'll work.04:52
prometheanfireah, that's right, it needs to to package ALL THE CLIENTS04:52
tonybprometheanfire: doesn't horizon also need that?04:53
prometheanfiretonyb: not sure what time it is for you, but we could talk face to face vidyo04:53
prometheanfireI don't package horizon04:53
*** daemontool__ has joined #openstack-release04:53
*** daemontool_ has quit IRC04:53
prometheanfireI used to, but it's hell04:53
prometheanfireclarkb: you know the search expression?04:53
tonybprometheanfire: Ah that'd explain it.04:53
clarkbprometheanfire: not off the top of my head but it is doable and documented in gerrit docs04:53
tonybprometheanfire: Normally this would be a fine time but I need to duck out for a bit. (grab my son from school)04:54
prometheanfireclarkb: searching for status:merged might be more useful for me04:54
prometheanfiretonyb: np, mind bugging me when you get in tomorrow?04:55
tonybprometheanfire: Sure.04:56
prometheanfiretonyb: I'll try to remind you if you forget04:56
tonybprometheanfire: cool.04:57
prometheanfiremade a weekly task to check for non-automated updates to upper-reqs so I don't forget the new update procedure04:57
prometheanfirehopefully I can meet the releases / stable-maint team at summit, it'd be nice to get this type of thing sorted (policy wise) for all packagers04:58
*** kzaitsev_ws has quit IRC06:01
*** kzaitsev_ws has joined #openstack-release06:01
*** sdake has quit IRC07:29
*** daemontool__ has quit IRC07:50
openstackgerritAndreas Jaeger proposed openstack/releases: openstack-doc-tools 0.34.0  https://review.openstack.org/29566408:22
AJaegerdhellmann, dims, ttx, could we get a new release of openstack-doc-tools for Mitaka, please? ^08:23
ttxyes sure. Will process the release queue shortly08:24
AJaegerthanks, ttx!08:24
AJaegerttx, do you want me to review translations again?08:25
AJaegerttx, will do it now in case you want to take some08:31
*** openstackgerrit has quit IRC08:33
*** openstackgerrit has joined #openstack-release08:33
ttxAJaeger: can't hurt, at least for teh initial / big ones08:34
AJaegerttx, quite some large imports see https://review.openstack.org/#/q/status:open+topic:zanata/translations+branch:stable/mitaka08:34
*** daemontool has joined #openstack-release08:34
*** pcaruana has joined #openstack-release08:40
*** daemontool has quit IRC08:57
*** doug-fish has quit IRC09:04
ttxProcessing congress rc109:36
*** sdague has joined #openstack-release09:44
*** dims has joined #openstack-release09:51
*** dims has quit IRC10:04
ttxwow, that release job is dead slow10:07
ttx30min to get congress repos cloned10:07
ttxdims: please review https://review.openstack.org/#/c/294776/ to unblock patch chain10:09
patchbotttx: patch 294776 - openstack-infra/release-tools - make the default dashboard format csv10:09
*** dims has joined #openstack-release10:12
ttxaaand.. timeout.10:20
openstackgerritMerged openstack/releases: murano deliverables - mitaka  https://review.openstack.org/29557510:26
ttxkzaitsev_ws: I'll create your stable/mitaka branches from that RC1 tag10:32
ttxunless you tell me it's a bad idea10:32
*** _amrith_ is now known as amrith10:37
openstackgerritMerged openstack/releases: Release Mitaka RC1 for Congress  https://review.openstack.org/29547310:41
ttxmucho faster10:43
openstackgerritMerged openstack/releases: Astara mitaka release candidate  https://review.openstack.org/29558910:51
*** kzaitsev_mb has joined #openstack-release10:51
dimsgood afternoon ttx10:51
dimsttx : i updated the spreadsheet last night after cutting ironic-python-agent release and cutting their stable branch - fyi10:52
ttxand hi!10:53
ttxdims feel free to +A https://review.openstack.org/#/c/295137/ and https://review.openstack.org/#/c/294594/10:57
patchbotttx: patch 295137 - releases - Tacker was not part of the Liberty release10:57
patchbotttx: patch 294594 - releases - Adding missing mitaka releases10:57
ttxI think I covered all dhellmann's comments there10:57
ttxdims: I'll stop for lunch, you can process openstack-doc-tools 0.34.010:58
dimsttx : on it11:16
openstackgerritMerged openstack/releases: Tacker was not part of the Liberty release  https://review.openstack.org/29513711:19
openstackgerritMerged openstack/releases: Adding missing mitaka releases  https://review.openstack.org/29459411:19
openstackgerritMerged openstack/releases: openstack-doc-tools 0.34.0  https://review.openstack.org/29566411:20
*** daemontool has joined #openstack-release11:28
dimsAJaeger : openstack-doc-tools 0.34.0 is out11:29
AJaegerthanks, dims!11:31
AJaegerdims, please approve the requirements change as well: https://review.openstack.org/#/c/295665/11:32
patchbotAJaeger: patch 295665 - requirements - Bump uc for openstack-doc-tools 0.3411:32
dimsAJaeger : do the jobs you need this for subject to constraints? (we haven't unfreezed requirements yet)11:33
AJaegerindeed, they do not...11:33
dimsgreat! then i'll just do a W-1 on it11:35
*** gordc has joined #openstack-release11:37
*** doug-fish has joined #openstack-release11:42
openstackgerritMerged openstack-infra/release-tools: make the default dashboard format csv  https://review.openstack.org/29477611:46
openstackgerritMerged openstack-infra/release-tools: sort on the managed flag before other values  https://review.openstack.org/29477711:46
*** kzaitsev_mb has quit IRC11:47
*** doug-fis_ has joined #openstack-release11:50
*** doug-fish has quit IRC11:52
gordcdhellmann, ttx: i was wondering, does releases project only handle big tent projects or can any project under openstack domain use it?11:58
openstackgerritMerged openstack-infra/release-tools: lower case all team names to sort consistently  https://review.openstack.org/29477811:58
openstackgerritMerged openstack-infra/release-tools: add PTL email to release dashboard  https://review.openstack.org/29477911:58
dimsgordc : apply for release:managed tag first in governance? https://governance.openstack.org/reference/tags/release_managed.html12:01
dimsgordc : which project?12:01
gordcdims: just asking generically. i was asked the question recently.12:01
dimsgordc : ack, please point them to "Tag application process" at the end of that page12:02
gordci was doing a query and it seemed most the items are in some way 'official'. thanks for link though12:03
*** kzaitsev_mb has joined #openstack-release12:03
dimsgordc : right, no one else has asked i think :)12:03
AJaegergordc: but what dims says means for me : Only big tent projects12:06
AJaegersicne those are the only ones listed in governance repository12:06
dimsAJaeger : hmm, interesting12:07
dimsAJaeger : where do people ask for git repos?12:08
AJaegerdims: git repos via project-config.12:09
AJaegerdims: Example https://review.openstack.org/29526012:10
AJaegerAnd those in openstack namespace are not necessary official - they are only official ones they're approved by TC (for new team) or adopted by PTL (for new repo for existing official team)12:10
dimsAJaeger : y looking, so there's no spot in governance repo for non-bigtent projects12:10
dimsAJaeger : ack12:11
AJaegerLike https://review.openstack.org/#/c/292335/12:11
patchbotAJaeger: patch 292335 - governance - Add Designate & Zaqar roles to OpenStack-Ansible P... (MERGED)12:11
gordcah i see. so big tent only.12:11
gordccool cool12:11
AJaegerdims: indeed, there's no spot in governance for non-bigtent projects. governance == big-tent12:12
dimsttx : is this by design? ^^12:12
AJaegerand mission of release team is AFAIK: Governance ;)12:12
AJaegerdims, projects in the big tent also adhere to TC and best practices. RElesae team is enforcing some of tehse best practices and processes.12:13
dimsAJaeger : for example, dhellmann mentioned that release team could cut branches for projects that wanted them12:13
AJaegerdims: that would be IMHO a change of scope.12:13
AJaegerI'm not objecting, that's your call ;) Just pointing it out.12:13
kzaitsev_mbttx: saw your message about stable/mitaka and RC1. Thanks for cutting us a stable branch =)12:14
AJaegerit would be strange to me if a project would follow release team oversight but not TC oversight (so, releases from release team but not part of big tent)12:14
gordcAJaeger: well a team could leverage the release scripts the framework provides. but it would create a lot more work for release team to manage even more projects that don't necessarily follow typical openstack 'rules'12:15
dimsAJaeger : gordc : http://markmail.org/message/hgcx5l3btkrgr5k512:16
AJaegergordc: yep12:16
gordcdims: cool cool, i vaguely remember reading that.12:16
AJaegerdims: python-senlinclient is in governance, isn't it? For me that message means: TAke on more governance repos...12:16
dimsAJaeger : right12:17
dimsAJaeger : once we take the couple of manual steps out, all it would take is +2A to get a release out12:18
sdaguehmmm... so who has branch push rights?12:19
dimssdague : at the moment, the release managers group only so we have to manually run a script (release_from_yaml.sh) to cut tags and there's another script to create branches12:21
sdagueI'm looking at the devstack branching, and I really thought I could do this12:21
dimssdague : check ACL?12:22
sdaguedims: ok, but what about for things like devstack that don't have releases12:22
dimssdague : https://review.openstack.org/#/admin/groups/416,members - you should be all set12:23
sdagueI can definitely not push a new branch12:23
dimssdague : if you need it today, i can do it without a review (there's a ./make_stable_branch.sh script)12:24
sdaguethough I also have a bad tag out there which I need to get sorted12:24
dimssdague : which one?12:24
sdagueI was following devstack branch docs, and they said to push a tag, which is wrong.12:25
sdagueso I have a stable/mitaka tag out there12:25
dimsi see a "stable/mitaka" tag.12:25
sdagueright, so that needs deleting12:25
sdagueI do not have the rights to delete it12:25
sdaguethough I do have the rights to create it12:26
sdagueafter that we need to branch. Originally we were waiting for swift, but I've been looking at logs, and we should be fine12:26
sdagueand without the stable branch upgrade on stable/mitaka is actually testing liberty -> master12:27
sdagueso the backports aren't getting tested12:27
sdaguefor upgrade12:27
*** bdemers has quit IRC12:27
dimssdague : "git push --delete origin tagname" ?12:27
sdaguegit push gerrit :refs/tags/stable/mitaka is what the internet tells me it should be12:28
sdaguehttp://paste.openstack.org/show/491442/ is what I get12:28
dimsok. let me see if i can delete that tag12:32
sdagueI also asked yolanda in -infra12:33
sdaguedims: the make_stable_branch.sh makes a lot of assumptions about projects which I don't think apply here12:33
sdaguelike $VERSION12:33
sdagueok, the tag is deleted now12:34
dimssdague : you were able to delete it?12:34
sdagueyolanda did12:34
dimssdague : instead of the VERSION i can pass a SHA12:36
dimswhat SHA would you like?12:37
ttxdims: yes, governance == official == big-tent12:37
ttxsdague: about rights, you may be able to use the gerrit branch creation UI. At one point I could do ont without the other12:38
sdaguedims: HEAD is fine12:39
ttxfwiw I have branch/tag creation rights but no branch/tag deletion right either :)12:39
sdaguettx: where is that?12:39
dimslet me try12:39
ttxsdague: example for grenade https://review.openstack.org/#/admin/projects/openstack-dev/grenade,branches12:39
sdaguettx: I don't have create anywhere there12:40
ttxcreate branch is greyed if you don't have branch creation rights12:40
ttxsdague: ok, so that is consistent. I think you need push refs rights to create branches/tags12:40
dimssdague : done - https://github.com/openstack-dev/devstack/tree/stable/mitaka12:40
sdaguedims: cool12:41
ttx"Create Reference" maybe12:41
dimssdague : "./make_stable_branch.sh mitaka openstack-dev/devstack HEAD"12:41
ttxseparate from "Push Signed Tag"12:41
dimsttx : ah ok12:42
sdaguethere is some wiki documentation which is just really confusing here12:42
sdaguefor the QA team12:42
sdaguewill need to clean that up12:42
* ttx creates stable branches for murano12:42
dimsttx : i forgot to tell you "captain, you have the con" :)12:43
* dims wanders off to get some bfst12:43
ttxkzaitsev: all set, master open for newton development12:50
*** mriedem has joined #openstack-release12:59
*** dims_ has joined #openstack-release13:02
*** dims has quit IRC13:02
*** daemontool has quit IRC13:07
*** bswartz has quit IRC13:08
*** daemontool has joined #openstack-release13:09
*** bswartz has joined #openstack-release13:14
dims_sdague : need any others? grenade?13:33
sdagueI will, but I want to make sure the devstack branch runs right first13:33
sdaguethere are changes in queue for those now13:33
dims_ack sdague : i should be off an on today heading to BU to talk to a class about OpenStack13:34
sdagueok, no prob13:35
*** daemontool has quit IRC13:48
*** bdemers has joined #openstack-release13:50
*** daemontool has joined #openstack-release13:54
*** sigmavirus24_awa is now known as sigmavirus2414:05
*** doug-fis_ is now known as doug-fish14:11
ttxredrobot: how far are you from RC1 ?14:12
ttxdaemontool: same question ^14:13
daemontoolttx, most probably today we can tag RC114:19
*** dims_ has quit IRC14:19
daemontoolttx, ping14:32
daemontoolthe stable/mitaka branch too needs to be created by the service teams?14:33
daemontoolor x.x.x.xrc1 tag only?14:33
*** openstackgerrit has quit IRC14:33
*** openstackgerrit has joined #openstack-release14:34
*** vgridnev has joined #openstack-release14:43
redrobotttx I think we may be ready today.  I had a question regarding the release notes though.14:52
redrobotttx who moves the "unreleased" notes into a mitaka.rst page?14:52
*** sdake has joined #openstack-release14:58
ttxdaemontool: we can tag and create the branch if you submit an openstack/releases change15:03
ttxdaemontool: something like https://review.openstack.org/#/c/295473/15:04
patchbotttx: patch 295473 - releases - Release Mitaka RC1 for Congress (MERGED)15:04
ttxredrobot: I think it happens automagically. dhellmann should ba able to answer that question when he is back tomorrow15:05
daemontoolttx,  so like the pervious releases, only a change in openstack/releases is needed by the service Team, ty15:12
*** vgridnev has quit IRC15:16
*** amrith is now known as _amrith_15:18
ttxdaemontool: you don't even need to tag if you push the change, we can tag and sign for you15:18
daemontoolok ty15:19
*** vgridnev has joined #openstack-release15:28
*** bdemers has quit IRC15:34
*** bdemers has joined #openstack-release15:37
*** dims has joined #openstack-release15:45
*** vgridnev has quit IRC15:54
*** dims_ has joined #openstack-release15:55
*** dims has quit IRC15:55
*** kzaitsev_mb has quit IRC16:11
sdakedhellmann quick question16:11
sdakethere is a bit of debate about how we hsould handle backports from our master branch to our stable/mitaka branch for rc2 and rc3 bugs16:12
sdakeoption 1 is to tarrget the bug to newton and liberty16:12
sdakeoption 2 is to use rc-backport-potential tag16:12
sdakei looked around at various projects16:12
sdakeand can't find a consistent handling of how bugs are managed in the rcs so backports aren't lost16:13
sdakedhellmann when you get done with that one, i'm ready to start reno integration, if you have a pointer to a patch that introduces reno to a project, I'd super appreciate it16:13
sdakein the meantime i'm going to try to catch some  fish and dig in the other repos for that initial commit16:14
dims_sdake : dhellmann is out today. ttx and i are around for releasing things. but yeah, dhellmann is probably right for those questions :)16:15
sdakedims_ do you hve any idea?  I pinged ttx offf-channel before thinking to ask here :)16:16
sdakeand he seems to be afk16:16
dims_y, a bit late in the day for him16:16
clarkbyou can probably just look at any project that uses reno16:16
sdakeusuallly he is around at my 8am timestart16:16
dims_sdake : Nova uses the backport potential tag i believe16:16
clarkbshould be in their git history16:17
dims_sdake : http://docs.openstack.org/developer/reno/usage.html16:17
dims_sdake : ^^ getting started tips16:17
sdakeclarkb agreed thanks16:17
sdakedims_ ya i read the docs, dhellmann and I had a conversation a few weeks ago about reno, and he mentioned he would hand-hold me through it :)16:18
sdakebut i guess i'll TBF16:18
*** SamYaple has joined #openstack-release16:18
dims_sdake :)16:18
*** inc0 has joined #openstack-release16:20
dims_sdake : one example from recent is trove (https://review.openstack.org/#/q/file:%255E.*releasenotes.*+project:openstack/trove)16:21
*** bswartz has quit IRC16:21
sdakedims_ thanks i'll copy that and cut&paste16:22
ttxsdake: you mean tracking on Launchpad ?16:23
sdakedims_ yu rock :)16:23
sdakettx right16:23
ttxsdake: yes, it's a pretty common question, because there is no perfect answer16:23
ttxoption 1, you create a mitaka series task and target the RC milestone16:24
dims_sdake : i just point to stuff, that's not hard work :)16:24
ttxthat lets you track the landing of the master patch in the main series16:24
ttx*if* you set the mitaka branch status to pre-release16:24
ttxand newton as the active development series16:24
*** sdake has quit IRC16:25
ttxmain drawback of this option is that only launchpad project drivers can create (or approve) series tasks16:25
ttxI think we lost sdake16:25
inc0I'll pass everything;)16:25
SamYaplettx: im still here16:25
inc0also logs are useful;)16:26
ttxoption 2, you use tags16:26
ttxoption 3, you use some etherpad to track backports16:26
SamYapleto be fair, we did discuss and were using option 1 before 2016 rolled around16:26
ttxthe way we did it when we handled that is a combination of option 1 and 216:27
ttxyou let people submit RC candidates using a tag16:27
inc0option 2 seems to be more lightweight16:27
ttxand you track what's approved to a RC using series tasks and milestones16:27
ttxit's a bit more intensive on the PTL /driver/ release liaison, but that's the only way to track it perfectly16:28
inc0ttx, that actually seems to be reasonable common ground16:28
ttxit's just a pain to set up due to LP getting in the way16:28
ttxhappy to help align the branch statuses and drivers teams so that you can do that16:28
*** sdake has joined #openstack-release16:29
inc0hey sdake read the logs16:29
ttx(funnily enough, LP has a concept of "release manager" but that person can't create series tasks either.)16:29
sdakettx apologies battery went to 0% :(16:29
sdakewill do16:29
inc0ttx suggested good common ground imho16:29
ttxyou have to be a driver to create series tasks (or approve the ones that were proposed)16:29
sdakettx ya we have alot of drivers - we let anyone in that team so they can target bugs and blueprints to themselves16:30
sdakei think we needt o change that aroudn a bit16:30
ttxagain, you need to set up your series status in launchpad so that it understands that master is now Newton, not Mitaka16:30
ttxotherwise you won't be able to create mitaka series tasks16:30
sdakettx let me read the logs once the bot catches up16:30
SamYaplei think we all agree both work. my only concern was single threading one person which tags seem like they might do16:30
ttxalright, let me know if you have additional questions16:30
SamYaplettx: the series was changed16:31
SamYaplebut now it seems to have reverted16:31
* ttx looks16:31
ttxon Kolla right16:31
SamYaplenot sure why its back at mitaka16:31
ttxI for sure didn't touch it :)16:31
* SamYaple pulls out the pitchforks16:32
sdakei changed he series to newton to see if that was what SamYaple was talkingabout16:33
ttxand goven Launchpad marvelous audit trail, you clearly won't be able to tell who did16:33
sdakebut then reverted that once i understood he was talking about something else16:33
sdakethe irc bot caught up16:34
SamYaplesdake: thats what i was talking about though16:34
SamYaplewell part of it16:34
sdakelet me experiment with whatyou proposed with 1 and 216:34
sdakewe dont want to use etherpad to track backports16:34
SamYapleright now new bugs filed will go against mitaka16:34
sdakeatleast I dont ;)16:34
SamYaplei think we can all agree to that :D16:34
sdakeok i'll change that back16:34
SamYaplettx: as always thanks for being a wealth of knowleges16:35
sdakeok that is changed16:35
sdakeya ttx knows everything and is always helpful resource :)16:35
ttxmore like a historic trove of old crufted best practices16:35
SamYaplealso that16:36
*** _amrith_ is now known as amrith16:36
sdakettx "In release freeze" ?16:37
sdakefor the status?16:38
sdakerather pre-release freeze16:38
sdakettx how do you make a series task?16:40
sdakeand you track what's approved to a RC using series tasks and milestones16:41
sdakehere is our tracker currently:16:41
ttxpre-release freeze sounds good once you cut RC1 and have a release branch16:42
sdakeyup we have done those things16:42
sdakeand we are tagging rc2 friday16:42
sdakeand rc3 april 2ndish16:42
ttxsdake: if you look at a bug you should be able to see "create series task" or something. Let me check16:43
ttx"Target to series"16:43
ttxthat lets you pick a branch name to create a series task16:43
ttxA bug in LP is a collection of BugTasks16:44
sdakeso like this https://bugs.launchpad.net/kolla/+bug/154023416:44
openstackLaunchpad bug 1540234 in kolla "rabbitmq cluster is not work" [Critical,Confirmed] - Assigned to weiyu (weiyu)16:44
ttxeach targeted to a series16:44
ttxthe complexity comes from the fact that there is a "default" series16:44
ttxwhich maps to the series which is in "active development"16:44
ttxand that is what the bug shows by default16:45
ttxeach task in a bug can have a different project and series16:45
ttxhttps://bugs.launchpad.net/kolla/+bug/1540234 looks good to me16:45
openstackLaunchpad bug 1540234 in kolla mitaka "rabbitmq cluster is not work" [Critical,Confirmed] - Assigned to weiyu (weiyu)16:45
sdakettx i've updated https://bugs.launchpad.net/kolla/+bug/1540234 with what I think is what you proposed16:45
sdakedoes that look correct?16:45
ttxyou got it :)16:46
sdakeok, SamYaple sound good?16:46
sdakeand we use tags as wel in this process16:46
sdakethe reason I want tags is so I can keep track of what has actually landed as a backport16:46
ttxtags let random users propose RC bugs, since they can't create series tasks16:46
*** dims_ has quit IRC16:46
ttxforces you to review the tagged bugs, but works around the lack of fine-grained perms in LP16:47
sdakeright - atm our drivers team has everyone and their sister ;)16:47
sdakemainly so folks can assign themselves bugs16:47
sdakebecause prior they couldnt' do so16:47
ttxit's probably fine too16:47
sdakeok, i'll bring it up as your proposal for how to manage bugs at our wednesday meeting16:48
sdakewith backports16:48
sdakeand if team in agreement i'll post instructions on the ml for the core reviewers who should be doing this work16:48
sdakei think the step we were missing is the "in freeze"16:49
sdakeand the agreement on the usage of rc tags16:50
sdakedo we remove the rc-backport-potential once the bug has been added as a task to mitaka-rc2?16:51
sdakettx ^16:52
*** pcaruana has quit IRC16:52
SamYaplesdake: yes that is exactly like what i think we should have16:52
ttxusually a a good idea yes, to avoid re-reviewing it16:52
sdakecool sounds good16:52
sdakei like it16:52
SamYaplesdake: thats what we talked about a few months back16:52
SamYaplecool im glad16:52
SamYaplei think its the clearest way16:52
sdakelets get the core reviewer team to buy in16:53
sdakeand we will make it so16:53
SamYaplei agree, last time we had this conversatoin in a meeting16:53
sdakeya I dont think it was at this depth though16:53
SamYaplei was not16:53
sdakeactually in prep for wednesday's meeting, I'll send out the full process as ttx has described it so peopel can read up16:54
sdakeand think about it for a day16:54
openstackgerritMatt Riedemann proposed openstack/releases: kilo: release python-openstackclient 1.0.5  https://review.openstack.org/29595416:58
*** kzaitsev_mb has joined #openstack-release16:58
ttxtaking a break before the meetings tunnel17:01
*** dims has joined #openstack-release17:02
openstackgerritFausto Marzi proposed openstack/releases: Add Freezer release meta for Mitaka-RC1  https://review.openstack.org/29596017:11
*** dims has quit IRC17:13
*** sdake_ has joined #openstack-release17:16
*** sdake has quit IRC17:16
openstackgerritJim Rollenhagen proposed openstack/releases: ironic-python-agent 1.0.2  https://review.openstack.org/29596517:20
*** bswartz has joined #openstack-release17:20
openstackgerritJim Rollenhagen proposed openstack/releases: ironic 4.2.3  https://review.openstack.org/29596617:21
*** daemontool has quit IRC17:22
*** amrith is now known as _amrith_17:24
*** mriedem1 has joined #openstack-release17:28
*** mriedem has quit IRC17:31
*** Kiall has quit IRC17:31
*** mriedem has joined #openstack-release17:31
*** mriedem has quit IRC17:32
*** mriedem has joined #openstack-release17:33
*** Kiall has joined #openstack-release17:33
*** mriedem1 has quit IRC17:33
*** daemontool has joined #openstack-release17:42
*** krotscheck has quit IRC17:43
*** pcaruana has joined #openstack-release17:44
openstackgerritFausto Marzi proposed openstack/releases: Add Freezer release meta for Mitaka-RC1  https://review.openstack.org/29596017:49
*** daemontool has quit IRC18:25
*** sdake_ is now known as sdake18:25
*** sigmavirus24 is now known as sigmavirus24_awa18:33
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to reset backport-potential tags once backports are merged  https://review.openstack.org/29599318:34
*** kzaitsev_mb has quit IRC19:03
*** inc0 has quit IRC19:04
*** kzaitsev_mb has joined #openstack-release19:42
ttxprecessing freezer rc119:43
*** sigmavirus24_awa is now known as sigmavirus2419:44
openstackgerritMerged openstack/releases: Add Freezer release meta for Mitaka-RC1  https://review.openstack.org/29596019:47
openstackgerritdevdatta-kulkarni proposed openstack/releases: Tagging Solum mitaka releases  https://review.openstack.org/29603219:50
openstackgerritJim Rollenhagen proposed openstack/releases: ironic 4.2.3  https://review.openstack.org/29596619:55
*** david-lyle_ has joined #openstack-release19:56
*** david-lyle has quit IRC19:57
*** jeblair has quit IRC19:58
*** jeblair has joined #openstack-release19:58
openstackgerritdevdatta-kulkarni proposed openstack/releases: Tagging Solum mitaka releases  https://review.openstack.org/29603220:00
*** david-lyle_ is now known as david-lyle20:02
*** kzaitsev_mb has quit IRC20:03
*** rockyg has joined #openstack-release20:07
*** sdague has quit IRC20:31
*** kzaitsev_mb has joined #openstack-release20:31
*** bdemers has quit IRC20:48
openstackgerritDouglas Mendizábal proposed openstack/releases: Release Barbican Mitaka RC1  https://review.openstack.org/29604520:53
openstackgerritJim Rollenhagen proposed openstack/releases: ironic 5.1.0  https://review.openstack.org/29604920:58
jrollttx: ^ ironic stable/mitaka release20:59
rockygdhellmann, you around?21:03
ttxjroll: hmm. Will probably process it tomorrow eu morning. So you still have time to update it in the coming hours if you want21:05
jrollttx: yeah, no rush, thanks21:05
rockygttx:  have some questions from the tricircle team for release21:10
*** dims has joined #openstack-release21:11
*** _amrith_ is now known as amrith21:11
* dims taking the con21:27
ttxrockyg: about to call it a day.21:27
ttxrockyg: email ? Tricircle is not official so I guess they do what they want21:28
*** TravT has joined #openstack-release21:28
dimsgood night ttx21:28
dimsi am back home from my day trip to boston21:28
rockygRight.  But they want to release and don't want to make waves.  As part of the ecosystem21:28
ttxdims: good presentation ?21:28
dimsttx : y. students from BU and North Eastern (joint presentation with Amrith)21:29
ttxrockyg: sure, send me some email and I can do free consulting :)21:29
* ttx disappears21:29
rockygSo, I suggested they follow the same rules as the projects by branching and announcing on ML and being specific they are not official.21:29
rockygWill do ttx  Thanks!21:29
openstackgerritMerged openstack/releases: kilo: release python-openstackclient 1.0.5  https://review.openstack.org/29595421:31
dimsmriedem : do you review ironic stable branch releases? https://review.openstack.org/#/c/295965/21:32
patchbotdims: patch 295965 - releases - ironic-python-agent 1.0.221:32
openstackgerritMerged openstack/releases: Release designate 1.0.2  https://review.openstack.org/29552721:32
mriedemdims: probably21:33
*** daemontool has joined #openstack-release21:41
openstackgerritMerged openstack/releases: ironic-python-agent 1.0.2  https://review.openstack.org/29596521:42
dimsmriedem : one more from jroll - https://review.openstack.org/#/c/295966/21:46
patchbotdims: patch 295966 - releases - ironic 4.2.321:46
mriedemgood lord bindep dumps a lot of info21:47
mriedemhave i complained about that yet to anyone?21:47
mriedembindep and zuul cloner21:47
dimsi've gotten used to zuul cloner...haven't had to look at bindep output yet :)21:48
*** openstackgerrit has quit IRC21:48
mriedemjroll: https://review.openstack.org/#/c/280072/ is a pretty shady backport21:48
patchbotmriedem: patch 280072 - ironic (stable/liberty) - Disable clean step 'reset_ilo' for iLO drivers by ... (MERGED)21:48
mriedemchanges a config option default value in a backport to stable21:48
mriedemkind of a no-no21:49
*** openstackgerrit has joined #openstack-release21:49
openstackgerritdevdatta-kulkarni proposed openstack/releases: Tagging Solum mitaka releases  https://review.openstack.org/29603221:51
mriedemdims: -1 on that one, i asked about a few changes, so will wait to see what the justification is for those on stable/liberty21:55
mriedemconfig option changes and dependency updates21:55
dimsmriedem : ack thanks!21:56
*** mriedem has quit IRC21:58
*** sigmavirus24 is now known as sigmavirus24_awa22:02
*** johnsom has quit IRC22:08
openstackgerritTravis Tripp proposed openstack/releases: Release Searchlight Mitaka RC1  https://review.openstack.org/29608922:18
*** gordc has quit IRC22:32
*** rockyg has quit IRC22:57
jrolldims: I replied to matt there but that could wait for tomorrow23:11
*** dims_ has joined #openstack-release23:12
*** dims has quit IRC23:15
*** dims has joined #openstack-release23:15
openstackgerritArmando Migliaccio proposed openstack/releases: Neutron Mitaka RC2 deliverables  https://review.openstack.org/29539823:17
*** dims_ has quit IRC23:18
*** dims_ has joined #openstack-release23:19
*** dims has quit IRC23:22
*** dims has joined #openstack-release23:23
*** dims_ has quit IRC23:25
*** kzaitsev_mb has quit IRC23:36
*** kzaitsev_mb has joined #openstack-release23:43
*** kzaitsev_mb has quit IRC23:54

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!