As a follow-up on this. There is a project [1] that contains the larger part of the PRs, I am 2/3 through classifying them as either "waiting for author or other" or as "can be tested". If you are not a committer to the project you may not be able to change a status, I need a volunteer to test this. The plan is that 1. you pick a PR from the Ready column, mark it as assigned to you (as a non-committer just make a comment to ask that. 2. go ahead test and try to break the feature/fix 3. comment your results and 3a. if good mark as "tested" 3b. add feedback to the author 4 if you are a committer you can move it to 4a. "review" if good 4b. waiting for author if bad/failed We are still looking at making contributing more convenient for everybody, but apache restrictions apply.
[1] https://github.com/orgs/apache/projects/668 On Mon, Aug 24, 2026 at 12:43 PM Daan Hoogland <[email protected]> wrote: > > Hee fellow CloudStackers, > > We have a big number of open PRs and especially PRs waiting for > verification. It is hard to verify everything is a live environment > and to keep up with development. > > Due to the large amount of open PRs, we (some colleagues and I) have > decided to organise a test-week, ... and give it the superhero name > SuperTestWeek ;) We will try to get as many open PRs merged as we can > in that week. > > We cordially invite everybody to join us the week of 6-11 September. > We have a team of 10 people totally dedicated (away from $dayjob) to > the open PRs. But of course the more the merrier.
