Re: Call for participation: Issue triaging and PR review/testing

2017-12-20 Thread Ron Wheeler
help with testing and reporting of bugs! - Rohit From: Ivan Kudryavtsev Sent: Wednesday, December 13, 2017 9:34:43 AM To: dev@cloudstack.apache.org Cc: Rohit Yadav; us...@cloudstack.apache.org Subject: Re: Call for participation: Issue triaging and PR review/te

Re: Call for participation: Issue triaging and PR review/testing

2017-12-20 Thread Rohit Yadav
loudstack.apache.org Cc: Rohit Yadav; us...@cloudstack.apache.org Subject: Re: Call for participation: Issue triaging and PR review/testing 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

RE: Call for participation: Issue triaging and PR review/testing

2017-12-14 Thread Paul Angus
...@cloudstack.apache.org; Ivan Kudryavtsev Cc: dev Subject: RE: Call for participation: Issue triaging and PR review/testing Manual testing, not sure if automated test could do an entire test Sent from Yahoo Mail on Android<https://overview.mail.yahoo.com/mobile/?.src=Android> On Thu,

RE: Call for participation: Issue triaging and PR review/testing

2017-12-14 Thread Paul Angus
Message- From: Luis [mailto:lmartinez...@yahoo.com.INVALID] Sent: 14 December 2017 02:04 To: us...@cloudstack.apache.org; Ivan Kudryavtsev ; us...@cloudstack.apache.org Cc: dev Subject: Re: Call for participation: Issue triaging and PR review/testing Hi What about creating a team for testing and

Re: Call for participation: Issue triaging and PR review/testing

2017-12-13 Thread Ron Wheeler
Is there a document (wiki page?) that captures the discussion about what was missed in the release of 4.10? Ron On 13/12/2017 9:53 AM, Ivan Kudryavtsev wrote: Hi, Rene. That sounds great, chaos engineering and controlled experiments are great tools, smoke tests improvements are also subject o

Re: Call for participation: Issue triaging and PR review/testing

2017-12-13 Thread Ivan Kudryavtsev
Angus > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Rene Moser [mailto:m...@renemoser.net] > Sent: 13 December 2017 12:56 > To: dev ; us...@cloudstack.a

Re: Call for participation: Issue triaging and PR review/testing

2017-12-13 Thread Ivan Kudryavtsev
Hi, Rene. That sounds great, chaos engineering and controlled experiments are great tools, smoke tests improvements are also subject of discussion and I think that UAT (user acceptance tests) suite should be designed finally. It's important to a business to have one. It's important to the communit

RE: Call for participation: Issue triaging and PR review/testing

2017-12-13 Thread Paul Angus
.net] Sent: 13 December 2017 12:56 To: dev ; us...@cloudstack.apache.org Subject: Re: Call for participation: Issue triaging and PR review/testing Hi all On 12/13/2017 05:04 AM, Ivan Kudryavtsev wrote: > Hello, devs, users, Rohit. Have a good day. > > Rohit, you intend to freeze 4.11 o

Re: Call for participation: Issue triaging and PR review/testing

2017-12-13 Thread Rene Moser
Hi all On 12/13/2017 05:04 AM, Ivan Kudryavtsev wrote: > 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 b

Re: Call for participation: Issue triaging and PR review/testing

2017-12-12 Thread Ivan Kudryavtsev
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

Re: Call for participation: Issue triaging and PR review/testing

2017-12-08 Thread Wido den Hollander
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