============================= #opendaylight-meeting Meeting ============================= Meeting started by colindixon at 17:46:40 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2014/opendaylight-meeting.2014-01-13-17.46.log.html . Meeting summary --------------- * the google doc of release tasks can be found here: https://docs.google.com/spreadsheet/ccc?key=0AoSzir1BfjyWdDQyVElWNG9mcWxhblREckZjbjFxUVE#gid=1 (colindixon, 17:47:23) * ACTION: Madhu will push a patch to integration which generates a new target to build the list of version skew so that we can track daily skew in the release (colindixon, 17:55:44) * in order to build per project version out-of-sync messages we will need to great jenkins jobs per project (colindixon, 17:57:55) * ACTION: Madhu will work with cdub and tykeal to migrate the *purely information* versions job to all projects participating with in the simultaneous release (colindixon, 17:58:47) * great phrobb, that means we can get started with the actual insertion on it's 1/15 start date (colindixon, 18:01:42) * suggested copyright headers can be found here https://wiki.opendaylight.org/view/Project_Proposals:Code_Prep_Suggestions#Copyright_and_license_headers_in_source_code_files (colindixon, 18:02:17) * ovsdb project uses author tag as well (Madhu, 18:09:13) * ACTION: phrobb to consult legal counsel to make sure that we can adopt https://wiki.opendaylight.org/view/Project_Proposals:Code_Prep_Suggestions#Copyright_and_license_headers_in_source_code_files as formal practice for copyright notices (colindixon, 18:12:29) * AGREED: to use the template for copyright headers at https://wiki.opendaylight.org/view/Project_Proposals:Code_Prep_Suggestions#Copyright_and_license_headers_in_source_code_files pending phrobb checking with legal counsel (colindixon, 18:14:18) * bundle versions for release (colindixon, 18:14:50) * we're talking about line 39 for now, we'll go back to the top of the spreadsheet later (colindixon, 18:16:55) * HELP: anyone wanting to help with the user manual template and/or developers' guide template should e-mail RobDolin at RobDolin@microsoft.com (colindixon, 18:24:30) * tabling the discussion of synchronized versions for a later date (colindixon, 18:25:42) * ACTION: Madhu will send out a sequence in which projects can fix their hydrogen release version numbers and will coordinate with team leads to do that starting on 1/15, moving from SNAPSHOT -> RELEASE will happen later and artifacts won't be cut until 1/27 (colindixon, 18:28:22) * release notes (colindixon, 18:29:11) * I have written up sample release notes, put them here: https://wiki.opendaylight.org/view/Sample_Release_Notes#Known_Issues_and_Limitations and asked for feedback on the mailing list. (colindixon, 18:29:48) * I have made some effort to root out scala (edwarnicke, 18:35:05) * ACTION: colindixon will look into creating a section for project and edition release notes for hydrogen (colindixon, 18:35:36) * ACTION: edwarnicke will help colindixon to produce a list of required tools for running based on the used languages in the release for the release notes (colindixon, 18:36:11) * HELP: anyone who wants to shape the release notes should provide feedback to my e-mail to discuss or reach out to me, or maybe even just edit the wiki page (colindixon, 18:36:52) * testing for JVM and OS platforms (line 36) (colindixon, 18:38:58) * ACTION: anees and/or shague_ to add fedora to the list of OSes, also to add JVM columns and decide which JVMs we're testing (colindixon, 18:45:00) * on the mailing list, somebody was saying that they had out of memory errors with the Oracle JVM on Ubuntu (colindixon, 18:45:32) * I have used openjdk successfully on ubuntu, and Oracle JDK successfully on MacOS X Maverick (and Mountain Lion before that... but its been a while) (edwarnicke, 18:46:24) * I'm going to try to focus the topics on things due tomorrow for a while (colindixon, 18:46:53) * documenting how to cut release artifacts (colindixon, 18:49:34) * HELP: we need somebody to volunteer to write up documentation about how to do this (colindixon, 18:49:46) * investigate signing of release docs (colindixon, 18:50:31) * ACTION: tykeal to talk to kernel.org about their code signing process to see if we could use it, sounds not totally promising (colindixon, 18:53:05) * download page (colindixon, 18:55:09) * phrobb and others are meeting today about the download page (colindixon, 18:57:25) * switching meeting to 9a PST for india (colindixon, 18:59:42) * AGREED: on moving the morning meeting to 9a for india since there were no objections (colindixon, 19:00:00) Meeting ended at 19:00:04 UTC. Action Items ------------ * Madhu will push a patch to integration which generates a new target to build the list of version skew so that we can track daily skew in the release * Madhu will work with cdub and tykeal to migrate the *purely information* versions job to all projects participating with in the simultaneous release * phrobb to consult legal counsel to make sure that we can adopt https://wiki.opendaylight.org/view/Project_Proposals:Code_Prep_Suggestions#Copyright_and_license_headers_in_source_code_files as formal practice for copyright notices * Madhu will send out a sequence in which projects can fix their hydrogen release version numbers and will coordinate with team leads to do that starting on 1/15, moving from SNAPSHOT -> RELEASE will happen later and artifacts won't be cut until 1/27 * colindixon will look into creating a section for project and edition release notes for hydrogen * edwarnicke will help colindixon to produce a list of required tools for running based on the used languages in the release for the release notes * anees and/or shague_ to add fedora to the list of OSes, also to add JVM columns and decide which JVMs we're testing * tykeal to talk to kernel.org about their code signing process to see if we could use it, sounds not totally promising Action Items, by person ----------------------- * colindixon * colindixon will look into creating a section for project and edition release notes for hydrogen * edwarnicke will help colindixon to produce a list of required tools for running based on the used languages in the release for the release notes * edwarnicke * edwarnicke will help colindixon to produce a list of required tools for running based on the used languages in the release for the release notes * Madhu * Madhu will push a patch to integration which generates a new target to build the list of version skew so that we can track daily skew in the release * Madhu will work with cdub and tykeal to migrate the *purely information* versions job to all projects participating with in the simultaneous release * Madhu will send out a sequence in which projects can fix their hydrogen release version numbers and will coordinate with team leads to do that starting on 1/15, moving from SNAPSHOT -> RELEASE will happen later and artifacts won't be cut until 1/27 * phrobb * phrobb to consult legal counsel to make sure that we can adopt https://wiki.opendaylight.org/view/Project_Proposals:Code_Prep_Suggestions#Copyright_and_license_headers_in_source_code_files as formal practice for copyright notices * shague_ * anees and/or shague_ to add fedora to the list of OSes, also to add JVM columns and decide which JVMs we're testing * tykeal * Madhu will work with cdub and tykeal to migrate the *purely information* versions job to all projects participating with in the simultaneous release * tykeal to talk to kernel.org about their code signing process to see if we could use it, sounds not totally promising * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * colindixon (139) * Madhu (94) * edwarnicke (72) * tykeal (24) * ashaikh (19) * phrobb (13) * GiovanniMeo (8) * abhijitkumbhare (6) * dmm (4) * RobDolin (3) * goldavberg (3) * shague_ (3) * odl_meetbot (2) * michal_rehak (1) * LuisGomez (1) * Konstantin (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot