Historically we would transition issues in Pulp's issue tracker from MODIFIED to CLOSED - CURRENTRELEASE when a GA build went out the door. The same approach is working against us for the duration of the Pulp 3.0 beta. We have a large number of issues in MODIFIED state, but are considered released.
I propose that we transition issues to CLOSED - CURRENTRELEASE when they have been shipped with a 3.0 beta. Could we add automation to do this at release time? What do you all think? Thanks, Dennis
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
