Hi all, Thank you for your participation. I think this retrospective went really well and people are getting the hang of it. If you haven't read it since it was started take a quick look when you have a chance. In addition to what participants added I also commented on #9098 and #9036, but didn't have anything actionable for them.
I reviewed al the fixed bugs in 2.1.5 like I did for 2.1.3 and people are doing a good job adding unit and dtests to cover what they worked on. This isn't really a change in behavior, people were doing a good job before there were just some hard/larger testing elements that went unrepresented but are now in JIRA. I created far fewer issues hanging off of CASSANDRA-9012 <https://issues.apache.org/jira/browse/CASSANDRA-9012> as part of this retrospective. I think this points to there being a bounded scope of things that are missing and that we are starting to get a picture of what is painful and what isn't. I regret not linking the issues that trigger the creation of a test task to the task so we can get visibility into severity and frequency associated with a test task. I did some of that this time, but that is missing from the 2.1.3 review I did. This is something anyone can do so if you are working on a bug that we shipped and you can find a test task that would have helped you should link them. This informs prioritization as well as test design. Reviewing the tickets in a release is turning out to be really informative for me. Already some thing stand out as repeated pain points across the two releases. I plan on continuing to do that so with a focus on linking bugs to test tasks that would address them. What is hanging off of CASSANDRA-9012 is not small. Many of those tickets are just stories and will probably transform into several tasks spread out over longer periods of time. But it is bounded and if we start working through them we should be able to catch a good chunk of bugs before they ship. You can look at the linked issues and see that some would not have been hard to catch. Philip Thompson has started work on the kitchen sink harness. I put some of my notes on implementation details from our discussion into the kitchen sink doc <https://docs.google.com/document/d/1kccPqxEAoYQpT0gXnp20MYQUDmjOrakAeQhf6vkqjGo/edit?usp=sharing>. Nothing is set in stone so feel to comment. Previously the doc just had a links to bugs we feel should be tested for by the kitchen sink harness. Regards, Ariel On Mon, May 4, 2015 at 11:50 AM, Ariel Weisberg <ariel.weisb...@datastax.com > wrote: > Hi, > > Someone asked if they can add their own to went well/poorly/changes and > the answer is yes. We'll iterate on what goes up, but anyone can bring > something up for discussion. I don't think you should post a personal > well/poorly section, but you can post about things that went poorly for > just you. When something doesn't work for you it's not working for any of > us. > > Ariel > > On Mon, May 4, 2015 at 11:40 AM, Ariel Weisberg < > ariel.weisb...@datastax.com> wrote: > >> Hi, >> >> It's time. This month were are going to try and do the retrospective in a >> Google >> doc >> <https://docs.google.com/document/d/159yJY2YS5hLTqlU7J2lOYJr5cfhECRGe7k-QwavuiBw/edit?usp=sharing>. >> Inside the docs I am guessing we will do a threaded conversation and sign >> off contributions in the discussion section. >> >> Last month things didn't thread well and it was hard to track what was >> going on. >> >> We released 2.1.5 in April so now is a good time to review anything you >> fixed in 2.1.5 with an eye towards things that we would like to have done >> better. You don't have to have an answer for how we could do things better. >> We don't want to be limited to discussing things we already have answers >> for. >> >> If something is already being addressed (or is queued to be addressed by >> a JIRA) there is no need to mention it unless you want +1 the issue for >> some reason such as it not being prioritized sufficiently. >> >> I am going to look at 2.1.5 the same way I didn't with 2.1.3, but I am >> going to hold off on volunteering stuff until I see what people come with. >> >> Regards, >> Ariel >> >> >
