I have not thought through it all, but some quick comments for now, I will come back and refine tomorrow or later tonight
> -----Original Message----- > From: Musayev, Ilya [mailto:imusa...@webmd.net] > Sent: Thursday, September 26, 2013 4:06 PM > To: dev@cloudstack.apache.org > Subject: RE: [DISCUSS] Release Managers for future ACS releases - > enhacement > > I can feel your pain, as well as Chip's, Dave's, Joe's and whoever was > involved in past. > > Here is a bit of uncharted territory we need to address about bug > assignment. > > In past I've seen folks ask - we have X number of bugs that need to be > triaged, who can take what? Are we still keeping this framework and do > we default to whoever wrote the code/patch initially - if no one > volunteers? [Animesh>] We have list of maintainers by component that may be something to start with. This does not mean they have to do it, but they can call back and say I do not have time right now can someone else look into it. Or if an assigned issue is not worked on for a week it automatically gets unassigned, would need to check on JIRA support for the workflow, having played with JIRA at least such reports are easy to generate. > > While Citrix is one of the main supporters of CloudStack project and has > people employed to do development, how does one - who has no insight > into Citrix - assign bugs to people who are employed by Citrix (and can > we even do that without their full consent)? > [Animesh>] We can look up the maintainers list by component and I can facilitate within Citrix. Even for the prior release I have received emails from nonCitrix community members to follow through with Citrix folks. > One other part, since Citrix and other companies have QA teams, perhaps > we can have a closer collaboration as to what testing was done on Citrix > side when it comes to major releases? (i.e. ACS 4.2 release) > [Animesh>] Yes, QA contributors have published test plans and Sudha has called out help with QA tasks in community. Alex, Amogh, Frank and Prasanna are working on a test infrastructure design that can be replicated across sites to make testing simpler for anyone who wants or can contribute. You should see a proposal on that soon. > I know in past Citrix would branch of from ACS or even have a separate > codebase, but with future releases, its all going to be one ACS code > base. So future actual release testing/qa (not automated as part of > built process) should get easier since we have folks dedicated to work > on ACS project to do QA or is this an incorrect assumption? > [Animesh>] We are aligned already from code perspective and you would have seen huge QA engagement in 4.2 . I wanted to call out like every place there is no Elastic human capital available so as a community we have to reduce the reliance on just Citrix QA. Citrix QA is a good community citizen but will naturally focus on Citrix priorities first. If you contribute a code to CloudStack ideally you should be prepared to maintain and test as well. Community testing is indeed needed for this project. > I am also under impression it would help to have at least one person > from Citrix on RM team, helps with communication, as they can tap people > by other means other than mailing lists. [Animesh>] Yes I am always there to facilitate with community. Sudha, Abhi and Ram Ganesh are also available to help out. > > There are a lot of assumptions here, I could be wrong on all or some of > these, please clarify or voice your opinion. [Animesh>] Thanks for bringing up these issues they are all valid and its best to clear out any expectations. > > Thanks > ilya > > > > > > > -----Original Message----- > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > > Sent: Thursday, September 26, 2013 5:25 PM > > To: dev@cloudstack.apache.org > > Subject: RE: [DISCUSS] Release Managers for future ACS releases - > > enhacement > > > > +1 > > > > Ilya I am glad that you brought it up and recognize the challenge. I > > survived on 3 cups of JetFuel[1] every day for last 3 months. It's > > like doing two $dayjob$ shifts > > > > http://www.keurig.com/coffee/jet-fuel-extra-bold-coffee-k-cup-coffee- > > people > > > > > > > > > -----Original Message----- > > > From: Musayev, Ilya [mailto:imusa...@webmd.net] > > > Sent: Thursday, September 26, 2013 9:02 AM > > > To: dev@cloudstack.apache.org > > > Subject: [DISCUSS] Release Managers for future ACS releases - > > > enhacement > > > > > > I apologize in advance if this is a repeat of something that was > > > previously stated. > > > > > > As Animesh learned recently with ACS 4.2, RM work for major versions > > > takes a lot of effort, to lesser extent the 4.2.x minor release may > > > not be as involved, but still decent amount of work. > > > > > > What complicates the matter further, is many of us have $dayjobs$ > > > that don't emphasize heavy involvement on ACS. > > > > > > Perhaps we can revisit the strategy and have 2 -3 release managers > > > for major version and 1-2 for minor. > > > > > > Obviously, one is going the be a Lead RM, and others will be > > > secondary but also involved. > > > > > > Any thoughts on this approach? > > > > > > Thanks > > > ilya > > >
