Monday, 2015-11-23

*** smcginnis has quit IRC03:03
*** smcginnis has joined #openstack-release03:05
*** aukhan has joined #openstack-release04:05
openstackgerritTony Breeds proposed openstack/releases: Add a warning for new mitaka releases of oslo.messaging  https://review.openstack.org/24853005:35
openstackgerritTony Breeds proposed openstack/releases: Add a warning for new mitaka releases of oslo.messaging  https://review.openstack.org/24853005:36
*** jhesketh has quit IRC06:31
*** jhesketh has joined #openstack-release06:34
*** ifat_afek has joined #openstack-release07:11
*** openstack has joined #openstack-release07:18
-cameron.freenode.net- [freenode-info] channel trolls and no channel staff around to help? please check with freenode support: http://freenode.net/faq.shtml#gettinghelp07:18
*** dtantsur|afk is now known as dtantsur09:09
*** ifat_afek has quit IRC09:54
*** flaper87 has quit IRC10:46
*** flaper87 has joined #openstack-release10:46
*** aukhan has quit IRC11:04
*** ifat_afek has joined #openstack-release11:13
openstackgerritMerged openstack/releases: Document an EOL and release dates  https://review.openstack.org/24767711:58
*** gordc has joined #openstack-release12:31
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Oslo releases for week of Nov 23, 2015  https://review.openstack.org/24839113:06
*** armax has joined #openstack-release13:06
*** armax has quit IRC13:10
*** doug-fish has joined #openstack-release13:25
ttxdhellmann: question for you. Someone asked where/if we maintain a list of development deadlines (the common ones and the project-specific ones) for other communities to more easily coordinate with us. Something that would list the Cinder driver proposal mitaka deadline or the Nova spec mitaka deadline. I was considering creating a new wiki page for teams to dump that but suddenly wondered if we13:33
ttxshould not somehow reuse the official page (for things following the cycle at least)13:33
ttxI see two potential issues: vandalism on the reference information there (which used ot be protected by admin rights), and accidental display glitches as the syntax on that table is a bit messy. One middle way would be to add the project-specific deadlines as paragraphs below the main table13:36
jrollttx: we could move that page to somewhere on docs.o.o, for the sake of code review (and it's prettier!)13:41
ttxwe could/should (we try to remove all reference information from the wiki)13:42
ttxI guess we could make that a part of docs.openstack.org/releases13:43
jrollthat seems like the right place for it, yeah :)13:43
*** bswartz has quit IRC13:53
openstackgerritGraham Hayes proposed openstack/reno: Add deprecations section to release notes  https://review.openstack.org/24770414:08
*** amotoki_ has joined #openstack-release14:09
*** amotoki has quit IRC14:12
*** amotoki_ is now known as amotoki14:12
*** bswartz has joined #openstack-release14:21
dhellmannttx, jroll : I like the idea of moving the schedule over to the releases repo and then encouraging teams to add their own dates to the schedule14:27
*** superdan is now known as dansmith14:35
*** mriedem has joined #openstack-release14:38
*** mriedem has quit IRC14:52
*** mriedem has joined #openstack-release14:57
*** openstackgerrit has quit IRC15:02
*** openstackgerrit has joined #openstack-release15:02
*** Daviey_ is now known as Daviey15:43
xylan_kongdhellmann: hi, do we need to cherry pick the adding reno changes to stable branch? or just add something like https://review.openstack.org/#/c/241322/ in Glance?15:48
dhellmannxylan_kong : originally I thought we just needed the note, but then we decided we needed to run the release notes build job on the stable branch too so we don't commit notes there that break the build on the master branch. So, please backport the tox.ini and other changes to add the release notes build *and* add an initial note15:53
dhellmannxylan_kong : I've documented this more clearly in a patch to the project team guide: https://review.openstack.org/#/c/244279/15:54
xylan_kongdhellmann: ok, got it, thanks for the info15:56
dhellmannxylan_kong : sure, sorry the initial instructions were a little confusing15:56
xylan_kongdhellmann: that's fine, beginning is always the most difficult stage for perfect15:57
xylan_kong:-)15:57
dhellmann:-)15:58
ttxdhellmann: I like the idea too16:04
ttxdhellmann: I just fear that will delay the info being accessible16:04
ttxbut I guess that can be done reasonably fast. And I might need a weekend project to keep busy while you're hurting turkeys16:05
*** armax has joined #openstack-release16:09
*** gordc has quit IRC16:47
*** gordc has joined #openstack-release16:51
dhellmannttx: actually, we have some paté for thanksgiving this year instead of cooking turkey for just the 2 of us ;-)16:52
*** dtantsur is now known as dtantsur|afk17:47
*** AJaeger has joined #openstack-release18:03
AJaegerdhellmann: do you have a few minutes to discuss your reno change?18:03
*** armax has quit IRC18:10
dhellmannAJaeger : sure18:13
AJaegerdhellmann: I'm looking at http://git.openstack.org/cgit/openstack/reno/tree/reno/utils.py#n2618:13
openstackgerritDoug Hellmann proposed openstack/reno: add complex formatting example  https://review.openstack.org/24886118:14
dhellmannAJaeger : ok18:14
AJaegerDon't the try and except return different types?18:14
AJaegerThis is unrelated to your change 246583, so I'll change my -1 to a +2 now ;) Just wanted that to have looked at...18:15
dhellmannAJaeger : you are right for python3, they do seem to return different t ypes18:16
*** ifat_afek has quit IRC18:16
dhellmannpython 2 always returns a str() but python 3 try returns a byte string and the except clause returns unicode18:16
AJaegerdhellmann: Do you want to patch this as part of 246583?18:17
dhellmannyeah, let me work on that18:17
AJaegerI wasn't completely sure whether those are different, thanks for confirming it18:17
AJaegerdhellmann: btw. the release-notes post job was broken for stable branches, jeblair, clarkb, and myself discused Friday a fix: https://review.openstack.org/#/c/248256/18:19
AJaegerright now, it will just fail on stable branches but once that is in, it publishes there as well...18:19
dhellmannAJaeger : ok, thanks for fixing that18:19
dhellmannAJaeger : I'm going to go find some lunch, but I'll work on that reno fix again this week18:20
AJaegerdhellmann: then let me remove my +2 again;)18:21
AJaegerEnjoy lunch!18:21
AJaegerdhellmann: did you see the nova discussion on Friday about https://review.openstack.org/#/c/247705/1 ? That release-note was badly formatted and looked really ugly. Having a good way to check formatting would be great - but I have no idea right now and wonder if it's possible at all.18:27
dhellmannAJaeger : https://review.openstack.org/24886118:28
dhellmannAJaeger : yeah, it's possible, you just have to escape the rst18:28
AJaegerthanks, dhellmann, I'll check..18:30
*** mriedem has left #openstack-release18:42
*** mriedem has joined #openstack-release18:43
mriedemdhellmann: what do you think about integrating reno with client libraries, like novaclient and glanceclient? good/bad idea based on the branch model? seems it could be done as long as applying release notes against tags rather than branches19:08
mriedemi noticed that novaclient's changelog is super stale19:09
openstackgerritFabio Giannetti proposed openstack/releases: Add Monasca to the Kilo deliverables  https://review.openstack.org/24888219:16
openstackgerritDoug Hellmann proposed openstack/reno: scan all changes and filter on files in reno not git log  https://review.openstack.org/24658419:17
openstackgerritDoug Hellmann proposed openstack/reno: add verbose and quiet options to command line for debugging  https://review.openstack.org/24658219:17
openstackgerritDoug Hellmann proposed openstack/reno: force the right return type for mocked urandom  https://review.openstack.org/24658319:17
dhellmannmriedem : I anticipated that we would use it for the clients, too.19:17
dhellmannAJaeger : ^^19:17
dhellmann(for the patches)19:17
AJaegermriedem: I'm using it for openstack-doc-tools already - not a client, just a library...19:18
openstackgerritDoug Hellmann proposed openstack/reno: add complex formatting example  https://review.openstack.org/24886119:19
AJaegerdhellmann: looks fine now, thanks! ttx, do you want to approve 246583 now?19:30
dhellmannAJaeger : thanks19:30
openstackgerritFabio Giannetti proposed openstack/releases: Add Monasca to the Kilo deliverables  https://review.openstack.org/24888219:39
openstackgerritMerged openstack/releases: release keystonemiddleware 1.5.3 for stable/kilo  https://review.openstack.org/24755319:51
*** dims has joined #openstack-release19:56
openstackgerritDoug Hellmann proposed openstack/releases: Add a warning for new mitaka releases of oslo.messaging  https://review.openstack.org/24853019:57
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Oslo releases for week of Nov 23, 2015  https://review.openstack.org/24839120:15
*** armax has joined #openstack-release20:22
dimsdhellmann : yes, the classifiers do not have 2.6 now20:24
dimsdhellmann : https://review.openstack.org/#/c/248391/20:24
dhellmanndims : ok, cool20:24
dhellmanndims : harlowja also had questions about the versions there, did you work that out?20:24
dimsthanks, i'll dropped taskflow and tooz per harlowja. i'll get started on that in a bit20:24
dimsy20:24
dhellmannk20:26
dimslet me check on zuul and gate status before i roll these out :)20:27
*** gordc has quit IRC20:30
openstackgerritDoug Hellmann proposed openstack/releases: add release notes links  https://review.openstack.org/24889920:34
openstackgerritDoug Hellmann proposed openstack/releases: add release notes links  https://review.openstack.org/24889920:58
*** AJaeger has quit IRC21:03
openstackgerritJoshua Harlow proposed openstack/releases: Tooz and taskflow releases for week of Nov 23, 2015  https://review.openstack.org/24891021:04
*** krotscheck has quit IRC21:10
*** andreaf has quit IRC21:11
*** anteaya has quit IRC21:11
*** vipuls has quit IRC21:12
*** krotscheck has joined #openstack-release21:17
*** andreaf has joined #openstack-release21:19
*** vipul has joined #openstack-release21:19
*** anteaya has joined #openstack-release21:27
openstackgerritMerged openstack/releases: Oslo releases for week of Nov 23, 2015  https://review.openstack.org/24839121:31
*** david-lyle has quit IRC21:31
*** david-lyle has joined #openstack-release21:34
*** dims_ has joined #openstack-release21:43
*** dims has quit IRC21:44
*** kzaitsev_mb has joined #openstack-release21:48
*** bswartz has quit IRC21:49
kzaitsev_mbI'm still a bit confused — whether I should add reno to murano-dashboard/client/agent or whether I should just keep it all the notes in murano itself. Sry for bringing it up again, but what is the best way to do it? (I've noticed, that none of the client repos still have reno configured =/)21:51
*** jhesketh has quit IRC21:55
*** david-lyle has quit IRC21:55
*** jhesketh has joined #openstack-release21:55
*** david-lyle has joined #openstack-release22:03
openstackgerritBrant Knudson proposed openstack/releases: keystonemiddleware 2.3.2 (liberty)  https://review.openstack.org/24892622:03
*** david-lyle has quit IRC22:04
dhellmannkzaitsev_mb : each deliverable should have its own release notes22:10
dhellmannkzaitsev_mb : I'll be sending another reminder this week about client releases and adding reno there22:10
kzaitsev_mband deliverable is something that get's packaged, right?22:11
dhellmannkzaitsev_mb : things that share a version number and are released together, even if in separate packages22:11
dhellmannso you might have one for murano & the dashboard, and a separate one for the client22:11
dhellmannor those might be 3 different deliverables, if you release them separately22:12
dhellmannmake sense?22:12
dhellmannkzaitsev_mb : I don't see a "murano" deliverable in the releases repository, so I don't know whether that's part of a multi-repo deliverable or if it was just not recorded22:15
kzaitsev_mbmurano itself and it's dashboard do share its versions, although with the new release system we might be releaseing them more or less separately, so I guess separate release notes would make sense22:16
kzaitsev_mbdhellmann: I guess I should fix that ommission22:17
dhellmannkzaitsev_mb : yeah, I'm not sure why it wasn't included. Possibly because it wasn't managed by the release team, before.22:18
*** david-lyle has joined #openstack-release22:21
openstackgerritBrant Knudson proposed openstack/releases: keystonemiddleware 2.3.2 (liberty)  https://review.openstack.org/24892622:21
openstackgerritBrant Knudson proposed openstack/releases: keystonemiddleware 2.3.2 (liberty)  https://review.openstack.org/24892622:23
kzaitsev_mboh, yeah, now everything makes a lot more sense =)22:24
*** david-lyle has quit IRC22:25
kzaitsev_mbI'll also update the list with 1.0.1 release, as I probably should have done long ago.22:25
*** armax has quit IRC22:30
*** mriedem is now known as mriedem_away22:46
*** dims_ has quit IRC22:55
*** amotoki has quit IRC22:58
*** david-lyle has joined #openstack-release23:03
*** david-lyle has quit IRC23:05
*** doug-fish has quit IRC23:17
*** david-lyle has joined #openstack-release23:23
*** dims_ has joined #openstack-release23:25
*** david-lyle has quit IRC23:25
*** dims_ has quit IRC23:26
*** jhesketh has quit IRC23:31
*** josh6627 has joined #openstack-release23:31
*** david-lyle has joined #openstack-release23:35
*** josh6627 has quit IRC23:35
*** jgriffith is now known as jgriffith_away23:38
*** david-lyle has quit IRC23:41
*** david-ly_ has joined #openstack-release23:41
*** armax has joined #openstack-release23:47

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