16:59:14 <colindixon> #startmeeting tsc
16:59:14 <odl_meetbot> Meeting started Thu Oct 23 16:59:14 2014 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:59:14 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:59:14 <odl_meetbot> The meeting name has been set to 'tsc'
16:59:21 <colindixon> #topic roll call and agenda bashing
16:59:29 <colindixon> #chair phrobb tbachman alagalah
16:59:29 <odl_meetbot> Current chairs: alagalah colindixon phrobb tbachman
16:59:35 <colindixon> #info colindixon
16:59:43 * tbachman cracks knuckles
16:59:53 <dmm> #info dmm
16:59:55 <regXboi> #info regXboi
16:59:55 * tbachman takes a drink of coffe
17:00:20 * regXboi notes he may do IRC more than phone today - hacking and coughing don't come through the IRC channel :)
17:00:53 <tykeal> *cough*hack*
17:00:54 <tykeal> ;)
17:01:04 <colindixon> #chair regXboi
17:01:04 <odl_meetbot> Current chairs: alagalah colindixon phrobb regXboi tbachman
17:01:12 <phrobb> #action colindixon to add irc channel information into TSC agenda on the wiki
17:01:21 <regXboi> phrobb: thanks
17:01:25 <kwatsen> #info Kent Watsen
17:02:01 * regXboi flexes fingers
17:02:46 <abhijitkumbhare> #info abhijitkumbhare (standing in for Chris Price)
17:02:53 <IvanWood> #info Ivan Wood
17:03:09 <colindixon> #link https://wiki.opendaylight.org/view/TSC:Main#Agenda the agenda
17:03:13 <tbachman> colindixon: thx
17:03:43 <regXboi> #topic action items from last meeting
17:04:00 <regXboi> #info pushing item 1 (testing of Helium on windows still assigned to LuisGomez phrobb and IvanWood) to a later date
17:04:32 <regXboi> #info looking for update on item 2 (gzhao to check on master branch version bumps) to that update
17:04:36 <tbachman> #info tykeal says that the sonar issues with the controller have been worked out
17:04:41 <dlenrow> #info dlenrow
17:05:02 <tbachman> #info tykeal solution was to cause it to garbage collect more often (spending too much time in garbage collection while talking to sonar)
17:05:07 <tbachman> #undo
17:05:07 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2534890>
17:05:14 <regXboi> #info tbachman's message covers items 3 and 4 (tykeal, zxiiro, and Tony T. to work off line on the Controller sonar issue and tykeal and ttkacik to work out what the next steps are to resolve this)
17:05:15 <cdub> #info Chris Wright
17:05:32 <edwarnicke> I am having some technical difficulties joining the webex
17:05:32 <tbachman> #info tykeal said the solution was to cause it to garbage collect more often (spending too much time in garbage collection while talking to sonar)
17:05:43 * cdub too
17:05:51 * tbachman waves to cdub and edwarnicke
17:05:59 <regXboi> and I've lost the thread because colindixon needs to slow down slightly
17:06:08 <tbachman> regXboi: this is nothin’
17:06:13 <regXboi> no kidding
17:06:14 <tbachman> he’s taking it easy on us right now
17:06:22 <tbachman> lol
17:06:32 * gzhao waves to edwarnicke
17:06:46 <abhijitkumbhare> edwarnicke - welcome back :)
17:06:46 <regXboi> edwarnicke: welcome back
17:06:58 <edwarnicke> abhijitkumbhare: Good to be back :)
17:07:37 <jmedved> #info jmedved
17:07:59 <colindixon> phrobb: recording?
17:08:02 <tbachman> mohnish: can you #info in?
17:08:10 <tykeal> I see it recording
17:08:13 <phrobb> colindixon:  yes
17:08:14 <tbachman> edwarnicke: can you #info in?
17:08:22 <tbachman> or did you already?
17:08:24 <regXboi> and away we go!
17:08:41 <edwarnicke> #info edwarnicke
17:08:44 <tbachman> #topic updates
17:08:47 <regXboi> therewe go :)
17:08:48 <edwarnicke> (now on the webex :) )
17:08:51 <tbachman> :)
17:08:51 <mohnish> #info joined the call
17:08:58 <regXboi> #topic board elections
17:09:06 <tbachman> mohnish: you usually do something like #info mohnish
17:09:11 <tbachman> (where #info is the first thing typed)
17:09:15 <mohnish> thanks
17:09:16 <edwarnicke> joined what?
17:09:17 <tbachman> np!
17:09:20 <mohnish> #info mohnish
17:09:28 <tbachman> mohnish: that’s it — thanks!
17:09:29 <alagalah> CAn anyone else hear phil ?
17:09:39 <alagalah> Cos I cannot
17:09:42 <regXboi> #info it sounds like we are in the middle of the process, but as I can't really hear phrobb it's difficult
17:09:44 <regXboi> #undo
17:09:44 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2848cd0>
17:10:08 <tbachman> #info In order to vote in the board elections you have to be a member of the non-profit, which requires submitting a form
17:10:14 * tbachman goes looking for email
17:10:15 <dlenrow> apparently phil is underwater while attending the meeting. Swimming laps?
17:11:14 <tbachman> #link https://lists.opendaylight.org/pipermail/tsc/2014-October/001945.html email from Phil Robb describing the process to submit
17:11:34 <regXboi> #topic update on events
17:12:00 <regXboi> #info dusseldorf SDN/OpenFlow world congess was a success
17:12:26 <regXboi> #info next week is a hackfest in Tokyo (next Wed to be precise)
17:12:46 <regXboi> #info openstack summit first work of Nov in Paris
17:12:55 <dmm> #info dmm will be at the openstack summit
17:12:55 * colindixon will not be at OpenStack
17:12:56 <tbachman> #info phrobb asks who’s participating in the OpenStack Summit
17:12:56 * cdub will be there
17:13:04 <gzhao> Helen and I will go to openstack
17:13:11 * regXboi will not be attending - too much to do here
17:13:23 <gzhao> #info Helen Chen and gzhao will attend openstack
17:13:43 <regXboi> #info regXboi will not be attending
17:13:44 <dlenrow> #info dlenrow @ OSSummit
17:13:50 <cdub> colindixon: we can't hear you
17:13:51 <regXboi> colindixon?
17:14:04 <tbachman> #info cdub, dmm, gzhao, Helen Chen, and dlenrow indicated they will be attending the OpenStack summit; colindixon and regXboi will not be attending
17:14:49 <dlenrow> +1 keep track of when community members show up at events
17:15:30 <tbachman> #info colindixon asks if there’s a simple mechanism for keeping track of who’s attending conferences
17:15:37 * edwarnicke refrains from suggesting chipping community members ;)
17:15:42 <kwatsen> self-signup on wiki?
17:15:54 <dlenrow> kwatson: Genius
17:15:57 <tbachman> #info abhijitkumbhare and kwatsen recommended doing this on a wiki
17:16:23 * tbachman can’t tell if dlenrow is referring to a web site, or paying kwatsen a compliment ;)
17:16:29 <dlenrow> alagala: Super genius (Wile E Coyote)
17:16:46 <tbachman> #topic System Integration and Testing
17:17:03 <tbachman> #info colindixon asks where we are with Windows testing and removing docker from the integration repo
17:17:29 <tbachman> #info LuisGomez says they’re still waiting for the master updating for version bumps
17:17:49 <tbachman> so, no windows, docker status?
17:18:42 <colindixon> did I lose audio?
17:18:47 <regXboi> the incredible random webex muting
17:18:48 <tbachman> colindixon: my webex just frozre
17:18:55 <tbachman> I can’t even unmute
17:18:55 <cdub> colindixon: if you are spekaing now, then yes
17:18:56 <tykeal> colindixon: I don't hear you
17:19:04 <tbachman> can anyone hear anyone on webex?
17:19:07 <tbachman> did it die on us?
17:19:07 <colindixon> I can’t hear anyone
17:19:13 <tykeal> tbachman: I hear LuisGomez
17:19:14 <kwatsen> seems like Luis can't hear us
17:19:17 <regXboi> webex isn't allowing me to unmute
17:19:18 <dlenrow> can't hear nobody
17:19:21 <IvanWood> I can hear Luis
17:19:21 <cdub> i can hear LuisGomez
17:19:22 <tbachman> regXboi: same
17:19:23 <abhijitkumbhare> I can hear LuisGomez
17:19:23 <regXboi> and I can't hear anything
17:19:31 <tbachman> we’re experiencing some fun :)
17:19:35 <dlenrow> can webex "host" unmute the world?
17:19:37 * colindixon is logging out and back in
17:19:46 <tbachman> just came back
17:19:58 <tbachman> we just lost like 2 mins
17:20:18 <dlenrow> tbachman: have to slip Lithium :)
17:20:24 <tbachman> dlenrow: lol
17:21:38 <phrobb> webex back for everyone?  I'm hearing Luis well
17:21:54 * zxiiro can hear
17:22:00 <abhijitkumbhare> dlenrow - slip by 2 min :)
17:22:47 <tbachman> #action LuisGomez will send an email indicating they will stop building the hydrogen release distributions in the future, with a timeline
17:24:24 <tbachman> #info LuisGomez asks how we handle working with events in other organizations (e.g. plugfests)
17:24:49 <tbachman> #info phrobb says we typically try to coordinate our activities, but it’s not required (i.e. helpful/valuable if we coordinate it)
17:24:55 * tbachman goes looking for email
17:25:15 <colindixon> http://www.criterionnetworks.com/events/onf-fall-2014-plugfest/
17:25:25 <tbachman> #link https://lists.opendaylight.org/pipermail/integration-dev/2014-October/001898.html email on plugfest
17:26:31 <tbachman> #info rexpugh says that HP is sponsoring the plugfest in Roseville
17:27:16 * tbachman hears edwarnicke’s voice for first time in a while
17:27:30 <tbachman> edwarnicke: welcome back!
17:27:40 <tbachman> #topic Stable Helium
17:27:57 <tbachman> #info First stability release scheduled for 11/10/2014
17:28:31 <tbachman> #info colindixon says that in order for the TSC to bless the release, ideally the artificacts would be cut by 11/6/2014
17:28:48 <tbachman> #info gzhao says that zxiiro sent an email about tagging the branch
17:29:02 <tbachman> #info gzhao says that the auto-release builds have been stable for last 4-5 days
17:29:27 <tbachman> #info gzhao recommends targeting a build around 10/28/2014 for integration to start testing
17:30:34 <abhijitkumbhare> #info abhijitkumbhare recommends testing for 1 week (have a build on Nov 3)
17:30:41 <tbachman> abhijitkumbhare: thx! :)
17:31:41 <tbachman> #info colindixon says that unless we want a special meeting on November 10th, cutting a release on November 3rd only allows 3 days for integration testing.
17:32:07 <tbachman> #info LuisGomez says the regular tests can be done in this time frame, but if we want to do some additional testing (e.g. performance), that might be tight
17:33:56 <tbachman> #action gzhao and LuisGomez to put together a plan for cutting and testing artifacts for  stable/helium
17:36:23 <abhijitkumbhare> #info abhijitkumbhare suggests having the stable release on a Thursday (either Nov 6 or 13) to coincide with the TSC meeting
17:36:37 <tbachman> #info gzhao says that the master branch versions have been bumped on all the projects, according to gerrit, but he noted that his build failed
17:36:47 <tbachman> #action LuisGomez to begin testing on bumped master
17:37:03 <tbachman> #action edwarnicke to help gzhao with getting auto-release on master un-stuck
17:38:01 * gzhao hopes he didn't screw up edwarnicke's lithium worker
17:38:04 <tbachman> #topic Creation Review for Release Engineering
17:38:21 <tbachman> #link https://wiki.opendaylight.org/view/Project_Proposals:Release_Engineering_-_Builder Wiki page for project proposal
17:38:36 <tbachman> #link #link https://lists.opendaylight.org/pipermail/project-proposals/2014-October/000159.html email proposing the project
17:38:39 <edwarnicke> gzhao: It is entirely possible my lithium worker wasn't working that great to begin with :)
17:39:04 <LuisGomez> gzhao, i think we need this merged to proceed with integration bump: https://git.opendaylight.org/gerrit/#/c/11856/
17:39:48 <tbachman> #info tykeal says their project is creating a build repository for keeping the CI jobs, so they can be versioned, reviewed, et.
17:40:26 <tbachman> #info colindixon asks if this repo is for non-LF employees, and can help with this effort
17:40:49 <gzhao> LuisGomez: ok, let me follow up with priyanka,
17:40:56 <tbachman> #info tykeal says they do intend to accept revisions to things, and are planning on doing this to help move everyone to a more scaleable setup
17:41:01 <rovarga> tykeal: are we also going to get a bit more visibility as to what's on the horizon?
17:41:09 <tbachman> #info colindixon asks if they would be open to committers outside the LF
17:41:29 <tbachman> #info tykeal says they’re open to this, but they want to make sure that new committers have a good understanding and committment to the project
17:42:54 <tbachman> #info colindixon asks if there’s a timeline for this
17:43:05 <tbachman> #info tykeal says that zxiiro has a lot of the basic jobs already designed
17:43:25 <tbachman> #info zxiiro says that he has 3 job templates — verify, merge, and daily
17:44:29 <tbachman> #info zxiiro says that there’s a single thing that new projects can use that creates these three templates
17:44:42 <tbachman> #info colindixon notes that integration is missing from this list
17:45:36 <tbachman> #info zxiiro says they just need a few projects to test the templates with, in order to verify their correctness
17:46:10 <tbachman> #info phrobb says they’re targeting the week of November 10th to complete this effort
17:46:48 <tbachman> #info tykeal says they received an email on whether this should be one big project with efforts underneath it, or whether it should be separate projects
17:47:05 <tbachman> #info tykeal says that the rel-eng heirarchy is related to anything for environmental needs
17:47:56 <tbachman> #info edwarnicke says you may want to consider a rel-eng top-level project, and use the life cycle feature
17:48:47 <tbachman> #info tykeal says there’s not a good way of saying “this is how it all fits together” — it’s best dealt with in “here’s how you do this piece"
17:49:55 * tbachman wonders where his scribe-partner-in-crime, regXboi, has gone too :(
17:50:16 * regXboi is having problems with webex
17:50:32 * regXboi notes he's only hearing half of everything said
17:50:34 <tbachman> #info rovarga asks if there will be something similar to a release plan to get an idea of what’s on the horizon
17:50:54 <cdub> that wouldnt' really make sense
17:51:12 <tbachman> #info tykeal says they aren’t planning on participating in a simultaneous release, but they will look into providing a release plan to assist developers
17:51:26 <rovarga> it actually would, as we need to align with project plans and need to see how our infrastructure is going to evolve
17:52:38 <tbachman> #info dlenrow notes that normally they’d look to see committer diversity, tho this is perhaps a special case
17:53:07 <tbachman> #info colindixon says that committer diversity is called out as a topic to be covered much after a creation review
17:53:54 <tbachman> #info mohnish says they want to find out more on how they do these pieces — will there be a wiki page describing this?
17:54:58 <tbachman> #info tykeal says they will definitely have documentation on how developers can add jobs this way, and will put this in their repository and wiki pages
17:55:38 <tbachman> #info zxiiro says their plan is to provide templates for the most common jobs (i.e. in their repo)
17:56:40 <tbachman> #info tykeal says that no one will have direct access to create jobs in jenkins, but will instead do this as part of the templates. This is b/c they’ve run into a lot of problems with projects creating their own jenkins jobs, so this will hopefully address some of those problems
17:58:43 <tbachman> #info regXboi expresses concern in being limiited to just these templates
17:59:03 <cdub> regXboi: i don't think you are precluded from doing your own
17:59:08 <cdub> regXboi: these are useful templates
17:59:33 <tbachman> #undo
17:59:33 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x284b910>
17:59:34 <tbachman> #undo
17:59:34 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x284b810>
17:59:57 <tbachman> #info tykeal says that no one will have direct access to create jobs in jenkins, but will instead do this as part of the UI provided This is b/c they’ve run into a lot of problems with projects creating their own jenkins jobs, so this will hopefully address some of those problems
18:00:47 <rovarga> regXboi: what are your concern with the proposed solution?
18:00:54 <tbachman> #info colindixon asks if the intent is to move projects to a single silo, or to recomend projects move to a single silo
18:01:19 <tbachman> #info tykeal says that they can’t force them to move to a single silo, but it’s their recommendation, and then they get the benefit of dependency triggers
18:01:22 <regXboi> rovarga: I actually want to see this in action for something *other* than the base three
18:02:57 <rovarga> regXboi: ah, right. I think the point is to provide the base three and evolve templates as more and more projects (like ovsdb) are integrated
18:03:08 <tbachman> #info regXboi would like to see documentation that helps them work outside of the 3 templates
18:04:09 <tbachman> #info edwarnicke points out that there is no mandate for people to follow these templates, and therefore is not an issue for the creation review for this project
18:04:28 <tbachman> #info tykeal says that if we don’t move to something like this, adding new projects is going to become more of a strain on our infrastructure
18:04:44 <phrobb> #startvote Shall the TSC approve the "Release Engineering - Builder" project to the "incubation" state? -1, 0, +1
18:04:44 <odl_meetbot> Begin voting on: Shall the TSC approve the "Release Engineering - Builder" project to the "incubation" state? Valid vote options are -1, 0, +1.
18:04:44 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:04:44 <cdub> yes, please!
18:04:51 <cdub> #vote +1
18:05:00 <dlenrow> #vote +1
18:05:07 <colindixon> #vote +1
18:05:16 <flaviof> #vote +1
18:05:22 <mohnish> #vote +1
18:05:24 <kwatsen> #vote +1
18:05:25 <regXboi> #vote +1
18:05:28 <IvanWood> #vote +1
18:05:33 <abhijitkumbhare> #vote +1
18:05:38 <edwarnicke> #vote +1
18:05:40 <phrobb> #endvote
18:05:40 <odl_meetbot> Voted on "Shall the TSC approve the "Release Engineering - Builder" project to the "incubation" state?" Results are
18:05:40 <odl_meetbot> +1 (10): flaviof, dlenrow, regXboi, edwarnicke, cdub, mohnish, kwatsen, colindixon, abhijitkumbhare, IvanWood
18:05:42 <tbachman> #info The belief of the TSC is that participation in the rel-eng project hasn’t been agreed to be mandatory
18:05:43 <dmm> #vote +1
18:05:49 <tbachman> dmm: just missed!
18:05:59 <tbachman> #info edwarnicke weeps tears of joy
18:06:09 <cdub> tykeal: huzzah!
18:06:10 <tbachman> tykeal: zxiiro congrats! :)
18:06:26 <cdub> zxiiro: huzzah!
18:07:50 <tbachman> #topic Lithium Release Plan
18:07:52 <tykeal> :)
18:08:24 <regXboi> edwarnicke: surprise!
18:08:33 <dlenrow> #info If current proposal is that we don't require commiter diversity at project creation (when there is greatest risk of land grab via special status of "appointed, not merit based" commiter approval at project creation)  then I want to discuss the merits of that proposal more. Future agenda?
18:09:37 <tbachman> #info colindixon says that we need to vote today for the last call for projects for Lithium
18:09:55 <tbachman> #info edwarnicke prefers we say the “soonest the last call can occur”
18:10:46 * tbachman sets stopwatch
18:10:48 * regXboi sets his alrarm
18:11:04 <regXboi> #link https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Lithium_Release_Plan_ckd draft LI plan
18:11:10 <tbachman> regXboi: thx!
18:11:22 <regXboi> tbachman: I can hear people again now
18:11:36 * tbachman hopes it’s the TSC call regXboi can hear ;)
18:11:45 <cdub> i haven't read it, can you highlight what is fundamentally different?
18:11:47 <edwarnicke> regXboi: hearing voices again?
18:12:42 <cdub> colindixon: ^^
18:12:43 <regXboi> edwarnicke: webex drops in and out, which makes scribing .... interesting :)
18:13:15 <tbachman> #info colindixon asks if all the TSC members have had a chance to read the release plan
18:13:31 <tbachman> #info cdub asks for the high-level differences (Cliffs Notes :) )
18:13:32 <dlenrow> fast flyby from author(s) would be good
18:13:40 <regXboi> #info answer is that we are going to have a flyby from Colin
18:14:42 <tbachman> #info the first thing is that there
18:14:44 <tbachman> #undo
18:14:44 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x274a450>
18:15:13 <tbachman> #info colindixon covers the definitions
18:15:28 <tbachman> #info Legacy APIs are assumd to be frozen for the duration of the Lithium Release
18:15:50 <tbachman> #info a Provisional API is one that is there but could be modified in the Lithium Release
18:16:33 <tbachman> #info Tentative APIs are APIs which may or may not be part of the final release
18:17:04 <tbachman> #info The release plan template covers things like expected dependencies on other projects
18:17:31 <tbachman> #info There’s also a section on what other projects need from this project, which should be filled out by the depending projects
18:17:45 <cdub> aka "send patches"
18:18:47 <tbachman> #info colindixon says that these dependencies should only apply for provisional APIs, and not for Legacy APIs
18:19:10 <tbachman> #info regXboi asks if we call out the definition of APIs for API freeze
18:19:18 <regXboi> #undo
18:19:18 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x269ecd0>
18:19:28 <regXboi> #info regXboi points out that we do call out the definition of APIs
18:19:31 <regXboi> :)
18:19:32 <tbachman> :)
18:20:23 <cdub> can you #link these as you show them
18:20:34 <cdub> colindixon: and you #link these as you show them?
18:20:56 <tbachman> cdub: you want the links he’s clicking on?
18:20:59 * tbachman can try to keep up
18:21:10 <cdub> yes
18:21:11 <tbachman> k
18:21:35 <cdub> tbachman: thanks
18:21:37 <tbachman> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Release_Schedule_Framework Framework for the release
18:21:43 * tbachman missed what colindixon asked
18:22:30 <phrobb> #action colindixon to ensure all bullets from "schedule framework" are indicated in the schedule for Lithium
18:22:31 <tbachman> colindixon: fwiw, there’s a link on that page, “Formal Lithium Release”, that isn’t being shared
18:22:33 <tbachman> phrobb: thx
18:22:54 <regXboi> phrobb beat me to it
18:23:07 <tbachman> #link https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Release_Plan_2014_Template Release Plan Template
18:24:08 <tbachman> #info The idea behind functionality freeze is that the APIs should be in some “Beta” functionality, so that dependent projects could have a sense of what APIs they can use and test against
18:25:58 <tbachman> #info colindixon says we should show projects how to prevent exporting their APIs
18:27:27 <tbachman> #info Code Freeze has pretty much the same meaning as in Helium
18:27:42 <regXboi> I didn't hear that question?
18:27:44 <tbachman> #info mohnish asks what if there’s a feature that has to be dropped at Code Freeze, for some reason
18:28:31 <tbachman> #info colindixon says you can drop functionality or delay a release, but this depends on what offset your project is on
18:28:38 * tbachman isn’t sure he got that right
18:29:27 <tbachman> #info edwarnicke asks if there’s been some integration points added to the release plan
18:29:34 <regXboi> tbachman: close enough
18:29:51 <tbachman> #info colindixon says that M2 and M3 address this
18:29:59 <tbachman> regXboi: thx
18:30:35 * tbachman notes there’s a lot of “we’d like to see” that’s not covered by the plan
18:30:57 <tbachman> #info edwarnicke says that handing a
18:30:58 <tbachman> #undo
18:30:58 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x28387d0>
18:31:38 <tbachman> #info colindixon says that as part of M2, he’d like to see the TSC perform release plan reviews, which would include possible pushback from projects indicating something isn’t reasonable
18:32:57 <tbachman> #info The Release Candidate definition says that you can’t spin the next RC until all the bugs in the current RC have been fixed
18:33:25 <tbachman> #info Intermediary RC’s can be created to allow RCs in between the (major) RCs to address such bugs
18:33:53 <tbachman> wasn’t there a continuous release/build proposed by dlenrow ?
18:33:58 <tbachman> (or was it rovarga?)
18:34:23 <tbachman> #info rovarga proposes that we should shoot for continuous release/delivery
18:34:32 <tbachman> #info colindixon says we’d like to get there, but maybe not with this release
18:35:08 <tbachman> #action colindixon to edit Lithium Relelase plan that we will continue to cut RCs to address bugs and create the release
18:35:19 <regXboi> tbachman: beat me to it again :)
18:35:24 <tbachman> lol
18:35:59 <tbachman> #info jmedved says we should continue cutting RCs, but there needs to be a deadline
18:36:03 <cdub> spin RC's until we're good has one drawback, which is there's little external visbility
18:36:25 <tbachman> #info colindixon says he’ll probably leave the RCs in the plan to provide such deadlines
18:37:16 <regXboi> AMEN
18:37:56 <tbachman> #info colindixon says that the full project graph as of today is at least 8 layers deep, and having 7 offsets is untenable
18:38:24 <tbachman> #info The release plan collapses this into 3 leves — offset 0, 1, and 2
18:38:45 <tbachman> #info The intent is a 2 week gap between offset for code deliverables, and a 1 week gap between offsets for non-code deliverables
18:39:54 <tbachman> #info edwarnicke asks how the offsets might work with continuous delivery
18:40:28 <tbachman> #info rovarga says that the key with continuous delivery is getting the key infrastructure off the ground; if we can get that in place by M2, then we probably can do this with continuous delivery
18:40:54 <tbachman> #info colindixon says he’s a bit skeptical, and would like to see a small set of projects start out with continuous delivery first, and then migrate the others
18:40:55 <dlenrow> #info My recommendation that we essentially exclude the offset 2 projects (leaves) from the SR is on record, I assume I don't need to restate on this call.
18:41:06 <tbachman> #info rovarga says that the problem with that approach is version skew
18:42:33 <tbachman> #info abhijitkumbhare says that we probably need an explicit test cycle in order to say that the release is good
18:42:56 <tbachman> #info colindixon says that the time between M5 and the RCs is essentially the test cycle
18:44:53 <tbachman> #link https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Lithium_Release_Plan_ckd#Requirements_for_Participation requirements for participation in Lithium
18:45:36 <tbachman> #info Projects need a Project Lead, elected by the project committers
18:46:14 <tbachman> #info Project Leads need to be responsive to release related communications (i.e. 48-hr response time, when emails sent indicating a response is required)
18:47:28 <tbachman> #info Service Release participation is now mandatory
18:47:42 <tbachman> #info Projects are also now required to report testing results to sonar
18:49:05 <tbachman> #info rovarga would like to see a requirement on code quality added
18:50:09 <tbachman> #info abhijitkumbhare asks if the sonar reporting is required for mature projects
18:50:19 <tbachman> #info colindixon says that sonar reporting is for all projects
18:50:49 <abhijitkumbhare> actually I wanted to say whether sonar reporting was also required for the new projects
18:51:07 <tbachman> #undo
18:51:07 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2728450>
18:51:08 <tbachman> #undo
18:51:08 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2728c10>
18:51:18 <tbachman> #info abhijitkumbhare asks if sonar reporting was also required for new projects
18:51:35 <tbachman> #info colindixon saysa that sonar reporting is required for all projects participating in the Simultaneous Release
18:51:52 <jmedved> jmedved seconds rovarga’s requirement
18:52:05 <jmedved> (can’t get to say it on the call)
18:52:20 <tbachman> #link https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist Wiki page for new project checklist
18:52:37 <abhijitkumbhare> I actually second colindixon requirements
18:53:04 * tbachman wasn’t sure who to action there
18:53:38 <tbachman> colindixon: 7 minutes
18:53:51 <jmedved> did we agree on anything re: sonar requirements?
18:54:05 <tbachman> jmedved: colindixon wanted to action someone on that
18:54:09 <tbachman> to bring it to closure
18:54:12 <tbachman> just wasn’t sure who :(
18:54:25 <tbachman> volunteers? :)
18:54:32 <jmedved> and what was the closure?
18:55:00 <tbachman> not sure, but I think that was the intent of the action (i.e. figure out what to do)
18:55:03 <jmedved> do we require it for all projects or not? (for a project to participate in simultaneous release)?
18:55:32 <tbachman> jmedved: we’ll ask it again on the call, after colin gets the vote that he wants for project proposals
18:57:04 <tbachman> #info cdub asks if it’s implicit on whether projects from previous releases are in the Lithium release
18:57:20 <tbachman> crumbs
18:57:21 <tbachman> missed that
18:57:47 <tbachman> #info abhijitkumbhare points out that most new projects are likely to be at offset 2
18:58:06 <tbachman> #info dlenrow says we should exclude offset 2 projects from the simultaneous release
18:58:21 <tbachman> #info regXboi says that before we do that, we need to have a proposal on how those projects would get released
18:58:45 <phrobb> #startvote Shall the TSC specify the soonest that the "Last Call for new projects to be eligible to join" the Lithium Release to be November 7th, 2014, for offest 0, November 20th, 2014 for offset 1, and November 28th, 2014 for offset 2? -1, 0, +1
18:58:45 <odl_meetbot> Begin voting on: Shall the TSC specify the soonest that the "Last Call for new projects to be eligible to join" the Lithium Release to be November 7th, 2014, for offest 0, November 20th, 2014 for offset 1, and November 28th, 2014 for offset 2? Valid vote options are -1, 0, +1.
18:58:45 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:59:41 <phrobb> #endvote
18:59:41 <odl_meetbot> Voted on "Shall the TSC specify the soonest that the "Last Call for new projects to be eligible to join" the Lithium Release to be November 7th, 2014, for offest 0, November 20th, 2014 for offset 1, and November 28th, 2014 for offset 2?" Results are
19:00:04 <regXboi> #action colindixon to clarify language around project proposals in draft schedule
19:00:05 <mohnish> #vote +1
19:00:06 * tbachman was going to do that
19:00:26 <mohnish> :-)
19:01:02 <phrobb> irc://irc.freenode.net:6667/#startvote Shall the TSC specify the soonest that the "Last Call for new projects to be  proposed"  to be allowed into the Lithium Release to be November 7th, 2014, for offest 0, November 20th, 2014 for offset 1, and November 28th, 2014 for offset 2? -1, 0, +1
19:01:04 <abhijitkumbhare> #vote +1
19:01:08 <mohnish> #vote +1
19:01:14 <colindixon> #startvote Shall the TSC specify the soonest that the "Last Call for new projects to be  proposed"  to be allowed into the Lithium Release to be November 7th, 2014, for offest 0, November 20th, 2014 for offset 1, and November 28th, 2014 for offset 2? -1, 0, +1
19:01:14 <odl_meetbot> Begin voting on: Shall the TSC specify the soonest that the "Last Call for new projects to be  proposed"  to be allowed into the Lithium Release to be November 7th, 2014, for offest 0, November 20th, 2014 for offset 1, and November 28th, 2014 for offset 2? Valid vote options are -1, 0, +1.
19:01:14 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
19:01:20 <cdub> #vote +1
19:01:20 <colindixon> #vote +1
19:01:21 <dlenrow> #vote +1
19:01:21 <dmm> #vote +1
19:01:26 <edwarnicke> #vote +1
19:01:28 <regXboi> #vote +1
19:01:30 <mohnish> #vote +1
19:01:32 <jmedved> #vote +1
19:01:32 <abhijitkumbhare> #vote +1
19:01:35 <IvanWood> #vote +1
19:01:53 <phrobb> #endvote
19:01:53 <odl_meetbot> Voted on "Shall the TSC specify the soonest that the "Last Call for new projects to be  proposed"  to be allowed into the Lithium Release to be November 7th, 2014, for offest 0, November 20th, 2014 for offset 1, and November 28th, 2014 for offset 2?" Results are
19:01:53 <odl_meetbot> +1 (10): dlenrow, jmedved, regXboi, dmm, edwarnicke, cdub, mohnish, colindixon, abhijitkumbhare, IvanWood
19:02:04 <regXboi> #action colindixon to add requirement for projects to report sonar testing results (i.e. fine bugs) as part of project review for participation in SR
19:02:10 <tbachman> regXboi: thx!
19:03:19 <regXboi> we done?
19:03:44 <phrobb> #agreed the vote on dates for new projects to Lithium above is approved
19:03:48 <phrobb> #endmeetiong
19:03:48 <tbachman> #endmeeting