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 > >
