cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan Kudryavtsev <kudryavtsev...@bw-sw.com>
Subject Re: Call for participation: Issue triaging and PR review/testing
Date Wed, 13 Dec 2017 04:04:43 GMT
Hello, devs, users, Rohit. Have a good day.

Rohit, you intend to freeze 4.11 on 8 january and, frankly speaking, I see
risks here. A major risk is that 4.10 is too buggy and it seems nobody uses
it actually right now in production because it's unusable, unfortunately,
so we are planning to freeze 4.11 which stands on untested 4.10 with a lot
of lacks still undiscovered and not reported. I believe it's a very
dangerous way to release one more release with bad quality. Actually,
marvin and units don't cover regressions I meet in 4.10. Ok, let's take a
look at new one our engineers found today in 4.10:

It happens rarely for Domain Admin, probably other roles are affected. We
meet it once a week. It's for resource accounting. Domain admin resource
quota is 200GB of primary storage. During continouos creation of VMs and
removing them it leads to "Maximum number of resources of type
'primary_storage' for domain id=2 has been exceeded", however only 26 GB is
used actually.

I mean smoke tests run well, unit tests run well, but *nobody reported very
obvious bug* which should be met number of times if community use 4.10. I
suppose, there are a lot of undiscovered and unreported regressions in 4.10
and this is a huge risk to the 4.11 release quality and more we move that
way quality decreases. Unfortunately, I'm not able to propose a silver
bullet, but I suppose feature development speed should be decreased until
master is tested very thoroughly and might be 8 january is too early for
4.11 freeze.



2017-12-09 2:00 GMT+07:00 Wido den Hollander <wido@widodh.nl>:

>
>
> On 12/08/2017 03:24 PM, Rohit Yadav wrote:
>
>> All,
>>
>> Given we've about a month left until 4.11/LTS freeze date of 8th Jan 2018
>> [1], I would like to call our community for active participation.
>>
>> Given a huge pile of open issues, please share on this thread a 'brief'
>> list of top bugs/issues that you would want to see fixed and are
>> applicable
>> to master branch, especially critical/blocker issues and regressions. I
>> would especially like to engage with the users of the community towards
>> this effort. I'll start weekly reporting of open issues by end of next
>> week.
>>
>> Developers - feel free to comment tagging Daan (@DaanHoogland), Paul
>> (@PaulAngus) and me (@rhtyd) in your pull requests if you're seeking
>> review
>> and testing (and merging) of your PR. I hope to work with you all with my
>> committer/contributor hat on.
>>
>> Finally, I look forward to all of your help and support towards the next
>> (LTS) release.
>>
>>
> Let's make it work!
>
> Thoughts, comments?
>>
>>
> With the holiday season coming up we might see things slow down a bit. But
> I think we already have enough PRs open for 4.11
>
> We should be able to get out a proper release again.
>
> Wido
>
>
> [1] http://markmail.org/message/mszlluye35acvn2j
>>
>> Regards,
>> Rohit Yadav
>> http://rohityadav.cloud | @rhtyd
>>
>>    __?.o/   Apache CloudStack
>>   (    )#     The best of CloudStack is yet to come!
>> (___(_)   https://cloudstack.apache.org
>>
>>


-- 
With best regards, Ivan Kudryavtsev
Bitworks Software, Ltd.
Cell: +7-923-414-1515
WWW: http://bitworks.software/ <http://bw-sw.com/>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message