Team, As you know, I'm on a mission to cleanup our JIRA projects. A large part of this effort involves making sure that the "Fix Version" field for most issues is filled in with a *valid current or future release name*.
In talking to the community about this, several people have asked me what to do with issues that have been identified, but are not of high enough priority to be resolved in the current release. The solution is to assign the issue to a future release. In order to better support this tactic, I have pushed out the release strings for the Guilin, Honolulu, and Istanbul releases to all ONAP projects. That's about 2 years worth of releases into the future. If you can't assign an issue to Frankfurt, or one of these future releases, then you might as well close it. As a side note, I would like to take over creation of ONAP major release names for all JIRA projects (e.g., Guilin, Honolulu, etc.). Please refrain from creating your own major ONAP release names. Note, however, that you may create your own *internal* release names, as necessary for use within the scope of your project. If you seem to be missing a major ONAP release name (through Istanbul), please let me know. Let me know if you have any questions. David -- *David McBride* Release Manager Linux Foundation Networking (LFN) Mobile: +1.805.276.8018 Email/Google Talk: [email protected] IRC: dmcbride -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19620): https://lists.onap.org/g/onap-discuss/message/19620 Mute This Topic: https://lists.onap.org/mt/67407399/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
