For sure. I will be doing a status report every Monday till the RC is accepted to help keep everyone on the same page. I think this will help us organize ourselves to best utilize our limited resources and keep us focused on getting PRs ready to merge.
This will all be easier to manage when we move the repo to the 'apache-cloudstack' github org. I need to follow up with the ASF on that, I have just been too busy recently. With the new org we will be able to track the status of each PR and the blockers to getting it merged via Labels, which will make things easier and more transparent to everyone. Right now I just have a bunch of todo lists that I am trying to keep up to date. Tt is not a perfect system by any stretch. If I can get more people participating in code review, I think things will start to move a bit faster. I will be getting more people setup with CI environments so we can start to distribute the CI load a little more, that should start to really get things moving. Gotta start somewhere. :) *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Mon, Apr 18, 2016 at 10:10 PM, ilya <ilya.mailing.li...@gmail.com> wrote: > Hi Will > > Thanks for the detailed update and effort. > > Please keep us posted. > > Regards > ilya > > On 4/18/16 1:48 PM, Will Stevens wrote: > > ACS PRs > > > > - 1452 - master (ready, pending LGTM) > > - 1475 - 4.7 (pending clarification) > > - 1420 - master + svm (CI running) > > - 1365 - 4.7 (pending ALL) > > - 1402 - 4.7 (needs work) > > - 1454 - master (ready, pending LGTM) > > - 1459 - master (rerun CI) NOTE: This closes #561 > > - 1409 - master (pending CI) > > - 1433 - master (pending CI) > > - 1230 - master (pending CI) > > - 1326 - master (*pending CI) > > - 1436 - master (*pending CI) > > - 1455 - master (*pending CI) > > - 1423 - master + svm (*pending CI) > > - 1428 - master (pending ALL) > > - 1450 - 4.7 (pending ALL) > > - 1453 - master (pending ALL) > > - 1403 - master (pending ALL) > > - 1331 - 4.7 (pending ALL) > > - 1475 - 4.7 (pending ALL) > > - 1458 - master (pending ALL) > > - 1297 - master (pending CI) > > - 1410 - 4.7 (pending ALL) > > - 1483 - 4.7 (pending ALL) > > - 1470 - 4.7 (pending ALL) > > - 1471 - 4.7 (pending ALL) > > - 1472 - 4.7 (pending ALL) > > - 1473 - 4.7 (pending LGTM) > > - 1474 - 4.7 (pending ALL) > > - 1486 - 4.7 (pending ALL) > > - 1483 - 4.7 (pending ALL) > > - 1488 - master (pending ALL) > > - 872 - master + svm (pending CI) > > - 1489 - master (pending CI) > > - 1456 - 4.7 (pending ALL) > > - 1412 - 4.6 (pending ALL) > > - 1406 - 4.6 (pending LGTM) > > - 1378 - 4.6 (pending LGTM) > > - 1491 - 4.7 (pending ALL) > > - 1360 - master (pending LGTM) > > - 1490 - 4.7 (pending ALL) > > - 1493 - master (pending ALL) > > - 1397 - master (pending CI) > > - 1499 - master (pending ALL) > > - 1371 - master + svm (pending ALL) > > - 1500 - master (pending ALL) > > > > * Denotes special requirements for CI testing > > svm = specifies that the PR will require an updated systemvm template > > > > --- > > > > Here is this Monday's status report. It is looking like we will need a > new > > systemvm template with the 4.9 release, so I would like to try to get on > > top of the PRs that will require systemvm template changes so we can make > > sure to get them tested and in earlier in this release window. This will > > give us more time to work out any kinks prior to the RC. > > > > Sorry for the slow down on the CI. I have been having some hardware > > issues, but I think I have resolved my issues (fingers crossed). We now > > have Daan up and running with a CI environment as well, so that will help > > as well. I owe a couple people instructions for getting a CI environment > > setup so they can start testing. I will hopefully be able to get to that > > tomorrow. > > > > If you can review the list above and try to give me code reviews on > > anything that has a status of 'pending LGTM' since I am only missing code > > review for those PRs (assuming my status is up to date). Also, I need to > > start getting code reviews on the PRs that have a status of 'pending > ALL'. > > > > There are a few PRs that have come up that are targeting 4.6. I would > like > > some guidance for how I should be handling them. My understanding is > that > > the 4.7 release is the oldest supported release, so should I be asking > the > > author to close the PR and open a PR against the 4.7 code? > > > > Hope you all had a great weekend. Looking forward to a productive week > > this week. :) > > > > Cheers, > > > > Will > > >
