The origin of this conversation is a bit of a hall-way discussion with Shyam. The actual matter should be familiar to maintainers. For what it is worth, it was also mentioned at the recent Community meeting.
As the current workflows go, once a release is made generally available, a large swathe of bugs against an EOLd release are automatically closed citing that "the release is EOLd and if the bug is still reproducible on later releases, please reopen against those". However, there is perhaps a better way to handle this: [0] clone the bug into master so that it continues to be part of a valid bug backlog [1] validate per release that the circumstances described by the bug are actually resolved and hence CLOSED CURRENTRELEASE them I am posting here for discussion around this as well as being able to identify whether tooling/automation can be used to handle some of this. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> _______________________________________________ maintainers mailing list [email protected] https://lists.gluster.org/mailman/listinfo/maintainers
