| *** thinrichs has quit IRC | 00:01 | |
| *** thinrichs has joined #openstack-release | 00:03 | |
| *** thinrichs has quit IRC | 00:15 | |
| *** daemontool_ has joined #openstack-release | 00:26 | |
| *** daemontool has quit IRC | 00:27 | |
| *** gordc has joined #openstack-release | 00:30 | |
| *** dims has joined #openstack-release | 00:57 | |
| *** kzaitsev_mb has quit IRC | 01:04 | |
| *** sdake has quit IRC | 01:06 | |
| *** sdake has joined #openstack-release | 01:08 | |
| *** sdake_ has joined #openstack-release | 01:11 | |
| *** sdake has quit IRC | 01:14 | |
| *** mriedem has quit IRC | 01:17 | |
| *** sigmavirus24_awa is now known as sigmavirus24 | 01:21 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 01:22 | |
| openstackgerrit | Adam Gandelman proposed openstack/releases: Astara 8.0.0.0rc1 mitaka release candidate https://review.openstack.org/295589 | 01:31 |
|---|---|---|
| openstackgerrit | Merged openstack/releases: ironic-python-agent 1.2.0 https://review.openstack.org/295559 | 01:35 |
| *** gordc has quit IRC | 02:26 | |
| *** _amrith_ is now known as amrith | 02:26 | |
| *** dims has quit IRC | 02:28 | |
| *** sdake_ is now known as sdake | 03:08 | |
| *** amrith is now known as _amrith_ | 03:44 | |
| prometheanfire | someone 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 |
| prometheanfire | could be non-voting periodic with maintainers (distro) being the particular benifiting parties | 04:40 |
| prometheanfire | tonyb: here | 04:40 |
| prometheanfire | not -stable | 04:40 |
| tonyb | Ah okay | 04:40 |
| prometheanfire | -stable is dead iirc, long live -releases | 04:40 |
| tonyb | prometheanfire: nope, I'm in stable all the time it is a good place to talk about stable specific stuff | 04:41 |
| prometheanfire | oh | 04:41 |
| prometheanfire | should I be asking that there then? | 04:41 |
| clarkb | fwiw thats basically how the constraints update jobs work | 04:41 |
| tonyb | prometheanfire: do you mean pip install without constraints? | 04:41 |
| prometheanfire | yes, without | 04:42 |
| tonyb | prometheanfire: here is fine. | 04:42 |
| prometheanfire | I've been told that deps of openstack serices (nova/cinder/keystone/etc) should be supported uncapped for two releases | 04:43 |
| prometheanfire | I'd like tests for that | 04:43 |
| clarkb | we do test it whenever we update constraints | 04:43 |
| prometheanfire | then I could just pay attention to requirements.txt and dev-reqs.txt updates instead of upper-reqs | 04:43 |
| clarkb | also I dont know that openstack has ever made that promise | 04:43 |
| prometheanfire | I've been told that in here, it wasn't a promise yet, but more of an expectation | 04:44 |
| prometheanfire | if I leave my deps uncapped, where can I get updates as to when I need to cap them for a particular project? | 04:44 |
| prometheanfire | for instance only nova if only it had a problem would be optimal | 04:45 |
| clarkb | when the constraint update changes fail | 04:45 |
| prometheanfire | which are which file? | 04:45 |
| clarkb | constraints | 04:45 |
| prometheanfire | upper-constraints? | 04:45 |
| clarkb | ya | 04:45 |
| prometheanfire | so only when that job fails? | 04:45 |
| prometheanfire | I am monitoring gerrit for that file already | 04:45 |
| clarkb | every day we bump them to the newest version allowed and push that to requirwments, this runs a bunch of tests | 04:46 |
| prometheanfire | so it'll be somewhat easy to follow | 04:46 |
| clarkb | if that fails there is a good chance dep doesnt work | 04:46 |
| prometheanfire | my current plan (packaging wise) is to leave mitaka uncapped and cap as needed | 04:46 |
| prometheanfire | then I'll update oslo on every release instead of ignoring most of them (and other deps in openstack) | 04:47 |
| prometheanfire | does that sound sane? | 04:47 |
| prometheanfire | also, my 'as needed' is defined as watching for fails in upper-reqs update jobs | 04:47 |
| prometheanfire | so, how are those fails handled | 04:47 |
| prometheanfire | a seperate commit to the same file? | 04:48 |
| clarkb | ya usually requires human intervention to bump a subset or fix then bump | 04:48 |
| prometheanfire | ok, then I'll only watch for updates to upper-reqs that are NOT automated | 04:48 |
| prometheanfire | that'll make it easier | 04:49 |
| prometheanfire | wonder if I can get gerrit to only email me when something is merged | 04:49 |
| prometheanfire | is it the 'Submitted Changes' notification? | 04:50 |
| prometheanfire | guess I'll test | 04:50 |
| prometheanfire | clarkb: tonyb that plan sound sane btw? | 04:50 |
| * prometheanfire needs to package heat this release | 04:51 | |
| tonyb | prometheanfire: +1 to adding heat | 04:52 |
| clarkb | I woukd watch for jenkins -1 on openstack/requirementa | 04:52 |
| tonyb | prometheanfire: I'd need to think harder about the problem to really evaluate if that'll work. | 04:52 |
| prometheanfire | ah, that's right, it needs to to package ALL THE CLIENTS | 04:52 |
| tonyb | prometheanfire: doesn't horizon also need that? | 04:53 |
| prometheanfire | tonyb: not sure what time it is for you, but we could talk face to face vidyo | 04:53 |
| prometheanfire | I don't package horizon | 04:53 |
| *** daemontool__ has joined #openstack-release | 04:53 | |
| *** daemontool_ has quit IRC | 04:53 | |
| prometheanfire | I used to, but it's hell | 04:53 |
| prometheanfire | clarkb: you know the search expression? | 04:53 |
| tonyb | prometheanfire: Ah that'd explain it. | 04:53 |
| clarkb | prometheanfire: not off the top of my head but it is doable and documented in gerrit docs | 04:53 |
| tonyb | prometheanfire: Normally this would be a fine time but I need to duck out for a bit. (grab my son from school) | 04:54 |
| prometheanfire | clarkb: searching for status:merged might be more useful for me | 04:54 |
| prometheanfire | tonyb: np, mind bugging me when you get in tomorrow? | 04:55 |
| tonyb | prometheanfire: Sure. | 04:56 |
| prometheanfire | tonyb: I'll try to remind you if you forget | 04:56 |
| tonyb | prometheanfire: cool. | 04:57 |
| prometheanfire | made a weekly task to check for non-automated updates to upper-reqs so I don't forget the new update procedure | 04:57 |
| prometheanfire | hopefully 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 packagers | 04:58 |
| *** kzaitsev_ws has quit IRC | 06:01 | |
| *** kzaitsev_ws has joined #openstack-release | 06:01 | |
| *** sdake has quit IRC | 07:29 | |
| *** daemontool__ has quit IRC | 07:50 | |
| openstackgerrit | Andreas Jaeger proposed openstack/releases: openstack-doc-tools 0.34.0 https://review.openstack.org/295664 | 08:22 |
| AJaeger | dhellmann, dims, ttx, could we get a new release of openstack-doc-tools for Mitaka, please? ^ | 08:23 |
| ttx | yes sure. Will process the release queue shortly | 08:24 |
| AJaeger | thanks, ttx! | 08:24 |
| AJaeger | ttx, do you want me to review translations again? | 08:25 |
| AJaeger | ttx, will do it now in case you want to take some | 08:31 |
| *** openstackgerrit has quit IRC | 08:33 | |
| *** openstackgerrit has joined #openstack-release | 08:33 | |
| ttx | AJaeger: can't hurt, at least for teh initial / big ones | 08:34 |
| AJaeger | ttx, quite some large imports see https://review.openstack.org/#/q/status:open+topic:zanata/translations+branch:stable/mitaka | 08:34 |
| *** daemontool has joined #openstack-release | 08:34 | |
| *** pcaruana has joined #openstack-release | 08:40 | |
| *** daemontool has quit IRC | 08:57 | |
| *** doug-fish has quit IRC | 09:04 | |
| ttx | Processing congress rc1 | 09:36 |
| *** sdague has joined #openstack-release | 09:44 | |
| *** dims has joined #openstack-release | 09:51 | |
| *** dims has quit IRC | 10:04 | |
| ttx | wow, that release job is dead slow | 10:07 |
| ttx | 30min to get congress repos cloned | 10:07 |
| ttx | dims: please review https://review.openstack.org/#/c/294776/ to unblock patch chain | 10:09 |
| patchbot | ttx: patch 294776 - openstack-infra/release-tools - make the default dashboard format csv | 10:09 |
| *** dims has joined #openstack-release | 10:12 | |
| ttx | aaand.. timeout. | 10:20 |
| openstackgerrit | Merged openstack/releases: murano deliverables 2.0.0.0rc1 - mitaka https://review.openstack.org/295575 | 10:26 |
| ttx | kzaitsev_ws: I'll create your stable/mitaka branches from that RC1 tag | 10:32 |
| ttx | unless you tell me it's a bad idea | 10:32 |
| *** _amrith_ is now known as amrith | 10:37 | |
| openstackgerrit | Merged openstack/releases: Release Mitaka RC1 for Congress https://review.openstack.org/295473 | 10:41 |
| ttx | mucho faster | 10:43 |
| openstackgerrit | Merged openstack/releases: Astara 8.0.0.0rc1 mitaka release candidate https://review.openstack.org/295589 | 10:51 |
| *** kzaitsev_mb has joined #openstack-release | 10:51 | |
| dims | good afternoon ttx | 10:51 |
| dims | ttx : i updated the spreadsheet last night after cutting ironic-python-agent release and cutting their stable branch - fyi | 10:52 |
| ttx | ack | 10:53 |
| ttx | and hi! | 10:53 |
| ttx | dims feel free to +A https://review.openstack.org/#/c/295137/ and https://review.openstack.org/#/c/294594/ | 10:57 |
| patchbot | ttx: patch 295137 - releases - Tacker was not part of the Liberty release | 10:57 |
| patchbot | ttx: patch 294594 - releases - Adding missing mitaka releases | 10:57 |
| ttx | I think I covered all dhellmann's comments there | 10:57 |
| ttx | dims: I'll stop for lunch, you can process openstack-doc-tools 0.34.0 | 10:58 |
| dims | ttx : on it | 11:16 |
| openstackgerrit | Merged openstack/releases: Tacker was not part of the Liberty release https://review.openstack.org/295137 | 11:19 |
| openstackgerrit | Merged openstack/releases: Adding missing mitaka releases https://review.openstack.org/294594 | 11:19 |
| openstackgerrit | Merged openstack/releases: openstack-doc-tools 0.34.0 https://review.openstack.org/295664 | 11:20 |
| *** daemontool has joined #openstack-release | 11:28 | |
| dims | AJaeger : openstack-doc-tools 0.34.0 is out | 11:29 |
| AJaeger | thanks, dims! | 11:31 |
| AJaeger | dims, please approve the requirements change as well: https://review.openstack.org/#/c/295665/ | 11:32 |
| patchbot | AJaeger: patch 295665 - requirements - Bump uc for openstack-doc-tools 0.34 | 11:32 |
| dims | AJaeger : do the jobs you need this for subject to constraints? (we haven't unfreezed requirements yet) | 11:33 |
| AJaeger | indeed, they do not... | 11:33 |
| dims | great! then i'll just do a W-1 on it | 11:35 |
| AJaeger | ok | 11:36 |
| *** gordc has joined #openstack-release | 11:37 | |
| *** doug-fish has joined #openstack-release | 11:42 | |
| openstackgerrit | Merged openstack-infra/release-tools: make the default dashboard format csv https://review.openstack.org/294776 | 11:46 |
| openstackgerrit | Merged openstack-infra/release-tools: sort on the managed flag before other values https://review.openstack.org/294777 | 11:46 |
| *** kzaitsev_mb has quit IRC | 11:47 | |
| *** doug-fis_ has joined #openstack-release | 11:50 | |
| *** doug-fish has quit IRC | 11:52 | |
| gordc | dhellmann, ttx: i was wondering, does releases project only handle big tent projects or can any project under openstack domain use it? | 11:58 |
| openstackgerrit | Merged openstack-infra/release-tools: lower case all team names to sort consistently https://review.openstack.org/294778 | 11:58 |
| openstackgerrit | Merged openstack-infra/release-tools: add PTL email to release dashboard https://review.openstack.org/294779 | 11:58 |
| dims | gordc : apply for release:managed tag first in governance? https://governance.openstack.org/reference/tags/release_managed.html | 12:01 |
| dims | gordc : which project? | 12:01 |
| gordc | dims: just asking generically. i was asked the question recently. | 12:01 |
| dims | gordc : ack, please point them to "Tag application process" at the end of that page | 12:02 |
| gordc | i was doing a query and it seemed most the items are in some way 'official'. thanks for link though | 12:03 |
| *** kzaitsev_mb has joined #openstack-release | 12:03 | |
| dims | gordc : right, no one else has asked i think :) | 12:03 |
| AJaeger | gordc: but what dims says means for me : Only big tent projects | 12:06 |
| AJaeger | sicne those are the only ones listed in governance repository | 12:06 |
| dims | AJaeger : hmm, interesting | 12:07 |
| dims | AJaeger : where do people ask for git repos? | 12:08 |
| dims | project-config? | 12:08 |
| AJaeger | dims: git repos via project-config. | 12:09 |
| AJaeger | dims: Example https://review.openstack.org/295260 | 12:10 |
| AJaeger | And 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 |
| dims | AJaeger : y looking, so there's no spot in governance repo for non-bigtent projects | 12:10 |
| dims | AJaeger : ack | 12:11 |
| AJaeger | Like https://review.openstack.org/#/c/292335/ | 12:11 |
| patchbot | AJaeger: patch 292335 - governance - Add Designate & Zaqar roles to OpenStack-Ansible P... (MERGED) | 12:11 |
| gordc | ah i see. so big tent only. | 12:11 |
| gordc | cool cool | 12:11 |
| AJaeger | dims: indeed, there's no spot in governance for non-bigtent projects. governance == big-tent | 12:12 |
| dims | ttx : is this by design? ^^ | 12:12 |
| AJaeger | and mission of release team is AFAIK: Governance ;) | 12:12 |
| AJaeger | dims, 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 |
| dims | AJaeger : for example, dhellmann mentioned that release team could cut branches for projects that wanted them | 12:13 |
| AJaeger | dims: that would be IMHO a change of scope. | 12:13 |
| AJaeger | I'm not objecting, that's your call ;) Just pointing it out. | 12:13 |
| kzaitsev_mb | ttx: saw your message about stable/mitaka and RC1. Thanks for cutting us a stable branch =) | 12:14 |
| AJaeger | it 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 |
| gordc | AJaeger: 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 |
| dims | AJaeger : gordc : http://markmail.org/message/hgcx5l3btkrgr5k5 | 12:16 |
| AJaeger | gordc: yep | 12:16 |
| gordc | dims: cool cool, i vaguely remember reading that. | 12:16 |
| AJaeger | dims: python-senlinclient is in governance, isn't it? For me that message means: TAke on more governance repos... | 12:16 |
| dims | AJaeger : right | 12:17 |
| dims | AJaeger : once we take the couple of manual steps out, all it would take is +2A to get a release out | 12:18 |
| sdague | hmmm... so who has branch push rights? | 12:19 |
| dims | sdague : 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 branches | 12:21 |
| sdague | I'm looking at the devstack branching, and I really thought I could do this | 12:21 |
| dims | sdague : check ACL? | 12:22 |
| sdague | dims: ok, but what about for things like devstack that don't have releases | 12:22 |
| dims | sdague : https://review.openstack.org/#/admin/groups/416,members - you should be all set | 12:23 |
| sdague | nope | 12:23 |
| sdague | I can definitely not push a new branch | 12:23 |
| dims | sdague : if you need it today, i can do it without a review (there's a ./make_stable_branch.sh script) | 12:24 |
| sdague | though I also have a bad tag out there which I need to get sorted | 12:24 |
| dims | sdague : which one? | 12:24 |
| sdague | I was following devstack branch docs, and they said to push a tag, which is wrong. | 12:25 |
| sdague | so I have a stable/mitaka tag out there | 12:25 |
| dims | i see a "stable/mitaka" tag. | 12:25 |
| dims | ack | 12:25 |
| sdague | right, so that needs deleting | 12:25 |
| sdague | I do not have the rights to delete it | 12:25 |
| sdague | though I do have the rights to create it | 12:26 |
| sdague | after that we need to branch. Originally we were waiting for swift, but I've been looking at logs, and we should be fine | 12:26 |
| sdague | and without the stable branch upgrade on stable/mitaka is actually testing liberty -> master | 12:27 |
| sdague | so the backports aren't getting tested | 12:27 |
| sdague | for upgrade | 12:27 |
| *** bdemers has quit IRC | 12:27 | |
| dims | sdague : "git push --delete origin tagname" ? | 12:27 |
| sdague | git push gerrit :refs/tags/stable/mitaka is what the internet tells me it should be | 12:28 |
| sdague | http://paste.openstack.org/show/491442/ is what I get | 12:28 |
| dims | ok. let me see if i can delete that tag | 12:32 |
| sdague | I also asked yolanda in -infra | 12:33 |
| sdague | dims: the make_stable_branch.sh makes a lot of assumptions about projects which I don't think apply here | 12:33 |
| sdague | like $VERSION | 12:33 |
| sdague | ok, the tag is deleted now | 12:34 |
| dims | sdague : you were able to delete it? | 12:34 |
| sdague | yolanda did | 12:34 |
| dims | sdague : instead of the VERSION i can pass a SHA | 12:36 |
| sdague | ok | 12:36 |
| dims | what SHA would you like? | 12:37 |
| dims | HEAD? | 12:37 |
| ttx | dims: yes, governance == official == big-tent | 12:37 |
| ttx | sdague: about rights, you may be able to use the gerrit branch creation UI. At one point I could do ont without the other | 12:38 |
| ttx | one* | 12:38 |
| sdague | dims: HEAD is fine | 12:39 |
| ttx | fwiw I have branch/tag creation rights but no branch/tag deletion right either :) | 12:39 |
| sdague | ttx: where is that? | 12:39 |
| dims | let me try | 12:39 |
| ttx | sdague: example for grenade https://review.openstack.org/#/admin/projects/openstack-dev/grenade,branches | 12:39 |
| sdague | ttx: I don't have create anywhere there | 12:40 |
| ttx | create branch is greyed if you don't have branch creation rights | 12:40 |
| ttx | sdague: ok, so that is consistent. I think you need push refs rights to create branches/tags | 12:40 |
| dims | sdague : done - https://github.com/openstack-dev/devstack/tree/stable/mitaka | 12:40 |
| sdague | dims: cool | 12:41 |
| ttx | "Create Reference" maybe | 12:41 |
| dims | sdague : "./make_stable_branch.sh mitaka openstack-dev/devstack HEAD" | 12:41 |
| ttx | separate from "Push Signed Tag" | 12:41 |
| sdague | right | 12:41 |
| dims | ttx : ah ok | 12:42 |
| sdague | there is some wiki documentation which is just really confusing here | 12:42 |
| sdague | for the QA team | 12:42 |
| sdague | will need to clean that up | 12:42 |
| * ttx creates stable branches for murano | 12:42 | |
| dims | ttx : i forgot to tell you "captain, you have the con" :) | 12:43 |
| ttx | ayeaye | 12:43 |
| * dims wanders off to get some bfst | 12:43 | |
| ttx | kzaitsev: all set, master open for newton development | 12:50 |
| *** mriedem has joined #openstack-release | 12:59 | |
| *** dims_ has joined #openstack-release | 13:02 | |
| *** dims has quit IRC | 13:02 | |
| *** daemontool has quit IRC | 13:07 | |
| *** bswartz has quit IRC | 13:08 | |
| *** daemontool has joined #openstack-release | 13:09 | |
| *** bswartz has joined #openstack-release | 13:14 | |
| dims_ | sdague : need any others? grenade? | 13:33 |
| sdague | I will, but I want to make sure the devstack branch runs right first | 13:33 |
| sdague | there are changes in queue for those now | 13:33 |
| dims_ | ack sdague : i should be off an on today heading to BU to talk to a class about OpenStack | 13:34 |
| sdague | ok, no prob | 13:35 |
| *** daemontool has quit IRC | 13:48 | |
| *** bdemers has joined #openstack-release | 13:50 | |
| *** daemontool has joined #openstack-release | 13:54 | |
| *** sigmavirus24_awa is now known as sigmavirus24 | 14:05 | |
| *** doug-fis_ is now known as doug-fish | 14:11 | |
| ttx | redrobot: how far are you from RC1 ? | 14:12 |
| ttx | daemontool: same question ^ | 14:13 |
| daemontool | ttx, most probably today we can tag RC1 | 14:19 |
| *** dims_ has quit IRC | 14:19 | |
| daemontool | ttx, ping | 14:32 |
| daemontool | the stable/mitaka branch too needs to be created by the service teams? | 14:33 |
| daemontool | or x.x.x.xrc1 tag only? | 14:33 |
| *** openstackgerrit has quit IRC | 14:33 | |
| *** openstackgerrit has joined #openstack-release | 14:34 | |
| *** vgridnev has joined #openstack-release | 14:43 | |
| redrobot | ttx I think we may be ready today. I had a question regarding the release notes though. | 14:52 |
| redrobot | ttx who moves the "unreleased" notes into a mitaka.rst page? | 14:52 |
| *** sdake has joined #openstack-release | 14:58 | |
| ttx | daemontool: we can tag and create the branch if you submit an openstack/releases change | 15:03 |
| ttx | daemontool: something like https://review.openstack.org/#/c/295473/ | 15:04 |
| patchbot | ttx: patch 295473 - releases - Release Mitaka RC1 for Congress (MERGED) | 15:04 |
| ttx | redrobot: I think it happens automagically. dhellmann should ba able to answer that question when he is back tomorrow | 15:05 |
| daemontool | ttx, so like the pervious releases, only a change in openstack/releases is needed by the service Team, ty | 15:12 |
| *** vgridnev has quit IRC | 15:16 | |
| *** amrith is now known as _amrith_ | 15:18 | |
| ttx | daemontool: you don't even need to tag if you push the change, we can tag and sign for you | 15:18 |
| daemontool | ok ty | 15:19 |
| *** vgridnev has joined #openstack-release | 15:28 | |
| *** bdemers has quit IRC | 15:34 | |
| *** bdemers has joined #openstack-release | 15:37 | |
| *** dims has joined #openstack-release | 15:45 | |
| *** vgridnev has quit IRC | 15:54 | |
| *** dims_ has joined #openstack-release | 15:55 | |
| *** dims has quit IRC | 15:55 | |
| *** kzaitsev_mb has quit IRC | 16:11 | |
| sdake | dhellmann quick question | 16:11 |
| sdake | there is a bit of debate about how we hsould handle backports from our master branch to our stable/mitaka branch for rc2 and rc3 bugs | 16:12 |
| sdake | option 1 is to tarrget the bug to newton and liberty | 16:12 |
| sdake | option 2 is to use rc-backport-potential tag | 16:12 |
| sdake | i looked around at various projects | 16:12 |
| sdake | and can't find a consistent handling of how bugs are managed in the rcs so backports aren't lost | 16:13 |
| sdake | dhellmann 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 it | 16:13 |
| sdake | in the meantime i'm going to try to catch some fish and dig in the other repos for that initial commit | 16: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 |
| sdake | dims_ do you hve any idea? I pinged ttx offf-channel before thinking to ask here :) | 16:16 |
| sdake | and he seems to be afk | 16:16 |
| dims_ | y, a bit late in the day for him | 16:16 |
| sdake | agreed | 16:16 |
| clarkb | you can probably just look at any project that uses reno | 16:16 |
| sdake | usuallly he is around at my 8am timestart | 16:16 |
| dims_ | sdake : Nova uses the backport potential tag i believe | 16:16 |
| clarkb | should be in their git history | 16:17 |
| dims_ | sdake : http://docs.openstack.org/developer/reno/usage.html | 16:17 |
| dims_ | sdake : ^^ getting started tips | 16:17 |
| sdake | clarkb agreed thanks | 16:17 |
| sdake | dims_ 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 |
| sdake | but i guess i'll TBF | 16:18 |
| *** SamYaple has joined #openstack-release | 16:18 | |
| SamYaple | o/ | 16:18 |
| dims_ | sdake :) | 16:18 |
| *** inc0 has joined #openstack-release | 16: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 IRC | 16:21 | |
| sdake | dims_ thanks i'll copy that and cut&paste | 16:22 |
| ttx | ohai | 16:22 |
| ttx | sdake: you mean tracking on Launchpad ? | 16:23 |
| sdake | dims_ yu rock :) | 16:23 |
| sdake | ttx right | 16:23 |
| ttx | sdake: yes, it's a pretty common question, because there is no perfect answer | 16:23 |
| ttx | option 1, you create a mitaka series task and target the RC milestone | 16:24 |
| dims_ | sdake : i just point to stuff, that's not hard work :) | 16:24 |
| ttx | that lets you track the landing of the master patch in the main series | 16:24 |
| ttx | *if* you set the mitaka branch status to pre-release | 16:24 |
| ttx | and newton as the active development series | 16:24 |
| *** sdake has quit IRC | 16:25 | |
| ttx | main drawback of this option is that only launchpad project drivers can create (or approve) series tasks | 16:25 |
| ttx | I think we lost sdake | 16:25 |
| inc0 | I'll pass everything;) | 16:25 |
| SamYaple | ttx: im still here | 16:25 |
| inc0 | also logs are useful;) | 16:26 |
| dims_ | :) | 16:26 |
| ttx | option 2, you use tags | 16:26 |
| ttx | option 3, you use some etherpad to track backports | 16:26 |
| SamYaple | to be fair, we did discuss and were using option 1 before 2016 rolled around | 16:26 |
| ttx | the way we did it when we handled that is a combination of option 1 and 2 | 16:27 |
| ttx | you let people submit RC candidates using a tag | 16:27 |
| inc0 | option 2 seems to be more lightweight | 16:27 |
| ttx | and you track what's approved to a RC using series tasks and milestones | 16:27 |
| ttx | it's a bit more intensive on the PTL /driver/ release liaison, but that's the only way to track it perfectly | 16:28 |
| inc0 | ttx, that actually seems to be reasonable common ground | 16:28 |
| ttx | it's just a pain to set up due to LP getting in the way | 16:28 |
| ttx | happy to help align the branch statuses and drivers teams so that you can do that | 16:28 |
| *** sdake has joined #openstack-release | 16:29 | |
| inc0 | hey sdake read the logs | 16:29 |
| ttx | (funnily enough, LP has a concept of "release manager" but that person can't create series tasks either.) | 16:29 |
| sdake | ttx apologies battery went to 0% :( | 16:29 |
| sdake | will do | 16:29 |
| inc0 | ttx suggested good common ground imho | 16:29 |
| ttx | you have to be a driver to create series tasks (or approve the ones that were proposed) | 16:29 |
| sdake | ttx ya we have alot of drivers - we let anyone in that team so they can target bugs and blueprints to themselves | 16:30 |
| sdake | i think we needt o change that aroudn a bit | 16:30 |
| ttx | again, you need to set up your series status in launchpad so that it understands that master is now Newton, not Mitaka | 16:30 |
| ttx | otherwise you won't be able to create mitaka series tasks | 16:30 |
| sdake | ttx let me read the logs once the bot catches up | 16:30 |
| SamYaple | i think we all agree both work. my only concern was single threading one person which tags seem like they might do | 16:30 |
| ttx | alright, let me know if you have additional questions | 16:30 |
| SamYaple | ttx: the series was changed | 16:31 |
| SamYaple | but now it seems to have reverted | 16:31 |
| * ttx looks | 16:31 | |
| ttx | on Kolla right | 16:31 |
| SamYaple | not sure why its back at mitaka | 16:31 |
| ttx | I for sure didn't touch it :) | 16:31 |
| * SamYaple pulls out the pitchforks | 16:32 | |
| sdake | i changed he series to newton to see if that was what SamYaple was talkingabout | 16:33 |
| ttx | and goven Launchpad marvelous audit trail, you clearly won't be able to tell who did | 16:33 |
| sdake | but then reverted that once i understood he was talking about something else | 16:33 |
| sdake | the irc bot caught up | 16:34 |
| SamYaple | sdake: thats what i was talking about though | 16:34 |
| SamYaple | well part of it | 16:34 |
| sdake | let me experiment with whatyou proposed with 1 and 2 | 16:34 |
| sdake | we dont want to use etherpad to track backports | 16:34 |
| SamYaple | right now new bugs filed will go against mitaka | 16:34 |
| sdake | atleast I dont ;) | 16:34 |
| SamYaple | i think we can all agree to that :D | 16:34 |
| sdake | ok i'll change that back | 16:34 |
| SamYaple | ttx: as always thanks for being a wealth of knowleges | 16:35 |
| sdake | ok that is changed | 16:35 |
| sdake | ya ttx knows everything and is always helpful resource :) | 16:35 |
| ttx | more like a historic trove of old crufted best practices | 16:35 |
| SamYaple | also that | 16:36 |
| *** _amrith_ is now known as amrith | 16:36 | |
| sdake | ttx "In release freeze" ? | 16:37 |
| sdake | for the status? | 16:38 |
| sdake | rather pre-release freeze | 16:38 |
| sdake | ttx how do you make a series task? | 16:40 |
| sdake | and you track what's approved to a RC using series tasks and milestones | 16:41 |
| sdake | here is our tracker currently: | 16:41 |
| sdake | https://launchpad.net/kolla/+milestone/mitaka-rc2 | 16:41 |
| ttx | pre-release freeze sounds good once you cut RC1 and have a release branch | 16:42 |
| sdake | yup we have done those things | 16:42 |
| sdake | and we are tagging rc2 friday | 16:42 |
| sdake | and rc3 april 2ndish | 16:42 |
| ttx | sdake: if you look at a bug you should be able to see "create series task" or something. Let me check | 16:43 |
| ttx | "Target to series" | 16:43 |
| sdake | right | 16:43 |
| ttx | that lets you pick a branch name to create a series task | 16:43 |
| ttx | A bug in LP is a collection of BugTasks | 16:44 |
| sdake | so like this https://bugs.launchpad.net/kolla/+bug/1540234 | 16:44 |
| openstack | Launchpad bug 1540234 in kolla "rabbitmq cluster is not work" [Critical,Confirmed] - Assigned to weiyu (weiyu) | 16:44 |
| ttx | each targeted to a series | 16:44 |
| ttx | the complexity comes from the fact that there is a "default" series | 16:44 |
| ttx | which maps to the series which is in "active development" | 16:44 |
| ttx | and that is what the bug shows by default | 16:45 |
| ttx | each task in a bug can have a different project and series | 16:45 |
| ttx | https://bugs.launchpad.net/kolla/+bug/1540234 looks good to me | 16:45 |
| openstack | Launchpad bug 1540234 in kolla mitaka "rabbitmq cluster is not work" [Critical,Confirmed] - Assigned to weiyu (weiyu) | 16:45 |
| sdake | ttx i've updated https://bugs.launchpad.net/kolla/+bug/1540234 with what I think is what you proposed | 16:45 |
| sdake | does that look correct? | 16:45 |
| ttx | yes | 16:46 |
| ttx | you got it :) | 16:46 |
| sdake | ok, SamYaple sound good? | 16:46 |
| sdake | and we use tags as wel in this process | 16:46 |
| sdake | the reason I want tags is so I can keep track of what has actually landed as a backport | 16:46 |
| ttx | tags let random users propose RC bugs, since they can't create series tasks | 16:46 |
| *** dims_ has quit IRC | 16:46 | |
| ttx | forces you to review the tagged bugs, but works around the lack of fine-grained perms in LP | 16:47 |
| sdake | right - atm our drivers team has everyone and their sister ;) | 16:47 |
| sdake | mainly so folks can assign themselves bugs | 16:47 |
| sdake | because prior they couldnt' do so | 16:47 |
| ttx | it's probably fine too | 16:47 |
| sdake | ok, i'll bring it up as your proposal for how to manage bugs at our wednesday meeting | 16:48 |
| sdake | with backports | 16:48 |
| sdake | and if team in agreement i'll post instructions on the ml for the core reviewers who should be doing this work | 16:48 |
| sdake | i think the step we were missing is the "in freeze" | 16:49 |
| sdake | and the agreement on the usage of rc tags | 16:50 |
| sdake | step/steps | 16:50 |
| sdake | do we remove the rc-backport-potential once the bug has been added as a task to mitaka-rc2? | 16:51 |
| sdake | ttx ^ | 16:52 |
| *** pcaruana has quit IRC | 16:52 | |
| SamYaple | sdake: yes that is exactly like what i think we should have | 16:52 |
| ttx | usually a a good idea yes, to avoid re-reviewing it | 16:52 |
| sdake | cool sounds good | 16:52 |
| sdake | i like it | 16:52 |
| SamYaple | sdake: thats what we talked about a few months back | 16:52 |
| SamYaple | cool im glad | 16:52 |
| SamYaple | i think its the clearest way | 16:52 |
| sdake | lets get the core reviewer team to buy in | 16:53 |
| sdake | and we will make it so | 16:53 |
| SamYaple | i agree, last time we had this conversatoin in a meeting | 16:53 |
| sdake | ya I dont think it was at this depth though | 16:53 |
| SamYaple | i was not | 16:53 |
| SamYaple | it* | 16:53 |
| sdake | actually in prep for wednesday's meeting, I'll send out the full process as ttx has described it so peopel can read up | 16:54 |
| sdake | and think about it for a day | 16:54 |
| openstackgerrit | Matt Riedemann proposed openstack/releases: kilo: release python-openstackclient 1.0.5 https://review.openstack.org/295954 | 16:58 |
| *** kzaitsev_mb has joined #openstack-release | 16:58 | |
| ttx | taking a break before the meetings tunnel | 17:01 |
| *** dims has joined #openstack-release | 17:02 | |
| openstackgerrit | Fausto Marzi proposed openstack/releases: Add Freezer release meta for Mitaka-RC1 https://review.openstack.org/295960 | 17:11 |
| *** dims has quit IRC | 17:13 | |
| *** sdake_ has joined #openstack-release | 17:16 | |
| *** sdake has quit IRC | 17:16 | |
| openstackgerrit | Jim Rollenhagen proposed openstack/releases: ironic-python-agent 1.0.2 https://review.openstack.org/295965 | 17:20 |
| *** bswartz has joined #openstack-release | 17:20 | |
| openstackgerrit | Jim Rollenhagen proposed openstack/releases: ironic 4.2.3 https://review.openstack.org/295966 | 17:21 |
| *** daemontool has quit IRC | 17:22 | |
| *** amrith is now known as _amrith_ | 17:24 | |
| *** mriedem1 has joined #openstack-release | 17:28 | |
| *** mriedem has quit IRC | 17:31 | |
| *** Kiall has quit IRC | 17:31 | |
| *** mriedem has joined #openstack-release | 17:31 | |
| *** mriedem has quit IRC | 17:32 | |
| *** mriedem has joined #openstack-release | 17:33 | |
| *** Kiall has joined #openstack-release | 17:33 | |
| *** mriedem1 has quit IRC | 17:33 | |
| *** daemontool has joined #openstack-release | 17:42 | |
| *** krotscheck has quit IRC | 17:43 | |
| *** pcaruana has joined #openstack-release | 17:44 | |
| openstackgerrit | Fausto Marzi proposed openstack/releases: Add Freezer release meta for Mitaka-RC1 https://review.openstack.org/295960 | 17:49 |
| *** daemontool has quit IRC | 18:25 | |
| *** sdake_ is now known as sdake | 18:25 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 18:33 | |
| openstackgerrit | Ihar Hrachyshka proposed openstack-infra/release-tools: Added tool to reset backport-potential tags once backports are merged https://review.openstack.org/295993 | 18:34 |
| *** kzaitsev_mb has quit IRC | 19:03 | |
| *** inc0 has quit IRC | 19:04 | |
| *** kzaitsev_mb has joined #openstack-release | 19:42 | |
| ttx | precessing freezer rc1 | 19:43 |
| ttx | processing* | 19:43 |
| *** sigmavirus24_awa is now known as sigmavirus24 | 19:44 | |
| openstackgerrit | Merged openstack/releases: Add Freezer release meta for Mitaka-RC1 https://review.openstack.org/295960 | 19:47 |
| openstackgerrit | devdatta-kulkarni proposed openstack/releases: Tagging Solum mitaka releases https://review.openstack.org/296032 | 19:50 |
| openstackgerrit | Jim Rollenhagen proposed openstack/releases: ironic 4.2.3 https://review.openstack.org/295966 | 19:55 |
| *** david-lyle_ has joined #openstack-release | 19:56 | |
| *** david-lyle has quit IRC | 19:57 | |
| *** jeblair has quit IRC | 19:58 | |
| *** jeblair has joined #openstack-release | 19:58 | |
| openstackgerrit | devdatta-kulkarni proposed openstack/releases: Tagging Solum mitaka releases https://review.openstack.org/296032 | 20:00 |
| *** david-lyle_ is now known as david-lyle | 20:02 | |
| *** kzaitsev_mb has quit IRC | 20:03 | |
| *** rockyg has joined #openstack-release | 20:07 | |
| *** sdague has quit IRC | 20:31 | |
| *** kzaitsev_mb has joined #openstack-release | 20:31 | |
| *** bdemers has quit IRC | 20:48 | |
| openstackgerrit | Douglas Mendizábal proposed openstack/releases: Release Barbican Mitaka RC1 https://review.openstack.org/296045 | 20:53 |
| openstackgerrit | Jim Rollenhagen proposed openstack/releases: ironic 5.1.0 https://review.openstack.org/296049 | 20:58 |
| jroll | ttx: ^ ironic stable/mitaka release | 20:59 |
| rockyg | dhellmann, you around? | 21:03 |
| ttx | jroll: hmm. Will probably process it tomorrow eu morning. So you still have time to update it in the coming hours if you want | 21:05 |
| jroll | ttx: yeah, no rush, thanks | 21:05 |
| rockyg | ttx: have some questions from the tricircle team for release | 21:10 |
| *** dims has joined #openstack-release | 21:11 | |
| *** _amrith_ is now known as amrith | 21:11 | |
| * dims taking the con | 21:27 | |
| ttx | rockyg: about to call it a day. | 21:27 |
| ttx | rockyg: email ? Tricircle is not official so I guess they do what they want | 21:28 |
| *** TravT has joined #openstack-release | 21:28 | |
| dims | good night ttx | 21:28 |
| dims | i am back home from my day trip to boston | 21:28 |
| rockyg | Right. But they want to release and don't want to make waves. As part of the ecosystem | 21:28 |
| ttx | dims: good presentation ? | 21:28 |
| dims | ttx : y. students from BU and North Eastern (joint presentation with Amrith) | 21:29 |
| ttx | rockyg: sure, send me some email and I can do free consulting :) | 21:29 |
| * ttx disappears | 21:29 | |
| dims | lol | 21:29 |
| rockyg | So, 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 |
| rockyg | Will do ttx Thanks! | 21:29 |
| openstackgerrit | Merged openstack/releases: kilo: release python-openstackclient 1.0.5 https://review.openstack.org/295954 | 21:31 |
| dims | mriedem : do you review ironic stable branch releases? https://review.openstack.org/#/c/295965/ | 21:32 |
| patchbot | dims: patch 295965 - releases - ironic-python-agent 1.0.2 | 21:32 |
| openstackgerrit | Merged openstack/releases: Release designate 1.0.2 https://review.openstack.org/295527 | 21:32 |
| mriedem | dims: probably | 21:33 |
| *** daemontool has joined #openstack-release | 21:41 | |
| openstackgerrit | Merged openstack/releases: ironic-python-agent 1.0.2 https://review.openstack.org/295965 | 21:42 |
| dims | mriedem : one more from jroll - https://review.openstack.org/#/c/295966/ | 21:46 |
| patchbot | dims: patch 295966 - releases - ironic 4.2.3 | 21:46 |
| mriedem | good lord bindep dumps a lot of info | 21:47 |
| mriedem | have i complained about that yet to anyone? | 21:47 |
| mriedem | bindep and zuul cloner | 21:47 |
| dims | i've gotten used to zuul cloner...haven't had to look at bindep output yet :) | 21:48 |
| *** openstackgerrit has quit IRC | 21:48 | |
| mriedem | jroll: https://review.openstack.org/#/c/280072/ is a pretty shady backport | 21:48 |
| patchbot | mriedem: patch 280072 - ironic (stable/liberty) - Disable clean step 'reset_ilo' for iLO drivers by ... (MERGED) | 21:48 |
| mriedem | changes a config option default value in a backport to stable | 21:48 |
| mriedem | kind of a no-no | 21:49 |
| *** openstackgerrit has joined #openstack-release | 21:49 | |
| openstackgerrit | devdatta-kulkarni proposed openstack/releases: Tagging Solum mitaka releases https://review.openstack.org/296032 | 21:51 |
| mriedem | dims: -1 on that one, i asked about a few changes, so will wait to see what the justification is for those on stable/liberty | 21:55 |
| mriedem | config option changes and dependency updates | 21:55 |
| dims | mriedem : ack thanks! | 21:56 |
| *** mriedem has quit IRC | 21:58 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 22:02 | |
| *** johnsom has quit IRC | 22:08 | |
| openstackgerrit | Travis Tripp proposed openstack/releases: Release Searchlight Mitaka RC1 https://review.openstack.org/296089 | 22:18 |
| *** gordc has quit IRC | 22:32 | |
| *** rockyg has quit IRC | 22:57 | |
| jroll | dims: I replied to matt there but that could wait for tomorrow | 23:11 |
| *** dims_ has joined #openstack-release | 23:12 | |
| *** dims has quit IRC | 23:15 | |
| *** dims has joined #openstack-release | 23:15 | |
| openstackgerrit | Armando Migliaccio proposed openstack/releases: Neutron Mitaka RC2 deliverables https://review.openstack.org/295398 | 23:17 |
| *** dims_ has quit IRC | 23:18 | |
| *** dims_ has joined #openstack-release | 23:19 | |
| *** dims has quit IRC | 23:22 | |
| *** dims has joined #openstack-release | 23:23 | |
| *** dims_ has quit IRC | 23:25 | |
| *** kzaitsev_mb has quit IRC | 23:36 | |
| *** kzaitsev_mb has joined #openstack-release | 23:43 | |
| *** kzaitsev_mb has quit IRC | 23:54 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!