Tuesday, 2015-09-01

*** dims has quit IRC00:03
*** sigmavirus24_awa is now known as sigmavirus2401:00
*** dims has joined #openstack-relmgr-office01:20
*** sigmavirus24 has quit IRC03:48
*** sigmavirus24 has joined #openstack-relmgr-office03:51
*** sigmavirus24 is now known as sigmavirus24_awa03:59
*** dims has quit IRC04:30
openstackgerritJohn Dickinson proposed openstack/releases: Swfit 2.4.0 release  https://review.openstack.org/21911904:35
notmynamedhellmann: ttx: ^04:36
notmynameI think I did that right. please let me know if there is something else you need from me for that04:36
notmynameI've got an email ready to go when it's cut04:36
*** dims has joined #openstack-relmgr-office05:59
*** dims has quit IRC06:04
*** armax has quit IRC06:37
ttxnotmyname: will do that later tiday and you should be able to send that email when you get up07:27
*** aukhan has joined #openstack-relmgr-office07:29
ttxstarting office hours for those interested07:56
johnthetubaguyttx: happy to catch up07:57
ttxjohnthetubaguy: o/07:59
ttxlet me check what the script suggests08:00
johnthetubaguyso we have quite a few things that I am hoping we could wait a bit for08:01
ttxscript suggests nothing.08:03
ttxjohnthetubaguy: sure, what ?08:03
johnthetubaguyso this one has lots of patches that are close ish: https://blueprints.launchpad.net/nova/+spec/request-spec-object08:04
johnthetubaguyI added notes on the ones were I think we can let them go into the RC period, one of those is:08:04
johnthetubaguythis one I would like to give a chance (although its a long shot): https://blueprints.launchpad.net/nova/+spec/resource-objects08:10
ttxHow about you add the ones you'd like to try on the liberty-3 page ?08:10
ttxWe'll use the liberty-rc1 page to list the FFEs08:11
johnthetubaguysounds good08:11
ttx(and the critical release bugs list08:11
johnthetubaguyI just added two to the RC1 page08:11
johnthetubaguythey are both really non-blueprints08:11
johnthetubaguymore just for tracking08:11
ttxjohnthetubaguy: how about we look at where we stand tomorrow ? Status looks good so far08:12
johnthetubaguyyeah, that makes sense08:12
ttxso in summary:08:13
ttx- use liberty-3 to track things you'd like to wait for08:13
ttx- use liberty-rc1 to track FFEs and RC bugs08:13
johnthetubaguyI am thinking its likely to be a Thursday tagging at this point, thats my gut feeling08:13
johnthetubaguy+1 to those actions, doing that now ish08:13
ttx- RC1 will be tagged "when ready"08:14
ttx- stable branch will be cut before RC1, or when the pressure to unfreeze master is greater than the cost of backporting fixes08:14
johnthetubaguyOK, gotcha08:14
ttxboth are more your choice than ours08:15
ttxeven if we can help08:15
johnthetubaguyalways appreciate the help you folks give us all :)08:15
johnthetubaguyhonestly a bit part of me wonders about tagging before RC1, in the hope people get more used to helping with the stable branch, but its feels like a massive risk08:16
johnthetubaguy(and big overhead, if you get the timing wroing)08:16
ttxright, there are two factors in deciding when to cut the release branch (which will become the stable branch)08:16
ttxcost of backporting bugfixes vs. cost of freezing master08:17
ttxand forced community focus on bugs08:17
ttxSo if you have a giant list of RC bugs, better keep only one frozen branch08:18
johnthetubaguyyeah, makes sense08:18
ttxif you only have a couple of them left to fix, no need to freeze everyone else08:18
ttxanyway, will talk again tomorrow08:18
johnthetubaguysounds good, catch you similar time tommorw08:19
johnthetubaguythank you!08:19
ttxKiall, flaper87: I'm around in case you want to sync your liberty-3 status08:20
ttxSergeyLukjanov: same08:20
ttxstevebaker: still around?08:20
openstackgerritMerged openstack/releases: Handle errors from git describe  https://review.openstack.org/21889208:31
flaper87ttx: thanks, I'm waiting for some patches to land before we can cut l-308:33
ttxflaper87: let me look at the sate of the zaqar page08:34
ttxnot much to change, are you still expecting persisten-transport to fully land ?08:35
ttxAlso we'll defer bugs when we tag08:35
flaper87yes, persistent transport is the one and there's another one that should be there but if it's not, I'll add it08:37
flaper87I'll ping you later today/tomorrow08:37
ttxit's not there, so yes, please add it08:37
ttxok We'll sync again later today/tomorrow08:38
*** dims has joined #openstack-relmgr-office08:42
*** katyafervent is now known as katyafervent_awa08:47
*** dims has quit IRC08:48
ttxKiall, SergeyLukjanov: around ?08:49
*** katyafervent_awa is now known as katyafervent08:51
stevebakerttx: can we sync in ~10 hours?09:56
ttxstevebaker: yes, can do after the TC meeting (at 21:00 utc, while the cross-project meeting runs)09:57
ttx(or dhellmann will be able to pick it up later)09:57
stevebakerttx: ok, sounds good.09:57
*** dims has joined #openstack-relmgr-office10:30
*** dims has quit IRC10:36
*** aukhan has quit IRC11:03
*** dims has joined #openstack-relmgr-office11:25
*** dims has quit IRC11:29
ttxdhellmann: trying to see how much of release_postversion.sh I can use to do the swift release11:48
openstackgerritThierry Carrez proposed openstack/releases: Swift 2.4.0 release  https://review.openstack.org/21911911:49
dhellmannttx: IIRC, it worked for ironic's release, but there may be slight differences12:21
ttxyeah, mostly things it doesn't do (like uploading the tarball) and things it does not need to do (like a release notes email)12:21
ttxso I ended up writing an intermediary.sh to match what I needed it to do12:22
ttxwe'll likely have to make them converge12:22
openstackgerritMerged openstack/releases: Swift 2.4.0 release  https://review.openstack.org/21911912:23
ttxwe should sit at the summit and devise the big plan for refactoring those tools12:23
ttxbecause it feels like we keep adding specialty scripts :)12:23
*** dims has joined #openstack-relmgr-office12:33
dhellmannheh, yeah12:33
dhellmannI have a branch started to convert the post version script to python, to make it easier to deal with the yaml file (multiple repos for one deliverable, etc.) and so we only have to provide the keyring password once12:34
dhellmannI'm trying to do that conversion in a way that will make it easy to recompose the results into new tools12:35
ttxnotmyname: 2.4.0 tagged, ready for your announce @ https://launchpad.net/swift/liberty/2.4.012:46
*** sigmavirus24_awa is now known as sigmavirus2412:51
ttxdhellmann: one thing we haven't discussed yesterday is how many release management slots we should request12:53
ttxwe had one fishbowl and one workroom last time12:53
ttxwe used the fishbowl for the stable discussion12:53
ttxmaybe same ?12:54
dhellmannso the outside session was the working session? that felt more useful13:04
ttxthe outside session was during the meetup I think13:04
dhellmannoh, right13:04
dhellmannwhat was the working session, then?13:04
ttxIt was a session on library releases13:11
ttxI would propose one about communicating upcoming changes for mitaka (fishbowl)13:11
ttxand one about coming up with a plan (workroom)13:12
ttxwe can use the meetup to start working on refactoring the tools13:12
ttxwe can do stable and not stable in parallel, separating them has done us no good in the past13:12
ttxyou'll be around Friday afternoon ? we could have a meetup then13:14
dhellmannyeah, I'm not leaving until saturday evening13:14
ttxFriday afternoon meetup rooms are not very expensive13:14
dhellmannthere's one direct flight in and out of atlanta each day, and I didn't want to leave in the middle of the day friday13:15
ttxHah, some projects have requested more slots than there is hours in the day13:15
dhellmannmaybe we can mix the retrospective I proposed in https://etherpad.openstack.org/p/mitaka-summit-release-track-topic-planning with the mitaka preview session13:15
*** sigmavirus24 is now known as sigmavirus24_awa13:24
openstackgerritThierry Carrez proposed openstack-infra/release-tools: Script to release cycle-with-intermediary  https://review.openstack.org/21927413:26
ttxKiall, SergeyLukjanov, nikhil_k, redrobot: ping me when you have 5 minutes to sync13:27
nikhil_kttx: hi13:36
ttxnikhil_k: ohai13:37
ttxfeels empty blueprint-wise, let me see if the script finds something to add13:37
ttxnope... Any blueprint that was finished that should be added there ?13:38
ttxnikhil_k: anything to wait on before tagging ?13:38
*** sigmavirus24_awa is now known as sigmavirus2413:39
nikhil_kttx: I was hoping to tag later in the week13:39
nikhil_kttx: there are a couple BPs that are sitting on minor nits13:40
nikhil_kttx: Also, I think there's some work on artifacts that isn't tagged on the BP page13:40
ttxnikhil_k: sure, we don't have to do that today. It's just unclear from the l3 page which things you are waiting on13:40
nikhil_kttx: want ensure we have everything up there13:40
ttxnikhil_k: maybe target the things you'd like to try to get in to liberty-3 so that they show up on our radar too13:40
nikhil_kttx: I will do that today13:40
ttxnikhil_k: cool, thx. We'll talk again tomorrow when progress has been made and the page is more complete13:41
nikhil_kttx: sounds good, thanks.13:41
nikhil_kttx: same time tomorrow?13:41
nikhil_kttx: ok, thanks/=.13:43
nikhil_kttx: any way your script can tag bugs for l3 that are already merged? I want to check if we have people assigned on duplicates or not before pinging everyone13:48
nikhil_kby l3 I meant HEAD on master13:48
nikhil_kjust curious13:49
ttxah, you mean, targeting fixcommitted bugs to the milestone ? Yes, I should be able to do that13:49
*** gordc has joined #openstack-relmgr-office13:52
nikhil_kttx: thanks!13:52
ttxnikhil_k: done13:54
nikhil_kttx: appreciate it13:59
openstackgerritMatt Riedemann proposed openstack/releases: Release python-novaclient 2.27.0  https://review.openstack.org/21928313:59
openstackgerritMerged openstack-infra/release-tools: clarify duties in library release process  https://review.openstack.org/21901714:10
*** bswartz has joined #openstack-relmgr-office14:17
ttxbswartz: o/14:17
bswartzttx: sorry it took so long to get here14:17
bswartzI had meetings....14:17
bswartzoh you have the link already14:17
bswartzthis is accurate14:17
ttxLet's see what the script suggests if anything14:17
ttxok, nothing relevant14:18
ttxSo you would like to try to sneak as much as you can on those "needs code review" blueprints ?14:18
bswartzwe're targeting L-3 for Thursday at this point14:19
ttxand maybe grant some feature freeze exception to the ones that won't make it, if any ?14:19
ttx(if they are really close)14:19
bswartzmost of those will merge before Thursday I think14:19
ttxok. How about we talk again on Thursday then14:19
ttxbswartz: Keep the list current with what you're waiting on14:19
bswartzI'm telling people anything not merged by Thursday UTC 1500 will need an FFE and we'll hold core team votes during our weekly meeting on those14:19
ttxyou can use https://launchpad.net/manila/+milestone/liberty-rc1 to list blueprints where you garnd a feature freeze exception14:20
ttx(and release-critical bugs obviously)14:20
bswartzare we using the new release process to create milestones now?14:20
ttxbswartz: not yet for RCs14:21
ttxor betas14:21
bswartzthat tree14:21
ttxwe'll still use a manula hand-of for the .0b3 tag14:21
bswartzI give you the commit hash and you push the tag?14:21
ttx(or dhellmann if I'm not around14:22
bswartzyeah then I'll be talking to you again in 48 hours14:22
ttxwe'll certainly use the repository for the final signoff14:22
bswartz48 hours should get most of those remaining BPs merged14:22
ttxand maybe for the RCs, still under discussion14:22
ttxso let's talk again on Thursday around this time14:22
bswartzor maybe even all of them!14:22
bswartzsounds good14:22
openstackgerritMerged openstack/releases: Add initial ironic-lib release  https://review.openstack.org/21898514:37
*** TravT_ has joined #openstack-relmgr-office14:48
*** TravT has quit IRC14:50
*** armax has joined #openstack-relmgr-office14:53
*** TravT_ is now known as TravT15:07
SergeyLukjanovttx, hi!15:07
SergeyLukjanovttx, can we sync now?15:07
ttxSergeyLukjanov: I'm on a call, maybe dhellmann can sync with you, otherwise, in ~30min15:08
SergeyLukjanovdhellmann, morning15:08
SergeyLukjanovI'll be here for ~1.5 hours15:08
dhellmannSergeyLukjanov: I'm here15:12
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: don't assume we will get an existing tag  https://review.openstack.org/21930815:12
SergeyLukjanovdhellmann, Id like15:12
SergeyLukjanovdhellmann, I'd like to sync re L3 and client release15:13
dhellmannSergeyLukjanov: ok, let's look at https://launchpad.net/sahara/+milestone/liberty-3 first15:13
SergeyLukjanovso, I think we'll be ready for client release later today15:13
SergeyLukjanovand L3 at thu15:13
SergeyLukjanovdhellmann, blueprint a bit outdated15:13
dhellmannthere are quite a few items on that milestone page that are incomplete, are any of them blockers?15:14
SergeyLukjanovI need to find another place with internet, will be back in 10 mins15:15
dhellmannSergeyLukjanov: ok15:15
*** dims has quit IRC15:17
ttxSergeyLukjanov: i'm back too, for ~20min15:42
SergeyLukjanovI'm back15:52
SergeyLukjanovsorry folks, the hotel internet connection is extremey bad15:52
SergeyLukjanovttx, dhellmann, for the sahara l3 we'd like the following blueprints merged15:52
*** vikram has joined #openstack-relmgr-office15:53
vikramdhellmann: hi15:53
SergeyLukjanovso, I'm proposing to make a L3 Wednesday evening and request FFE for the rest of blueprints15:53
SergeyLukjanovhopefully we'll be able to merge most of them till this time15:54
notmynamettx: thanks15:54
dhellmannvikram: hi, let me finish helping SergeyLukjanov15:54
vikramdhellmann: no worries15:54
ttxnotmyname: I haven't announced it, so feel free to fire your email asap15:54
dhellmannSergeyLukjanov: if you update your launchpad page for l3 to only include the blueprints you actually want to be blocking the tag, that will help us keep track of when you're ready15:54
notmynamettx: ok. I'll do that shortly15:54
SergeyLukjanovdhellmann, ack, will do15:55
notmynamettx: also, will respond about session slots via email15:55
dhellmannSergeyLukjanov: FFE is up to you to manage within the project, so you can add anything you want to consider for that to the rc1 milestone15:55
ttxnotmyname: read all the replies, I fumbled my counts15:55
SergeyLukjanovdhellmann, so, it's no more needed to discuss FFE with release team?15:55
dhellmannSergeyLukjanov: we only care about what's blocking a given milestone or release, it's up to each team to decide what those things are. We can give you advice if you want it, on each case.15:56
dhellmannSergeyLukjanov: keep in mind that everything you grant an exception for prevents a part of your team from focusing on bug fixes, so you want to balance those 2 duties15:57
SergeyLukjanovdhellmann, yes, sure, I remember about it15:57
dhellmannyep, it's on my checklist to remind you :-)15:58
dhellmannSergeyLukjanov: there are quite a few bugs on the liberty-3 milestone page, too, are any of those blockers for this week's tag?15:59
SergeyLukjanovdhellmann, thx :) that's always better to have reminder than not :015:59
SergeyLukjanovdhellmann, I've updated blueprints for https://launchpad.net/sahara/+milestone/liberty-3 and now looking on bugs15:59
notmynamettx: announce email sent16:00
ttxand approved16:00
SergeyLukjanovdhellmann, nothing important enough to block the L316:02
dhellmannSergeyLukjanov: ok, I can use the script to untarget the bugs16:02
SergeyLukjanovdhellmann, no worries, I'll do it by myself16:03
dhellmannSergeyLukjanov: ok, if you'd rather that's fine16:04
SergeyLukjanovwhat will be the l3 process this time?16:04
dhellmannSergeyLukjanov: https://wiki.openstack.org/wiki/Release_Cycle_Management/Milestone_Checklist16:04
dhellmannlargely the same as last time, except for considering how to handle RC116:04
*** dims has joined #openstack-relmgr-office16:05
SergeyLukjanovdhellmann, ack16:05
SergeyLukjanovdhellmann, should I share the SHA of the commit I think should be tagged or CR to openstack/releases?16:06
dhellmannfor the milestone you can just give me the sha when you're ready16:06
ttxdhellmann: I'm pausing for a couple hours before the meeting. I didn't touch base with that many people during my day, so we have a backlog now. I'll try to pick up a few before/after meeting tonight16:06
dhellmannttx: ack, I'll try to hit as many as I can, too16:06
ttxMissed Kiall, gordc, redrobot in the Central->EMEA zones16:07
SergeyLukjanovdhellmann, ack, are you ok with tagging tomorrow evening?16:07
dhellmannSergeyLukjanov: since we don't have a set date for RC1, and we cut the stable branch at the same time, we need to consider how to balance the length of time we freeze master for new features against the amount of work it is to backport bug fixes. We would like to cut RC1 before the end of September, but doing it too soon means potentially more backports.16:07
dhellmannSergeyLukjanov: sure, and if I'm not available ttx or I can tag L3 early Thursday16:08
SergeyLukjanovdhellmann, cool, thx16:08
SergeyLukjanovdhellmann, yeah, it's very tricky....16:08
SergeyLukjanovIMO there should be at least two full weeks after freeze16:08
*** jgriffith has joined #openstack-relmgr-office16:10
*** dolphm has joined #openstack-relmgr-office16:20
notmynamettx: so if I understand you correctly, there are 8 slots each day on wednesday and thursday. right?16:24
notmynamettx: and those are the "normal" 50 min slots?16:25
openstackgerritSergey Lukjanov proposed openstack/releases: Release liberty "official" python-saharaclient 0.11.0  https://review.openstack.org/21934416:42
SergeyLukjanovdhellmann, actually we have a client done already16:43
*** david-ly_ has joined #openstack-relmgr-office16:49
*** david-lyle has quit IRC16:49
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Oslo Releases for Sep 1, 2015  https://review.openstack.org/21936217:06
*** david-ly_ has quit IRC17:07
dhellmannSergeyLukjanov: ok, I'll cut that client release for you17:09
SergeyLukjanovdhellmann, thank you very much!17:10
SergeyLukjanovdhellmann, heh, it's my first vacation with so bad internet ;)17:10
dhellmannvikram: sorry for the delay, how can I help?17:10
openstackgerritMerged openstack/releases: Release liberty "official" python-saharaclient 0.11.0  https://review.openstack.org/21934417:12
dimsdhellmann: need to push 3 libs out which have code changes (https://review.openstack.org/219362) - i can take care of it if it looks good to you17:20
dhellmanndims: +217:29
vikramdhellmann: I want to make a release for a new repo "networking-onos"17:31
vikramWant to understand how it can be done17:31
dhellmannvikram: ok, good17:31
dhellmannat the lowest level the thing that triggers a release is pushing a gpg-signed tag to the gerrit repo17:31
dhellmannyou can do that directly, or you can use our release tool scripts, which also record the release in launchpad17:32
dhellmanndoes the project have its own launchpad page?17:32
vikramis it documented some where?17:32
SlickNikdhellmann / ttx: let me know when's a good time for a quick sync?17:32
dhellmannSlickNik: give me just a few minutes to finish helping vikram and then we can sync up17:32
SlickNikdhellmann: Awesome — I'm around just ping when ready. Thanks!17:33
dhellmannvikram: ok, good. The release tools are documented in http://git.openstack.org/cgit/openstack-infra/release-tools/tree/README.rst17:33
dhellmannvikram: there's a section down at the bottom of that file that explains the basic process17:33
vikramdhellmann: ok let me go through that17:34
dhellmannvikram: the 2 parts that usually trip folks up are setting up the gpg key to sign the tag, and authenticating with launchpad17:34
vikramdhellmann: Ok.. One more query, how the release of the sub-project is done with the official release?17:35
vikramdhellmann: Let's say liberty-3 release for neutron will also do the release of big tent projects? or I need to follow the process as you have mentioned and release of my own?17:36
dhellmannvikram: your project uses the "release:independent" model, so that means the release team won't be doing the release work for you. I can help you get set up, but we only directly release the "release:managed" projects17:37
dhellmannvikram: if you have questions, dims, lifeless, ttx, and I should all be able to help answer them in this channel17:37
vikramdhellmann: thanks a lot dhellmann..17:37
dhellmannvikram: sure thing, let me know if you have questions after you've had a chance to review the procedures17:38
vikramdhellmann: let me go through the README.rst ..17:38
vikramdhellmann: thanks for your help & guidance17:38
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add launchpad-login command  https://review.openstack.org/21937717:44
dhellmannvikram: ^^ may help you set up your launchpad credentials17:44
dhellmannSlickNik: ok, I'm ready if you are17:45
gordcttx: dhellmann: just an fyi, i'm waiting on reviews for 3 bps. one is a single patch remaining, one is partially merged, and the last one is up for review but may need a FFE.17:45
dhellmanngordc: sounds good. If you update your liberty-3 milestone page to reflect that, you'll be all set when they're merged and you're ready to tag17:45
vikramdhellmann: sure17:45
gordcdhellmann: cool cool. thanks17:46
SlickNikdhellmann: Thanks — just wanted to touch base regarding https://launchpad.net/trove/+milestone/liberty-317:46
dhellmannSlickNik: yep17:46
SlickNikStill have a few BPs in various stages of undergoing CR or merging.17:47
SlickNikThere's a couple I'm going to have to punt to Mitaka since I don't believe we'll be able to make enough progress on them for Liberty.17:48
SlickNikAnd I'm probably going to need to FFE at least 1 (maybe 2).17:48
dhellmannSlickNik: ok, at this point you should move the FFE item(s) to the rc1 milestone, and move anything else out of L3 that you aren't considering a blocker17:49
SlickNikI plan to have all of this cleaned up and ready to tag by Thursday.17:49
dhellmannthis is what our script would do automatically: http://paste.openstack.org/show/438263/17:49
SlickNikdhellmann: In the process of having conversations with folks before I do just that :)17:49
dhellmannsounds good17:49
dhellmannSlickNik: I have a couple of other reminders:17:50
dhellmannit sounds like you have the FFE thing under control, but keep in mind that every FFE prevents the team from focusing on bug work so you want to minimize those17:50
dhellmannit's up to you to manage them, but we can advise if you want to talk about specific cases17:50
dhellmannbecause there's no "date" for RC1, we can cut that for you whenever you consider it ready. Keep in mind that we cut the stable branch at the same time, and so from that point on bug fixes need to be backported.17:51
dhellmannthat means that although we want to tag RC1 by the end of September, we also want to balance doing that early (to unblock feature work in master) with the effort to handle the backports17:51
dhellmannSlickNik: that's it from me, did you have anything else you wanted to bring up?17:52
SlickNikdhellmann: ++ on the FFE advice — I completely concur and will strive to keep it to a minimum.17:52
SlickNikOne thing I'm going to do after the L3 cut is identify the must fix bugs and blockers — I suspect that after these are fixed (+ a little bit of bake time) we should be able to cut RC1.17:53
dhellmannSlickNik: sounds good, this is all just reminders :-)17:53
*** david-lyle has joined #openstack-relmgr-office17:54
SlickNikroger that :)17:54
dhellmannyou can use the rc1 milestone to track those17:54
*** sigmavirus24 is now known as sigmavirus24_awa17:54
SlickNikyup, I see that now.17:55
SlickNikThat's pretty much all I had. Thanks much! :)17:55
dhellmannSlickNik: great, thanks for checking in and, as usual, let us know if we can help between now and tag-day17:55
SlickNikwill do — as an aside, I'm going to be on a plane most of Wednesday, so if anything Trove related does come up in my absence feel free to contact either cp16net or amrith17:57
SlickNikhopefully nothing will, but just in case.17:57
*** david-lyle has quit IRC18:01
dhellmannSlickNik: thanks for the heads-up, I'll make a note18:02
dhellmannKiall, redrobot, armax, dougwig, stevebaker : let me know if you have time to sync up for the milestone18:04
armaxdhellmann: here18:05
dhellmannhi, armax18:05
armaxdhellmann: we still have a few patches in the gate18:05
dhellmannlooking over https://launchpad.net/neutron/+milestone/liberty-3 I see there are several open blueprints and bugs -- are all of those blockers?18:05
armaxdhellmann: I have been cleaning this up18:05
dhellmannok, good18:06
dhellmannjust to make sure you saw it, ttx created a rc1 milestone that you can use for things you expect to need to treat as a FFE18:06
armaxdhellmann: I am thinking we would need at least today to clean this up even further18:06
armaxdhellmann: in a way that stuff will move to rc118:06
dhellmannyou can just remove the target milestone from anything you aren't going to block on18:06
armaxdhellmann: I am new to this process though, is that ok? Or do I need to be more aggressive?18:06
dhellmannok, sounds good18:07
armaxdhellmann: I can be more aggressive :)18:07
dhellmannwe want to tag by thursday, so if you want to check back in tomorrow that would be good18:07
armaxdhellmann: ok will do.18:07
dougwigarmax: the pecan bp can be pushed to M.18:07
dhellmannok, good, I will be out early in the day but expect to be online by this time of day again18:07
armaxdhellmann: ok cool18:07
armaxdougwig: we were going to merge it back to master18:08
armaxdougwig: no?18:08
dougwigarmax: i think that bp is done when pecan is the server, which will not be in L.18:08
dhellmannjgriffith: let me know when you have a few minutes to sync up for l318:15
*** david-lyle has joined #openstack-relmgr-office18:19
Kialldhellmann: heh, IRC on my desktop stopped notifying me of mentions it seems. On my way home, tomorrow?18:20
dhellmannKiall: sure thing, drop by here when you have some time18:20
jgriffithdhellmann: ready when you have an open slot18:21
dhellmannjgriffith: let's do it18:21
jgriffithdhellmann: cool18:21
dhellmannlooking at https://launchpad.net/cinder/+milestone/liberty-3 I see some blueprints and bugs still open, are those all blockers?18:22
jgriffithdhellmann: no18:22
jgriffithdhellmann: not blockers18:22
dhellmannok, good18:22
jgriffithdhellmann: I don't think I'm going to let anything block at this point18:22
dhellmannso there are a couple of ways to update that list18:22
dhellmannI can run the scripts to untarget everything that is open18:22
dhellmannor we can do it by hand if you have a couple of items to keep18:22
dhellmanndo you need to move any of those to the rc1 milestone as FFEs?18:22
jgriffithdhellmann: I think by hand... I'm trying to decide which to keep (take it to the very last minute) :)18:23
dhellmannsure, that's fine18:23
jgriffithdhellmann: so that's what I'm considering today... as well as possibly a few of the low priority ones I bumped already18:23
jgriffithdhellmann: so I'm struggling with one inparticular, perhaps you could provide your input :)18:23
dhellmannI can try18:23
jgriffithdhellmann: object versioning for volumes18:24
jgriffithdhellmann: HUGE patch (1500 lines)18:24
dhellmannyeah, that sounds, just from the description, like a large architectural change to be making this late18:24
jgriffithbut if it slips again, that's n+1 before cinder finally gets rolling upgrades18:24
jgriffithyeah... on the surface I said no way18:24
jgriffithyeah, I know the right answer here... just trying to figure out if I can convince myself otherwise :)18:25
jgriffithanyway... other than that...18:25
jgriffithI'd like to stretch this out til tomorrow evening if possible?18:25
jgriffithdhellmann: do the cinder weekly meeting at 16:00 tomorow make sure everything looks ok, then roll with it18:26
jgriffithdhellmann: that work?18:26
dhellmannyeah, I'll make a note that you'll check in with us tomorrow18:26
jgriffithOk, perfect18:26
jgriffithThat's about all I have...  only other question was on client side18:26
jgriffithI'm assuming that's part of dependency freeze and release team?18:27
dhellmannwe can do a client release whenever you're ready18:27
jgriffithdhellmann: Ok, I'll poke at that today and make sure it's *ready*ish18:27
dhellmannyeah, I think we'll be making some exceptions for our own libs18:27
dhellmannjgriffith: sounds good. Are you familiar with the new process for that?18:27
jgriffithdhellmann: ok, that answer my question on that18:27
jgriffithdhellmann: not completely no :(18:27
dhellmannok, it's not hard -- have a look at the openstack/releases repository. In the deliverables directory, you'll find $SERIES/$PROJECT.yaml files18:28
dhellmannthe readme should explain what to do, but I'm available to answer questions as well18:28
jgriffithdhellmann: sounds good, sure I can fumble through it18:28
dhellmannbasically you need to tell us a version number and a sha18:28
jgriffithif not I'll shout18:28
jgriffithdhellmann: ahh... ok, ez enough18:28
dhellmanndims and lifeless both know that process, too, if I'm not online18:28
jgriffithI think that's about all I've got then18:29
dhellmannok, great, thanks!18:29
jgriffithdhellmann: thanks to you!18:29
jgriffithcya in a bit18:29
*** vikram has quit IRC18:30
*** dims has quit IRC18:40
redrobotdhellmann hello!18:42
redrobotdhellmann I'm hoping we can wait to tag Barbican until Thursday18:42
dhellmannredrobot:yep, just wanted to sync up on where things stand before then18:44
dhellmannredrobot: for example, https://launchpad.net/barbican/+milestone/liberty-3 is looking pretty empty18:45
redrobotdhellmann yeah... I need to spend some time cleaning that up and targeting bugs/specs18:45
redrobotdhellmann it's currently not accurate18:46
*** HenryG has joined #openstack-relmgr-office18:46
*** bdemers has joined #openstack-relmgr-office18:49
bdemersto request a new release via the _new_ process, all i need to do is create a yaml file for a given project name, similar to what was done here: https://review.openstack.org/#/c/217766/ ?18:49
bdemersand are the releases cut automaticly once it gets merged ?18:49
dhellmannbdemers: which project?18:50
dhellmannbdemers: that repo is currently only being used for managed projects18:50
bdemersit doesn’t have an entry yet, i can add one, but want to make sure i’m doing the right thing first18:51
dhellmannbdemers: that project is listed as release:independent, so you would not request a release through the releases repository18:52
dhellmannyou, or someone else on the release team for the project, can tag the release directly18:52
dhellmannif you have a launchpad page set up for the project, you can use the tools in the openstack-infra/release-tools repository18:52
dhellmannthere's a README there that explains how to use the tools, and we can help you if you have questions from there18:53
bdemersdhellmann: is it advantageous for us to use openstack/release instead ?18:56
bdemersit seems like openstack/release is the way forward? though, i’m slightly more confused now then before i started asking about this :D18:57
dhellmannbdemers: I don't think it's really an option for your project at this point18:57
dhellmannwhen we have the release process fully automated, we may open it up to unmanaged projects, but for now we're still doing the releases by hand ourselves18:58
bdemerswhat makes a project not independent ?18:59
*** jhesketh has quit IRC18:59
dhellmannthe project asks for it, and we agree to take on the work. We've not done that yet for the neutron extension projects.18:59
dhellmannthere are just too many of you, frankly, for us to do that until we have more automation in place.19:00
bdemersok, so does openstack/release just wrap the openstack-infra/release-tools bits ?19:00
dhellmannand the automation isn't complete, so part of the wrapper is a member of the release team :-)19:01
bdemersok, so I _should_ be able to hack on this then ?19:01
bdemerswhere does the current automation start/stop19:01
bdemersor have holes ?19:01
dhellmannthe scripts all work, it's a matter of setting up a job with a trusted gpg key19:02
dhellmannare you using the same versioning as neutron?19:02
bdemerssame major.minor in kilo19:03
dhellmannthe setup.cfg for networking-cisco has an old version # that doesn't match what neutron is using19:03
*** jhesketh has joined #openstack-relmgr-office19:03
dhellmannare you releasing for kilo or liberty?19:03
dhellmannah, ok19:03
dhellmannso you're releasing from the stable/kilo branch?19:04
*** sigmavirus24_awa is now known as sigmavirus2419:04
bdemersfor libery going forward, i assume we want to be independ of the neutron version, but that likely needs more disussion19:04
bdemersyeah, from stable/kilo19:04
dhellmannthe scripts may be less helpful, then, since most of them are anticipating post-versioning style projects19:06
dhellmannbdemers: have a look at the rcdelivery.sh script19:07
dhellmannbdemers: you may also want to consult with ttx tomorrow, since he has more experience with pre-version project releases19:08
bdemerswill do, thanks!19:11
*** dims has joined #openstack-relmgr-office19:18
*** dims has quit IRC19:25
*** armax has quit IRC19:26
*** lifeless has quit IRC19:34
*** sdague has quit IRC19:34
*** jhesketh has quit IRC19:34
*** sdague has joined #openstack-relmgr-office19:34
*** lifeless has joined #openstack-relmgr-office19:34
*** jhesketh has joined #openstack-relmgr-office19:35
*** dims has joined #openstack-relmgr-office19:35
* ttx is back19:35
bdemersttx: good timing, not much scroll back, see above19:36
ttxdhellmann: who do we have left to sync up with  ? David, Morgan and Steve ?19:37
ttxbdemers: reading19:37
dhellmannttx: we had a few who wanted to come back tomorrow after cleaning up the milestone page19:38
dhellmannttx: morgan was one of those, only stevebaker and david-lyle have been completely absent so far, and steve has a note he'll be around at some point today19:39
stevebakerdhellmann: I'm ready now if you like19:40
stevebakerttx: ^19:40
ttxbdemers: https://wiki.openstack.org/wiki/StableBranchRelease has a process for stable releases19:40
dhellmannstevebaker: hi!19:40
dhellmannstevebaker: looking over https://launchpad.net/heat/+milestone/liberty-3 now19:40
stevebakerdhellmann: hey19:41
dhellmannI see a few blueprints that are in progress, are those blockers?19:41
ttxbdemers: it's mostly about pushing a tag and then get the launchpad page (if you have any) aligned19:41
dhellmannttx: I wasn't sure if any of our scripts that do things with tarballs would help19:41
dhellmannnone seemed to quite match up with a final release19:41
ttxI'm mostly blind to that process, been handled by stable branch managers19:41
stevebakerdhellmann: they are not blockers, but I'd like them to be considered for FFE so have left them there and set them High19:42
ttxdhellmann: and they use a lot of manual steps19:42
bdemersttx: is there any limit to how often we can release, (i.e. up to a release for every bug fix on stable)19:42
dhellmannstevebaker: ok, you can move those to the new rc1 milestone to track them as FFEs there -- and FFEs are up to you to sign-off on, though we'll be happy to consult if you need an outside opinion19:42
dhellmannttx: that's what I thought19:42
ttxbdemers: back in kilo the versioning scheme was different, so you would issue 2015.1.z19:43
ttxand traditionally that would be bumped at the same time as neutron is19:43
dhellmannstevebaker: the same question applies to the open bugs -- those are easy to move out of the milestone with a script if you'd like19:43
bdemersbut we _can_ release at a different cadence as neutron right ?19:44
ttxbdemers: neutron stadium releases are a bit of a grey area, and stable/kilo is completely dark since those repos didn't really exist back then19:44
stevebakerdhellmann: there are no blocker bugs I believe19:44
ttxbdemers: which is why it's easier to start with liberty and use semver x.y.z still versioning. Then yes, you could in theory release for every fix19:44
dhellmannstevebaker: ok, I can run the script to clean those up at any point, so let me know if you want me to do that or take a look at them all by hand first19:45
stevebakerdhellmann: ok. will you cut the release at any time?19:46
bdemersi figured liberty would be much easier, but tring to nail down some kilo work with before libery is cut19:46
ttxbdemers: difficult to have that discussion with mestery on holiday, but I suspect he had an idea of how those would be released and if stable/kilo releases would make sense or not19:46
dhellmannstevebaker: I'll tag the L3 milestone when you give the go-ahead19:46
dhellmannstevebaker: we'd like to do that by thursday19:46
ttxbdemers: let me check if there are tarball jobs set up19:47
bdemersttx: ok, does mestery ususally hang out in this room ?19:47
ttxbdemers: he does, but he is away this week19:47
dhellmannstevebaker: then for RC1, we would like to have that by the end of september, but you'll want to balance doing it early with the extra work for back-porting bug fixes19:47
*** lifeless has quit IRC19:47
ttxbdemers: jobs appear to be up and publishing to http://tarballs.openstack.org/networking-cisco/19:48
stevebakerdhellmann, ttx: I'm on PTO next 2 days but will be back on your Friday. asalkeld has agreed to do go-ahead duties19:48
ttxbdemers: and there was a 2015.1.0 posted there some time ago19:48
dhellmannstevebaker: ok, I'll make a note of that19:48
stevebakerdhellmann: thanks19:48
ttxbdemers: pushing a 2015.1.1 tag to stable/kilo current head should do it19:49
ttxSam Betts did that for 2015.1.019:49
bdemersttx: cool, i’ll chat with sam when he is back on in the morning19:50
ttxpushing a tag is just about using git tag -s then git push19:50
bdemersyeah, but i doubt i have privs for that19:51
david-lyledhellmann: what have I been missing ?19:51
*** lifeless has joined #openstack-relmgr-office19:52
stevebakerttx: can I get back to you about Heat summit space needs in 12 hours? (after the heat meeting)19:54
ttxstevebaker: sure19:55
ttxdavid-lyle: we could catch up after the TC meeting19:55
david-lylettx: sure19:55
dhellmanndavid-lyle: what ttx said :-)19:55
david-lylejust saw my name fly by19:55
openstackgerritMatt Riedemann proposed openstack/releases: Release os-brick 0.4.0  https://review.openstack.org/21901319:59
openstackgerritMerged openstack/releases: Oslo Releases for Sep 1, 2015  https://review.openstack.org/21936220:05
*** armax has joined #openstack-relmgr-office20:05
*** bswartz has quit IRC20:44
dhellmanndavid-lyle: shall we sync up for L3?21:05
david-lyledhellmann:  sure, was cleaning up the status21:08
* dhellmann reloads the page21:08
dhellmannok, I see 2 open blueprints on https://launchpad.net/horizon/+milestone/liberty-3 and several bugs, are those blockers for the L3 tag?21:09
david-lyleno, the critical bug has been resolved, updating21:10
david-lyleand 1 of the 2 bps won't make it, so I moved it out21:10
david-lyleI expect a couple more to merge in by tag time21:10
dhellmannok. if you have anything you want to hold as a FFE, you can put that in the new rc1 milestone to track it21:10
david-lyleI'm sure we'll have ~521:10
dhellmannthe scripts will clear out any open blueprints or bugs when I run it when you're ready to tag21:10
david-lylewe get later items21:11
dhellmannyou've done this before, but just as a reminder: there's no specific date for the RC1 tag & branch operation, but we'd like to do it by the end of september21:11
david-lyleok, we can handle that21:11
dhellmannpicking the date means balancing the needs of bug work, FFEs, etc. with the desire to open master back up for full feature work21:12
dhellmannwe'll leave FFE management up to you, as well as that date21:12
david-lyleright and we'll have an RC-2 for final translations at a minimum21:12
dhellmannso let us know when you're ready and we'll coordinate the steps needed to make the rc121:12
dhellmannmakes sense21:12
david-lyleI've worked that out with Daisy already21:12
david-lyleack, on RC-121:13
dhellmannok, did you have any questions for us?21:14
david-lylewe're target Thursday for the L-3 tag, correct?21:14
dhellmannyes, and we can do it earlier if those patches land21:14
david-lylethursday is better :)21:14
david-lyleless FFE, hopefully21:15
dhellmannI've been hearing that a lot today21:15
david-lyleI bet21:15
dhellmannanything else?21:15
david-lylethat's it for now, I'll need one more django_openstack_auth release, probably around Thursday as well21:16
dhellmannok, that can happen whenever you're ready21:16
david-lyleupdate from g-r and another pending change21:16
david-lyleok, I'll ping you when we're ready21:16
dhellmannyep, we'll have a round of other lib releases for the same reasons21:16
dhellmannsounds good, just check back in here with me or ttx when you're ready for the tag on the horizon repo21:16
david-lylewill do. Thanks!21:17
dhellmanndavid-lyle: thanks!21:17
lifelessdouble checking21:33
lifelessis requirements in freeze now ?21:33
lifelessttx: ^21:33
ttxlifeless: no21:37
ttxlifeless: will be soft-frozen (i.e. require exceptions / good reasons) startign Friday21:38
openstackgerritDoug Hellmann proposed openstack/releases: group service and library projects separately  https://review.openstack.org/21946521:40
openstackgerritDoug Hellmann proposed openstack/releases: show more of the release summary in table  https://review.openstack.org/21946621:40
*** sigmavirus24 is now known as sigmavirus24_awa22:18
*** gordc has quit IRC22:27
morgandhellmann, ttx: tomorrow we should be ready to release keystoneauth 1.x it looks like22:35
morgandhellmann, ttx: i'll post to the repo so we can add it to g-r (will make SDK team happy)22:35
morganbefore the soft-freeze22:35
openstackgerritJim Rollenhagen proposed openstack/releases: Release python-ironicclient 0.8.0  https://review.openstack.org/21947622:42
jrolldhellmann: going to check with ironic folks a bit on that but I think we're good to go here ^22:43
*** dims has quit IRC23:03
*** dims__ has joined #openstack-relmgr-office23:24
*** jhesketh has quit IRC23:54
*** jhesketh has joined #openstack-relmgr-office23:55

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