Nice videos.... I guess I'm missing a lot of great shows by living in the US.
Yes, interest in Quantum is at an all-time high, which is a mixed blessing. I strongly suspect that there is already more code proposed for G-3 than we have time to do a good job reviewing. Plus there are additional patches that have not even been proposed yet. To me, the important thing, like we discussed in the meeting, is for each core dev to focus on being a reviewer for at least one 'high' priority patch, and then to identify an additional set of patches that you think are both valuable and feasible for reviewing in the short-time left. I have left all possible items targeted at G-3, because my approach has been to let core reviewers make decisions about what will make it based on feature importance, review responsiveness, code quality, code complexity, etc. If we think we should handle this flood of blueprints differently, I'm always open to ideas. It can be easy to get frustrated + burned out by a feeling that we need to review every patch, simply because its proposed. But since reviewing everything in time for G-3 is impossible, here are a couple things you can think about to make you feel a bit better about not doing a "rush job" for last minute reviews: - Generally, code proposed at the last minute and rushed through review contains more bugs than normal code. Thus, not only does reviewing this code take away time that could be used for testing + fixing bugs in the existing code base, its actually introducing more bugs, causing a vicious cycle. The same is true for docs: not only are you not spending time writing docs for existing stuff, you are adding code that requires even more documentation. - In many cases, people proposing patches at the very end of G-3 often could have proposed those patches earlier, but they (or their employers) made prioritization decisions that delayed them until the last minute. Don't let their decisions cause you undue heartburn + burnout. The code will all get merged into OpenStack eventually. Of course, we want to do our best to make sure people can get changes into Quantum as quickly as feasible, we should just never let this undermine our most important goals: a happily contributing core team and a high quality + well documented piece of software. Dan On Wed, Feb 6, 2013 at 10:00 AM, Gary Kotton <[email protected]> wrote: > Hi, > Over the last two weeks there has been a ton of new patches. I think that > we have hit a record for the amount of open patches. To be honest I feel > like I am drowning with them a bit. In addition to doing the easy ones here > and there I will focus on the following: > 1. Brocade plugin > 2. Yongs patches for the agents > 3. Service insertions > Oh well. > Initially I felt like Tommy: > http://www.youtube.com/watch?**v=919IA_Lj0Ko<http://www.youtube.com/watch?v=919IA_Lj0Ko> > Any idea when I can get an assistant: http://www.youtube.com/watch?** > v=sVe9zjO6-O8 <http://www.youtube.com/watch?v=sVe9zjO6-O8> > Thanks > Gary > > > -- > Mailing list: > https://launchpad.net/~**quantum-core<https://launchpad.net/~quantum-core> > Post to : > [email protected].**net<[email protected]> > Unsubscribe : > https://launchpad.net/~**quantum-core<https://launchpad.net/~quantum-core> > More help : > https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp> > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
