Kolla developers and bug triagers, Our Mitaka rc2 is scheduled for April 1st. It would be fantastic if anyone that wants to contribute to Kolla in the next two weeks could do the following:
1. Confirm bugs in the "Triaged" state if not the original reporter - that way a developer can assign themselves to work on the problem. Once confirmed set to the Confirmed state. 2. If a bug is in the Confirmed state, assign yourself to it and fix it in priority order High/Medium/Low/Wishlist. 3. Note some wishlist bugs are actually RFEs which will be -2'ed until Mitaka is branched. But many of these are also easy documentation bug fixes where a DocImpact flag was used but the documentation was never written. 4. Bugs in the triaged state with an owner should either be moved to the confirmed state, or their owner removed - how can a bug be fixed if it has no confirmation? :) We typically have capacity to handle approximately 20 bugs per week, which means rc2 should be in good shape assuming we don't find many more issues. The tracker is here: https://launchpad.net/kolla/+milestone/mitaka-rc2 Your assistance appreciated :) Regards, -steve
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
