As we are before next milestone, let's get back to this excellent (in my opinion) proposal from Dmitry. Current situation is the following: there are 121 blueprints targeted for 6.0. Most of them miss a header with QA/reviewers/developers information, basically those are incomplete blueprints
Hi, I really like what Mike proposed. It will help us to keep milestone clean and accurate. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Aug 6, 2014 at 11:26 AM, Mike Scherbakov mscherba...@mirantis.com wrote: As we are before next milestone, let's get back to this
On 06 Aug 2014, at 10:41, Sergii Golovatiuk sgolovat...@mirantis.com wrote: Hi, I really like what Mike proposed. It will help us to keep milestone clean and accurate. +1 for Mike’s proposal. New members will also benefit from that move: clean picture will make easier to pick up features
Do not cheat. If we need to add functionality after feature freeze, then let add functionality after feature freeze. No reason for additional obfuscation. It will make our workflow for blueprints harder, but it will help us. We will see what we are really going to do and plan our work better.
I have some objections. We are trying to follow a strict development workflow with feature freeze stage. In this case we will have to miss small enhancements that can emerge after FF date and can bring essential benefits along with small risks of breaking anything (e.g. changing some config
+1 Keeping features separate as blueprints (even tiny ones with no spec) really will let us focus on the volume of real bugs. On Tue, Jun 24, 2014 at 5:14 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote: Guys, We have a beautiful contribution guide: