#opendaylight-meeting: tsc
Meeting started by colindixon at 17:00:12 UTC
(full logs).
Meeting summary
- agenda bashing and roll call (colindixon, 17:00:18)
- colindixon (colindixon,
17:00:27)
- https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=37287#Agenda
the agend in it's usual plce (colindixon,
17:00:34)
- https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-10-01-16.59.html
last week's meeting minutes (colindixon,
17:01:19)
- ACTION: colindixon to
try to find somebody to help with documenting the general procedure
for the platform upgrade from Helium to Lithium (for SR3)
https://bugs.opendaylight.org/show_bug.cgi?id=3160 (colindixon,
17:01:37)
- ACTION: colindixon to
reach out to the advisory gorup for input on Boron (colindixon,
17:01:55)
- Daniel Farrell (dfarrell07,
17:02:09)
- edwarnicke (edwarnicke,
17:03:05)
- Chris Price (for him since I undid it)
(colindixon,
17:03:08)
- mohnish anumala (mohnish_,
17:03:12)
- TSC at-large Elections (colindixon, 17:06:10)
- colindixon describes the Board meeting held
last night. Much discussion on the vote for the (phrobb,
17:07:27)
- LuisGomez (LuisGomez,
17:07:36)
- The Board felt that the waver was going to be
approved indef if we don't come up with a better solution
(dfarrell07,
17:08:11)
- waiver to allow Platinum designates to remain
on TSC if/when other employees from the same company join the
TSC (phrobb,
17:08:20)
- edwarnicke asks were any thoughts from the
Board given? (phrobb,
17:09:05)
- colindixon notes that the Board felt that as
long as platinum designates exist, the waiver will be needed. So
finding ways to get rid of Platinum designates would be
helpful (phrobb,
17:09:53)
- edwarnicke asks do we have a sense of what a
"minimal viable size" for the TSC?... the answer is "no" a minimum
size was not discussed (phrobb,
17:10:26)
- colindixon and edwarnicke not that "2 is too
small and 18 is too big" (phrobb,
17:11:10)
- Phil or Neela will launch a thread to discuss
this and possibly form a workgroup made up from Board and TSC
members (phrobb,
17:12:29)
- Delaying the election process by 30 days
doesn't cause a legal problem, says legal people (dfarrell07,
17:12:36)
- events (colindixon, 17:13:56)
- https://www.opendaylight.org/global-events
the events page as usual (colindixon,
17:14:13)
- SDN OF world congress in dusseldorf next
week (colindixon,
17:14:26)
- hackfest near SF on 11/9 and 11/10, currently
have 72 registered people, maxes out a 130, so register (colindixon,
17:15:10)
- https://wiki.mef.net/display/LH/MEF+LSO+Hackathon
LSO hacakathon in Dallas on 11/16 (colindixon,
17:15:31)
- http://regonline.com/ODLHackfest2015
Hackfest reg site (dfarrell07,
17:15:32)
- Beryllum (colindixon, 17:15:53)
- we have 5 outstanding M3 readouts: l2swich,
neutron, snmp, snmp4sdn, and yang-push (colindixon,
17:16:32)
- regXboi (ryant moats) notes that the neutron
delay was because of other fires from upstream hurting them
(colindixon,
17:17:04)
- anipbu is noting that we have started removing
projects from beryllium from auto-release when they are blocking
progress in addition to notifiying them of the issue (colindixon,
17:18:52)
- edwarnicke asks if we're removing projects from
integration/distribution as well because it will fail to build if
artifacts it dpeends on aren't built as part autorelese (colindixon,
17:19:32)
- colindixon notes that breaking autorelease
should be similar to projects as if they couldn't run mvn and should
treat it as such when helping out to fix things (colindixon,
17:21:42)
- https://wiki.opendaylight.org/view/Weather#Current_Weather_Report
external version upgrades are coming over time, look at weather here
for more information (colindixon,
17:22:45)
- regXboi begs people to test everything first,
and he notes that Eclipse 2.6.0 persistence broke things
(colindixon,
17:23:20)
- https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1314869162
(anipbu,
17:23:23)
- https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1314869162
anipbu notes that Steven has been building locally to see how
patches affect all projects for external dependencies (colindixon,
17:24:00)
- edwarnicke asks if we have a way to test this
automatically, colindixon says we do for single patches (colindixon,
17:24:38)
- https://nexus.opendaylight.org/content/sites/site/org.opendaylight.releng.builder/master/jenkins.html#Patch_Test_Job
this works for single patches, but this doesn't work for parten poms
around odlparent since parent poms are included at build time, not
assembly time (colindixon,
17:25:45)
- rovarga says that we could move the odlparent
dependency managment to an artifacts-style pom which could then be
imported into other proejcts, this would mean that we could change
versions at assembly time, not build time, which would allow the
patch test job to work (but not for properties) (colindixon,
17:28:31)
- for what it's worth if you get old versions if
you pull in external bundles by version in karaf features.xml,
instead odlparent could publish them as features as well
(colindixon,
17:29:51)
- ACTION: anipbu to
work with others (stephen kitt?) to see if we can get this done,
move odlparent dependency managment to an artifacts pom, move away
from odlparent properties, and make third party bundles features in
odlparent (colindixon,
17:32:30)
- regXboi asks when we push go for an upgrade
based on anipbu's spreadsheet above (colindixon,
17:35:23)
- anipbu says that all projects with breakages
are contacted and when to proceed is based on people's
responses (colindixon,
17:38:48)
- LuisGomez asks what about projects with not
enough system tests (colindixon,
17:38:54)
- LuisGomez asks if we need to get all projects
to vote +1 on a new patche to merge it, colindixon says that with 50
projects and the numer of external versions we need to ugrade, we
don't have time to take a week to collect feedback from each
project (colindixon,
17:40:28)
- rovarga notes that the changes to odlparent are
likely to have to wait until Boron because offset 0 M4 is a week
from now (colindixon,
17:42:44)
- regXboi asks if we should have a designed time
between releases to line up the new build chains and things like
like that before the major development happens (colindixon,
17:43:23)
- Isaku Yamahata to committer for Neutron Northbound (colindixon, 17:44:52)
- https://git.opendaylight.org/gerrit/#/q/project:neutron
patch sets (colindixon,
17:45:17)
- he is #2 committer in terms of patch sets in
last 90 days and has been handling a lot of testing and bug
fixing (colindixon,
17:45:39)
- VOTE: Voted on "shall
the TSC confirm Isaku Yamahata as a committer for Neutron
Northbound?" Results are, +1: 7 (colindixon,
17:46:52)
- Lithium-SR2 (colindixon, 17:47:05)
- we are still waiting on the controller team to
sign off that the test failures are non-blocking (colindixon,
17:47:22)
- https://docs.google.com/spreadsheets/d/1ktL11ElNdf4D3RUeRNUd8SPnYO0to0DxzSZGst0KdMQ/edit#gid=599953319
(anipbu,
17:48:03)
- https://docs.google.com/spreadsheets/d/1ktL11ElNdf4D3RUeRNUd8SPnYO0to0DxzSZGst0KdMQ/edit#gid=599953319
(jamoluhrsen,
17:48:05)
- tom pantelis is looking at the clustering ones,
and ttkacik is looking at teh netconf one (colindixon,
17:49:32)
- LuisGomez says the clustering ones aren't
regressions (colindixon,
17:50:08)
- LuisGomez beileves that the netconf one is also
not a regression (colindixon,
17:50:18)
- ttkacik says that it looks like we have
conflicts related to open ports (in this case it looks line oneM2M
was binding to a port in use) in the NETCONF failures (colindixon,
17:53:14)
- ACTION: anipbu to
talk to ttkacik to for help with figuring out which projects are
conflicting with prots and try to resolve (or at least
document) (colindixon,
17:54:17)
- VOTE: Voted on "shall
the TSC approve the Lithium-SR2 release using the artifacts tested
as described in anipbu's spreadsheet linked above?" Results are, +1:
6 (colindixon,
17:57:32)
- AGREED: we will ship
the LIthium-SR2 artifacts (colindixon,
17:57:46)
- ACTION: anipbu to get
tykeal_away the staging repo number, and talk with zxiiro to get the
versions bumped (colindixon,
17:58:19)
- Beryllium branch cutting (colindixon, 17:58:29)
- https://lists.opendaylight.org/pipermail/tsc/2015-September/003879.html
the discussion (colindixon,
17:58:46)
- this needs to be decided by next week
(colindixon,
17:58:58)
- colindixon says that he'd like to see us cut
all at once at offset 2 M5, which would be 12/17/2015, he knows it
causes some people pain, but that it tends to cause pain for those
who can bear it and will risk less breakage in offset 1 and offset 2
projects (colindixon,
18:01:21)
- rovarga notes that will effectively steal 5
weeks of development time from the offset 0 projects (colindixon,
18:03:36)
- cookies (colindixon, 18:04:56)
Meeting ended at 18:05:28 UTC
(full logs).
Action items
- colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160
- colindixon to reach out to the advisory gorup for input on Boron
- anipbu to work with others (stephen kitt?) to see if we can get this done, move odlparent dependency managment to an artifacts pom, move away from odlparent properties, and make third party bundles features in odlparent
- anipbu to talk to ttkacik to for help with figuring out which projects are conflicting with prots and try to resolve (or at least document)
- anipbu to get tykeal_away the staging repo number, and talk with zxiiro to get the versions bumped
Action items, by person
- anipbu
- anipbu to work with others (stephen kitt?) to see if we can get this done, move odlparent dependency managment to an artifacts pom, move away from odlparent properties, and make third party bundles features in odlparent
- anipbu to talk to ttkacik to for help with figuring out which projects are conflicting with prots and try to resolve (or at least document)
- anipbu to get tykeal_away the staging repo number, and talk with zxiiro to get the versions bumped
- colindixon
- colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160
- colindixon to reach out to the advisory gorup for input on Boron
People present (lines said)
- colindixon (86)
- odl_meetbot (22)
- ChrisPriceAB (13)
- dfarrell07 (12)
- edwarnicke (8)
- phrobb (7)
- anipbu (4)
- LuisGomez (3)
- KLuehrs (3)
- jmedved (2)
- mohnish_ (2)
- regXboi (1)
- abhijitkumbhare (1)
- jamoluhrsen (1)
Generated by MeetBot 0.1.4.