V30 - Sprint #6 » History » Revision 6
Revision 5 (Johannes Bornhold, 05.02.2015 14:28) → Revision 6/9 (Johannes Bornhold, 05.02.2015 14:30)
h1. Release v3.1.0 Main objectives are aligned to the "Roadmap":https://code.rhodecode.com/marcink/docs/files/default/roadmap-momentum.rst * Bugfixing of high priority issues Expected sources are our regression tests and feedback from the first Customers trying out our new release. Please see below regarding the handling of high priority issues. * Stable system even if the vcsserver is not installed * Next steps in the redesign pipeline: compare view, file view, summary view, error pages * Pull Request improvements - First steps * Per Repository settings * (?) Smart commits h2. Issue handling We classify new issues according to the question of how much it would prevent our users from using our product. Everything which would be a serious impediment from that perspective will be in priority "High" and will be sneaked in into our running Sprint. This is an attempt to find a good trade off between staying focused and keeping productivity high and on the other side reacting to severe issues in a timely manner. Please notify Johannes (Lisa) in case you think that you found an issue which would qualify as priority "High". h2. Links Review changes "Issues overview":https://bugs.rhodecode.com/projects/rhodecode-3-0/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=32&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&group_by=priority h2. Contacts * Lisa We are involving Martina and Greg more into our workflow, starting with our daily standup meeting and planning. This way they know what we are up to and have a chance to prepare their own schedule better. * We (mainly Johannes) is making the main contact around the issue tracker and the details of the planning for check_screens script available so that this Sprint can be used by every team member to quickly verify if frontend changes have unintended collateral damage in other places. This is expected to pay off within a few days already, since it avoids extra loops when checking PRs. * Paris We (mainly Greg) kick off test automation. This is the main contact around Merging Pull Requests a prevention of letting Greg become more and more a bottleneck. h2. Links "Issues overview":https://bugs.rhodecode.com/projects/rhodecode-3-0/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=32&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&group_by=priority