Hi Vish, Sounds good, I'm all for trying out new things. I think updates on the main openstack list would help.
On Mon, Oct 17, 2011 at 3:08 PM, Vishvananda Ishaya <vishvana...@gmail.com>wrote: > Hi Nirmal, > > I understand the concern. I really want to keep these sub teams focused on > implementation details as opposed to large theoretical discussions. > Separate mailing lists may not be the best solution, but lets let it go for > a couple of months and re-evaluate. Keep in mind that it is just a few > clicks to sign up for any team/list. I can also get the leads to make > regular updates to the main openstack list so everyone can get a high-level > overview of the planned changes. > > Vish > > On Oct 17, 2011, at 9:05 AM, Nirmal Ranganathan wrote: > > Separating into subteams seems like a good idea and will allow more focus > on certain areas, but having separate mailing lists for each team might be a > little too overkill, could lead to fragmented development discussions. Even > to have a cursory overview of what's happening in the teams will require you > to subscribe to each of the mailing lists, unless the openstack mailing list > is cc'd in all the emails, at which point it becomes pointless to have the > subteam mailing lists. > > > Nirmal > > On Mon, Oct 17, 2011 at 9:35 AM, Jay Pipes <jaypi...@gmail.com> wrote: > >> On Mon, Oct 17, 2011 at 1:56 AM, Vishvananda Ishaya >> <vishvana...@gmail.com> wrote: >> > Nova Testing Cleanup Team >> > https://launchpad.net/~nova-testing >> > We have discussed cleaning up the unit tests and separating out >> integration >> > tests for a while, but this needs a specific team to focus on it. We >> need >> > volunteers and a lead. >> > lead - (no lead yet) >> >> Good stuff, Vish, thanks for sharing! Just an FYI, part of the >> OpenStack QA team (folks from NTT) is focusing on cleaning up and >> improving the unit test coverage and quality of Nova. The OpenStack QA >> team meets regularly (Wednesdays at noon EDT) and you should have >> started seeing a steady stream of incoming bug reports regarding test >> coverage and fixes. >> >> For each component in Nova, the NTT team is writing traceability >> matrices (test analysis documents) and submitting bug reports when a) >> the specification for a component does not match the code behaviour, >> b) when there is no specification for a pieces of code, and c) where >> tests are not actually testing the correct behaviour. You can see >> these bugs and traceability matrices in the bug reports (as Google >> Docs spreadsheets) here: >> >> http://bit.ly/paxoxj >> >> I recognize that branches are linked in Launchpad instead of Gerrit, >> and I'm working with the NTT folks to correct that. >> >> Nati-san from NTT is leading his team and can be a good contact for >> the small/unit testing side for Nova. >> >> Cheers! >> -jay >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> > > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp