Hi everyone, I would like to propose that we introduce a “Review documentation” period on the release schedule.
We would formulate it as a deadline, so that it fits in the schedule and making it coincide with the RC1 deadline. For projects that are not following the milestones, we would translate this new inclusion literally, so if you would like your project to be documented at docs.o.o, then doc must be introduced and reviewed one month before the branch is cut. In the last week since we released Ocata, it has become increasingly apparent that the documentation was not updated from the development side. We were not aware of a lot of new enhancements, features, or major bug fixes for certain projects. This means we have released with incorrect/out-of-date documentation. This is not only an unfortunately bad reflection on our team, but on the project teams themselves. The new inclusion to the schedule may seem unnecessary, but a lot of people rely on this and the PTL drives milestones from this schedule. From our side, I endeavor to ensure our release managers are working harder to ping and remind doc liaisons and PTLs to ensure the documentation is appropriately updated and working to ensure this does not happen in the future. Thanks, Alex
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
