Hey folks, There was a discussion around Pulp3.0, deciding how to triage "must be in" vs...otherwise, and dealing with the non-prioritized backlog.
You can find a braindump/minutes here : https://etherpad.net/p/Pulp_3.0%2C_3.1_backlog_meeting The TL;DR that came out of the meeting was: - Having a release-tag implies that an issue/task/story is *promised* for that release. Therefore... - Having the "3.0" tag means "it's a BLOCKER for 3.0 GA", and... - Anything else is NOT currently assigned for the 3.0 release - The 3.1 tag has been DELETED - since we're not promising anything for 3.1, until 3.0GA is put to bed. The action items that came out of the mtg, include - this email (hello!) - bmbouter to work on some visualizations of issue-discovery-rate for various stakeholders/plugins G -- Grant Gainey Principal Software Engineer, Red Hat System Management Engineering
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
