Tuesday, 2015-12-01

*** openstackstatus has quit IRC00:24
*** openstackstatus has joined #openstack-release00:26
*** ChanServ sets mode: +v openstackstatus00:26
*** mriedem_away is now known as mriedem00:42
*** mriedem has quit IRC01:13
*** openstackgerrit has quit IRC01:22
*** openstackgerrit has joined #openstack-release01:22
dimslifeless ping02:03
lifelessdims: pong02:07
dimslifeless in https://review.openstack.org/#/c/238871, the dups are already handled in extract_reqs02:08
dimslifeless : will fix the other two problems mentioned02:08
lifelessoh, I see02:09
lifelessdims: any chance of making the tests programmatic and putting them in tree?02:09
dimslifeless : i want to move code to openstack/requirements, once i get the logic correct, will add the tests there02:10
lifelessdims: ok02:10
lifelessdims: we really need a new project...02:10
lifelessdims: because you'll have to backport any code you move to openstack/requirements to liberty,kilo and juno atm02:11
lifeless(because the project-config job runs on all branches and it calls into openstack/requirements02:12
lifelessso, I looked at this previously and we share more code than we did in the past02:12
lifelessbut the branching etc stuff really is infra specific02:12
lifelessI'd be ok with just a manual script we run that will exercise things02:13
lifelessanything >> nothing02:13
dimslifeless : understood. updated with the last set of changes we talked about. talk to you tomorrow03:54
dimsgoing to get some zzzs03:54
*** amotoki has joined #openstack-release05:26
*** ifat_afek has joined #openstack-release05:45
openstackgerritChristian Berendt proposed openstack/releases: Release of openstackdocstheme 1.0.8  https://review.openstack.org/25164706:01
*** ifat_afek has quit IRC06:06
*** ifat_afek has joined #openstack-release06:06
*** dims has quit IRC06:09
*** dims has joined #openstack-release06:14
*** ifat_afek_ has joined #openstack-release06:27
*** ifat_afek has quit IRC06:30
openstackgerritChristian Berendt proposed openstack/releases: Release of openstackdocstheme 1.0.8  https://review.openstack.org/25164707:08
openstackgerritChristian Berendt proposed openstack/releases: Release of openstackdocstheme 1.2.5  https://review.openstack.org/25164707:18
*** dtantsur|afk is now known as dtantsur08:44
openstackgerritDmitry Tantsur proposed openstack/releases: Release python-ironic-inspector-client 1.3.0 for mitaka  https://review.openstack.org/25173409:32
openstackgerritSylvain Bauza proposed openstack/releases: [WIP] Release Nova 13.0.0 beta 1  https://review.openstack.org/25180511:29
*** flaper87 has quit IRC11:30
*** flaper87 has joined #openstack-release11:30
*** flaper87 has quit IRC11:39
*** flaper87 has joined #openstack-release11:47
*** flaper87 has quit IRC11:47
*** flaper87 has joined #openstack-release11:47
*** bdemers has quit IRC12:40
*** sileht has joined #openstack-release12:47
*** dtantsur is now known as dtantsur|brb13:09
*** gordc has joined #openstack-release13:15
*** stevemar has quit IRC13:22
gordcttx: is there a way to test whether my email's be blacklisted by openstack-dev mailing list? can't seem to receive/send emails from it anymore.13:22
*** stevemar_znc has joined #openstack-release13:23
*** ifat_afek_ has quit IRC13:40
ttxI don't think we have a blacklist system. Do you get any error ?13:51
gordcttx: nope. i just stopped receiving mail over the weekend... i tried unsubscribing and re-subscribing but i never get the re-subscribe confirmation email.13:58
ttxlet me check if anything looks funny on our side13:58
gordcttx: i'll check my mail settings again, it seems like openstack-dev is in my safe list.13:58
gordcttx: thanks13:58
*** bdemers has joined #openstack-release14:08
gordcttx: it's a microsoft thing. i can't register with my two microsoft accounts but i can with my gmail14:20
*** amotoki_ has joined #openstack-release14:24
*** mriedem has joined #openstack-release14:36
*** amotoki has quit IRC14:38
*** dtantsur|brb is now known as dtantsur14:43
openstackgerritSylvain Bauza proposed openstack/releases: [WIP] Release Nova 13.0.0 beta 1  https://review.openstack.org/25180514:43
smcginnisCan anyone tell me what I'm missing here?14:48
smcginnisFirst time releasing a client.14:48
smcginnisI set the depends-on flag, but it looks like the upper-constraint patch is failing not seeing the new client.14:49
smcginnisOr is it expected to fail until the new client lands and the depends on is just a safety?14:50
dhellmannsmcginnis : yes, it's just a safety14:50
smcginnisdhellmann: Great, thanks.14:51
smcginnisdhellmann: So I can just wait and recheck once the new client goes through, right?14:51
dhellmannsmcginnis : we had a lot of projects releasing and then never updating the constraints, so their new libs weren't actually being used, so we changed the process like this14:51
dhellmannyeah, after the release you just recheck and it should work then14:51
smcginnisdhellmann: Perfect. Thanks!14:52
dhellmannsmcginnis : np, thank you for helping out with this :-)14:52
smcginnisdhellmann: I'm learning. :)14:52
*** bauzas has joined #openstack-release14:54
bauzasI have a quick question for https://review.openstack.org/#/c/251805/14:55
bauzasdo I need to provide the SHA for the commit I provided or for the Jenkins merge patch for that one ?14:55
bauzasI guess the latter but I'd love some feedback14:56
bauzasttx: ^ ?14:56
ttxbauzas: checking14:58
ttxthe merge patch.14:58
bauzasttx: to be clear, the change just merged https://review.openstack.org/#/c/251805/14:58
ttxbauzas: otherwise we'd be tagging your branch14:59
bauzasttx: okay, that's what I thought14:59
ttxand not when it rejoined the HEAD14:59
bauzasttx: yeah, it's understandable14:59
openstackgerritSylvain Bauza proposed openstack/releases: Release Nova 13.0.0 beta 1  https://review.openstack.org/25180515:00
bauzasttx: thanks :)15:00
fungidhellmann: this is the time you wanted to talk about release automation next steps, yeah?15:01
dhellmannfungi : hi, yes!15:01
*** amotoki_ is now known as amotoki15:01
fungijust making sure our tz mappings agreed15:01
dhellmannfungi : I started making some notes in https://etherpad.openstack.org/p/mitaka-release-automation at the bottom15:01
dhellmannfungi : yeah, I'm in georgia, so I think we're the same tz unless you're travelling15:01
* fungi is _always_ in utc ;)15:02
dhellmannso the 2 main questions I had are there at the bottom of the etherpad: did I get the bug handling changes right, and what's our next step for the spec (assuming ttx likes this draft)15:02
fungiright-o, i haven't reviewed that spec yet15:02
dhellmannok, so that's probably the next step ;-)15:03
fungiyeah, i'm skimming as we speak15:04
fungihow far along is the centralize release tagging spec. should we consider that complete now?15:06
dhellmannyes, we've been doing all lib tagging using that process already and we'll be using it for mitaka milestone tags, too15:07
dhellmannwe retroactively added the tags for service projects for liberty after doing those manually15:07
dhellmannactually, this spec technically completes that work, so I'm not sure how you want count it15:08
fungijust checking. mind uploading an infra-specs change at some point to move it to the completed list in the index? no rush, just housekeeping15:08
*** dims has quit IRC15:08
dhellmannsure, I'll do that today15:08
fungithe series name mentioned in the proposed change section near the end of the third paragraph... this is basically derived from the branch?15:11
dhellmannso it's "mitaka" or "liberty"15:11
dhellmannthat's part of the deliverable path name in the releases repo, and is expected to match the stable branch if one exists15:11
dhellmannduring mitaka development we detect that there's no stable branch and don't indicate that the release is a stable release15:12
dhellmannafter the stable branch is included, the release announcements include a comment about it being a stable branch (or maybe it's just an extra tag in the email headers)15:12
fungileaving a note, but basically zuul doesn't know the branch of a tag (from a git perspective a tag can point to a commit which appears in multiple branches, though from the perspective of our automation there will generally only ever be one branch for a tag so we can make an educated guess and just plan to leave a safe fallback in case that assumption is occasionally incorrect)15:12
dhellmannthe logic we have in the scripts already works this stuff out, so I don't think we need zuul to do anything15:13
fungiokay, cool15:13
dhellmannas long as the workdir has the repo checked out to the new tag, we can do everything else from that point15:13
dhellmannif it doesn't, the announce script will need to somehow know what release to be announcing :-)15:14
fungiyeah, just curious what happens if the announce script finds the tag is in the history of multiple branches. but as you say, it's an implementation detail we don't need to work out in the spec itself15:15
dhellmannwhen a job runs after a tag is pushed, is the workdir for the project being tagged checked out to that tag point?15:16
fungie.g., 1. make stable/mitaka branch from head of master, 2. tag tip of stable/mitaka as 10.0.0, 3. release script sees tag is in the history of both stable/mitaka and master branches15:16
fungiyeah, the jobs in question generally checkout the tag by name15:17
dhellmannok, cool15:17
fungiso something has to reverse the tag to a branch or series name somewhere15:17
dhellmannthe announce script does something like $(git describe $(git describe $TAG^)) to determine the previous version15:17
dhellmannthe series name is part of the input to the process, so we just carry it through15:18
dhellmannthe release script adds it to the comment when tagging, and the announce script parses it back out15:18
fungioh, got it, so we don't guess at a series name it's already supplied separately15:18
dhellmannit's part of the deliverable filename in the releases repository15:18
dhellmannnow the validator there verifies that the commit being tagged is a descendant of the previous one in that series file, but that's before the tag is created15:19
dhellmannfungi : any other thoughts on the spec or those patches to change the bug handling behavior?15:24
fungii'm adding a few more comments in the review15:25
fungiokay, comments added, sorry for the delay15:31
fungithey don't substantially alter the spec itself though so it's safe to keep discussing next steps15:32
dhellmannno worries, thanks for doing the review15:32
flaper87dhellmann: hey, do you have 5 mins?15:33
flaper87It's re Glance's m-115:33
flaper87I'm targeting un-targeted bugs now15:33
dhellmannfungi : on the direct-release question, yes that's what I'm saying. see the 2 open reviews listed in https://etherpad.openstack.org/p/mitaka-release-automation15:33
flaper87(the ones w/ a patch merged)15:33
dhellmannflaper87 : you can do that, but it's no longer required15:34
flaper87I wanted to ask you what do you need from me to cut m-1?15:34
flaper87dhellmann: that was one of the questons15:34
* flaper87 goes and reads reno's docs15:34
dhellmannflaper87 : I sent an email to the list friday, let me find that link15:34
fungidhellmann: yep, i'm looking at those now. the question was more for the benefit of other reviewers15:34
dhellmannflaper87 : http://lists.openstack.org/pipermail/openstack-dev/2015-November/080692.html15:34
flaper87dhellmann: oh, nice. I wasn't around yday so it's probably on my backlog15:34
dhellmannfungi : ah, ok15:34
flaper87dhellmann: thank you15:34
dhellmannflaper87 : I figured as much, np15:34
mesterydhellmann: I had the same question as flaper87, but now I know what to do! Thanks to both you and flaper87! :P15:37
dhellmannfungi : it did turn out that there were a lot of edits to project-config, so changing the default seemed to make more sense. I'm not sure I've got that quite right now, though. I asked on the ML, and no project liaison said they wanted to stick with the current behavior, so even though I added a reverse option to jeepyb I didn't add it to any projects15:37
dhellmannmestery, flaper87 : if you have questions, please post them as follow ups to that email so everyone can see the answer15:37
flaper87dhellmann: sure thing :)15:38
mesterydhellmann: ++, looks clear to me, and I'm glad we got the reno stuff done in Neutron a few weeks back :)15:38
dhellmannmestery : ++, good work on landing that stuff early15:38
fungidhellmann: that seems reasonable15:38
dhellmannfungi : cool15:38
mesterydhellmann: Thanks for driving that with clear messages to the ML and help from you and andreas when needed :)15:39
fungidhellmann: my only related concern is downstream consumers of that hook in separate deployments (not openstack's) though i have a feeling there are few/none15:39
dhellmannfungi : yeah, I wasn't sure how to predict fallout from that :-/15:39
fungiso if other reviewers don't object then i'm okay15:39
dhellmannI'll add the depends-on and remove the WIP flag today, then15:40
fungiit looked like you already added the depends-on?15:41
dhellmannoh, so I did :-)15:41
dhellmannI'll fix the merge conflict instead ;-)15:41
*** bdemers has quit IRC15:43
fungiokay, i think i've looked through the outstanding proposed changes and also answered pertinent questions on the etherpad15:46
*** bdemers has joined #openstack-release15:46
dhellmannfungi : great, thanks. I'll add the item to the agenda for next week. And we can do announcements by hand for the time being, until we figure out the email solution.15:48
fungiyeah, if you wait until after this afternoon's infra meeting (20:00 utc or later should be safe) then it'll be less confusing15:49
dhellmannfungi : makes sense15:49
ttxdhellmann: quick Sphinx/RST question15:54
ttxdoesn't generate a link on line 815:54
ttxI'd like that to generate an internal link in the document15:54
*** dims has joined #openstack-release15:55
ttxAlso I'd like to put some links in bold, but **:ref:`foo`** doesn't do what I expect15:55
dhellmannttx: you're missing a - between 1 and milestone on line 815:58
ttxno damn that was silly15:59
dhellmannI don't think there's a way to wrap a link in bold like that, unfortunately15:59
ttxI wanted to single out cross-project events vs. project-specific ones15:59
dhellmannseparate columns?15:59
ttxcould use two columns, but that's slightly less practical to edit16:00
dhellmannttx: also, look at the list-table directive. way way easier to edit than this format16:00
ttxalso less room if we want to keep udner 80 cols16:00
ttxdhellmann: no way to have rowspan in list-table afaict16:00
dhellmannhmm, maybe true16:01
ttxso it makes listing multiple entries on a single week a bit inconvenient16:01
ttxoh well let's try that as a first step16:02
dhellmannI wonder if it would let you have a list in a cell16:02
dhellmannnot as nice as this, I guess16:02
dhellmannttx: we could also do something with the class directive and css to change the style16:03
*** wshao has joined #openstack-release16:04
*** dims_ has joined #openstack-release16:08
*** dims has quit IRC16:10
dims_dhellmann : any idea what gate-neutron-pep8-constraints is doing in requirements review? https://review.openstack.org/#/c/251088/16:10
dhellmanndims_ : none. ask infra?16:10
dims_ack thanks16:11
dhellmanndims_ : let me know what you find out? :-)16:11
*** kzaitsev_ws has quit IRC16:11
dims_yes of course, let me dig a bit before i ask16:11
*** kzaitsev_ws has joined #openstack-release16:13
dims_dhellmann : fyi https://review.openstack.org/#/c/251596/ got merged asking fungi on infra16:14
fungiyep, that's my bad. i didn't think it through. requirements will need integration tests more like what oslotest is (was?) doing16:20
dims_fungi : i have to dig it up, have not looked at oslotest in a while16:23
dhellmannfungi, dims_ : thanks for digging into that one16:26
*** dims has joined #openstack-release16:30
*** dims_ has quit IRC16:33
*** bswartz has quit IRC16:37
openstackgerritgordon chung proposed openstack/releases: python-ceilometerclient 2.1.0  https://review.openstack.org/25195416:38
openstackgerritKyle Mestery proposed openstack/releases: Mitaka-1 milestone for Neutron deliverables  https://review.openstack.org/25195916:45
openstackgerritThierry Carrez proposed openstack/releases: [WIP] Add Mitaka release schedule  https://review.openstack.org/25196416:48
ttxdhellmann: I need a preliminary review on the WIP to doublecheck I'm on the right track :)16:48
dhellmannttx: looking16:49
ttxdhellmann: also... should we track on the etherpad how many projects fail to submit mitaka-1 ? Or just let them fail ?16:49
dhellmannwe should probably keep track this time so we can push the liaisons harder next time16:50
mesteryCarrot and a stick, I like it dhellmann ttx :)16:50
ttxright. I'll list managed/cycle-with-milestones things on our etherpad16:50
ttxmestery: good cop, bad cop16:51
dhellmannttx: I was born to play bad copy16:51
dhellmanner, cop16:51
*** bdemers has quit IRC16:52
dhellmannttx: the schedule looks good. I wonder if it makes sense to have a /schedules subdir instead of including the file in /releases, but that's not a big deal either way16:52
ttxyeah, that can, be easily fixed afterwards16:52
ttxI just didn't want to continue adding stuff to a layout if you didn't like it16:53
ttxThe only drawback of this layout I think is the short space we have for columns. But since we want references there... it can be expanded to a long real title16:53
ttxIf I make dates smaller they wrap and look ugly16:54
*** amotoki has quit IRC16:55
openstackgerritMerged openstack-infra/release-tools: remove release_many.sh  https://review.openstack.org/25151016:57
openstackgerritMerged openstack-infra/release-tools: add more detail to the output  https://review.openstack.org/25156716:57
openstackgerritMerged openstack-infra/release-tools: catch more errors in external commands  https://review.openstack.org/25156816:57
openstackgerritMerged openstack-infra/release-tools: better formatting for command errors  https://review.openstack.org/25156916:57
*** mriedem is now known as mriedem_meeting16:58
*** wshao has quit IRC17:01
*** bdemers has joined #openstack-release17:01
ttxdhellmann: while I think about the automation... the first job is definitely deliverable-driven (one tag request for several repos, with add_comment fixing launchpad for all of them). The second job is more repository-driven (tarball generation). That may make it difficult to drive announcements from the same one.17:03
ttxi.e. you want announcements to be about the deliverable17:03
ttxwhile at that stage you have multiple tarball jobs running reacting to the tags we pushed from the deliverable-driven job17:04
ttxWe could push the announcement from the first job but we don't have tarballs yet. If we want to push announcement from the second one though, we need to somehow know when all the tarballs making up the deliverable are up17:05
*** dtantsur is now known as dtantsur|afk17:11
ttxdhellmann: ok, added lines to the etherpad. You can track reno support there as well if you want17:12
openstackgerritgordon chung proposed openstack/releases: ceilometer 5.1.0 - stable/liberty  https://review.openstack.org/25198217:15
openstackgerritSteve Martinelli proposed openstack/releases: release keystone managed libraries for mitaka-1  https://review.openstack.org/25052317:15
stevemar_zncdims: dhellmann: would love your input on https://review.openstack.org/#/c/250523/17:16
openstackgerritgordon chung proposed openstack/releases: ceilometer 2015.1.2 - stable/kilo  https://review.openstack.org/25198317:17
dhellmannstevemar_znc : on my list17:18
*** doug-fish has joined #openstack-release17:25
*** stevemar_znc is now known as stevemar17:25
dimsstevemar ack give me a few17:28
stevemarthank you both17:29
dimsah, releases, thought this was a review of code :)17:29
dimslooks like dhellmann already volunteered :)17:30
openstackgerritgordon chung proposed openstack/releases: ceilometer 2015.1.3 - stable/kilo  https://review.openstack.org/25198317:37
openstackgerritgordon chung proposed openstack/releases: ceilometerclient 1.1.2 - stable/kilo  https://review.openstack.org/25199217:40
openstackgerritgordon chung proposed openstack/releases: ceilometerclient 1.6.0 - stable/liberty  https://review.openstack.org/25199317:42
*** mriedem_meeting is now known as mriedem17:43
*** bswartz has joined #openstack-release17:43
*** mihgen has joined #openstack-release17:45
dimslifeless : dhellmann : another look please when you get a chance - project-requirements-change.py -https://review.openstack.org/#/c/238871/18:56
*** mriedem has quit IRC18:56
*** mriedem has joined #openstack-release19:01
*** patchbot has quit IRC19:03
openstackgerritFlavio Percoco proposed openstack/releases: Release Glance 12.0.0b1  https://review.openstack.org/25202319:08
*** patchbot has joined #openstack-release19:10
*** patchbot has quit IRC19:12
*** patchbot has joined #openstack-release19:13
flaper87dhellmann: I think I've done everything required on your email ^19:14
flaper87do let me know if I'm missing something! Thank you :)19:15
*** armax has quit IRC19:16
*** devananda has quit IRC19:33
*** devananda has joined #openstack-release19:47
*** armax has joined #openstack-release19:51
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: ensure virtualenv is created in toolsdir  https://review.openstack.org/25157019:53
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: factor out command to list deliverable changes  https://review.openstack.org/25157119:53
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: rewrite release_from_yaml.py as bash script  https://review.openstack.org/25157219:53
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add the series to the release tag  https://review.openstack.org/25157319:53
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add announce.sh to generate a release notes email  https://review.openstack.org/25157419:53
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: factor out command to list deliverable changes  https://review.openstack.org/25157119:58
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: rewrite release_from_yaml.py as bash script  https://review.openstack.org/25157219:58
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add the series to the release tag  https://review.openstack.org/25157319:58
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add announce.sh to generate a release notes email  https://review.openstack.org/25157419:58
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add the release metadata to the release tag  https://review.openstack.org/25157320:16
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add announce.sh to generate a release notes email  https://review.openstack.org/25157420:16
openstackgerritMerged openstack-infra/release-tools: ensure virtualenv is created in toolsdir  https://review.openstack.org/25157020:22
openstackgerritSteve Martinelli proposed openstack/releases: release keystone managed libraries for mitaka-1  https://review.openstack.org/25052320:36
dhellmannmestery : regarding the networking-* projects, why are those not release:cycle-with-intermediary or release:cycle-with-milestones?20:42
mesterydhellmann: I think they probably should be to be honest20:42
dhellmannmestery : ok, then rather than moving the deliverable files around do you want to talk to the neutron team about changing those tags?20:43
*** AJaeger has joined #openstack-release20:43
mesterydhellmann: That's an interesting idea, I'll do that by proposing hte patch to governance. Thanks!20:43
dhellmannmestery : ack, I left a comment on the patch, too20:44
mesterydhellmann: coolio :)20:44
AJaegerdhellmann: do you have time to release openstackdocstheme 1.25 today, please? https://review.openstack.org/#/c/251647/20:44
dhellmannAJaeger : I'm looking at releases right now, in fact20:44
stevemarAJaeger: get in line :P20:44
stevemardhellmann: the keystone libs patch is ready to go! hoping to get things released before it's too late in the week20:45
stevemar(yes i know you are reviewing releases now)20:45
dhellmannstevemar : :-)20:45
AJaegerstevemar: I will ;)20:48
AJaegerdhellmann: thanks!20:48
openstackgerritMerged openstack/releases: Release of openstackdocstheme 1.2.5  https://review.openstack.org/25164720:50
openstackgerritMerged openstack/releases: ceilometerclient 1.1.2 - stable/kilo  https://review.openstack.org/25199220:59
openstackgerritMerged openstack/releases: ironic-lib 0.5.0  https://review.openstack.org/25000021:04
openstackgerritgordon chung proposed openstack/releases: ceilometerclient 1.5.1 - stable/liberty  https://review.openstack.org/25199321:07
*** AJaeger has quit IRC21:09
stevemardhellmann: for stable/liberty and stable/kilo, are those now being released being openstack/releases?21:13
dhellmannstevemar : yes21:20
stevemardhellmann: is there a recommended schedule for when to release those things, or just whenever ptl decides? or when stable decides? i'm a bit unclear on that one21:20
dhellmannstevemar : you know, the stable folks may just be tagging service projects on some of the older stable branches21:22
dhellmannstevemar : stable/kilo is still synchronized. stable/liberty is not, so it's up to you to propose releases when you have "enough" patches built up.21:22
openstackgerritMerged openstack/releases: Release python-cinderclient 1.5.0  https://review.openstack.org/25153421:23
stevemarokay, i may tag a liberty release if we have enough patches there21:23
dhellmannstevemar : ++21:23
stevemardhellmann: one question about tagging bugs, should get tag them as mitaka-1 or leave the milestone untagged, that causes funniness in the client libs i noticed21:24
dhellmannstevemar : whether you target bugs is entirely up to you now. the release tool leaves a comment indicating when a fix was included in a release.21:26
stevemari rememberd that much21:26
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: rewrite release_from_yaml.py as bash script  https://review.openstack.org/25157221:31
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add the release metadata to the release tag  https://review.openstack.org/25157321:31
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add announce.sh to generate a release notes email  https://review.openstack.org/25157421:31
openstackgerritMerged openstack/releases: mitaka: release glance-store 0.10.0  https://review.openstack.org/24811921:37
openstackgerritMerged openstack/releases: release keystone managed libraries for mitaka-1  https://review.openstack.org/25052321:46
*** bswartz has quit IRC21:51
openstackgerritSteve Martinelli proposed openstack/releases: tag keystone for mitaka-1  https://review.openstack.org/25207621:54
openstackgerritSteve Martinelli proposed openstack/releases: tag keystone for mitaka-1  https://review.openstack.org/25207621:58
SergeyLukjanovdhellmann, hi!21:59
SergeyLukjanovcould I help you with handling lib releases?21:59
SergeyLukjanov(I'm in CA for the next 3 weeks)21:59
dhellmannSergeyLukjanov : great! we're in the middle of rewriting the release scripts, so you could start by reviewing those changes to become familiar with them. The spec is https://review.openstack.org/24590722:04
dhellmannttx: I used the draft versions of release.sh and announce.sh that are up for review now to do all of the library releases today. Everything seems to be working fine.22:05
dhellmannSergeyLukjanov : if you want to review release requests for milestone tags, that would be a big help, too22:06
ttxdhellmann: awesome22:06
gordcdhellmann: just curious about requirements upper-constraint patch for clients... is it just in case the automated job doesn't kick in?22:06
dhellmannttx: I realized that we might want a different version of announce.sh that checks out the repository, like release.sh does, but for now I just updated my local copies of repos and passed those directories to announce.sh22:07
dhellmanngordc : it's in part to educate everyone about how that process works, and also to provide a separate patch with just one constraint change so if it fails we can tell that it's because of that release, vs. having to debug all of the updates in the change from the bot22:08
* dhellmann makes a note to document the reasons for that better in the release instructions22:08
gordcdhellmann: ah, good point. yeah i didn't do it this time because i had to abandon all my previous requirements patch.22:10
gordci'll make the changes22:10
dhellmanngordc : yeah, if the bot patch passes we can approve that one and abandon the individual ones, but this way makes debugging easier if we have failures22:11
dhellmannif failures start becoming rare, we can change the process again22:11
gordcdhellmann: cool cool. understood.22:11
gordcdhellmann: if the liberty upper-contraint already covers https://review.openstack.org/#/c/251993/ . should i lower it to match liberty releases or keep it as is?22:17
gordcright now liberty upperscontraint is pointing at first relesae fro mitaka22:17
dhellmannwe have that in a few places, but I'm not sure how/why22:18
dhellmanngordc : the constraint is already higher than this release, then you don't need to make any changes22:18
gordcdhellmann: kk, i'll make a note in gerrit22:18
dhellmanngordc : ack. I'm done for the day, so I'll look at those releases first thing tomorrow22:19
gordcdhellmann: no problem. thanks!22:20
*** gordc has quit IRC22:24
stevemardhellmann: for the recent keystone library releases, it seems like those bugs associated with the projects in "fix committed" are no longer being auto-closed; i was expecting this for non-library projects, do i have to manually mark these bugs as fix-released for the libs?22:52
*** bdemers has quit IRC22:55
dhellmannstevemar : leave them for now; we'll bulk update them and I have patches up to change jeepyb to put them in fix-released automatically22:55
stevemardhellmann: rgr that22:55
stevemardhellmann: so i think we're almost all good to go for keystone mitaka-1, just the release notes to land, and i've proposed a release change22:55
stevemarthanks for helping out so much! :)22:56
stevemarwe've got reno everywhere including libraries22:56
dhellmannstevemar : http://lists.openstack.org/pipermail/openstack-dev/2015-November/080288.html22:57
dhellmannstevemar : \o/ for the reno work and for getting your milestone tag proposed!22:57
*** mriedem has quit IRC22:58
stevemar#success got reno in all keystone projects22:59
openstackstatusstevemar: Added success to Success page22:59
dhellmannstevemar : ++22:59
*** david-lyle has quit IRC23:25
*** dstanek has quit IRC23:41
*** dstanek has joined #openstack-release23:41

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