Chris,
So, to summarize, you're looking for a status that can be set to you know which of the Patches Pushed need to be applied to the previous release? There is currently no facility for specifying multiple releases that a bug applies to. We'd have to create a custom field. The difficulty would come with making use of it. For my part, I only test bugs on master, because I only work on master. Verifying the bug in previous releases doubles or triples the work (depending on how many previous releases I'm supporting). That makes filing the bug report much less sustainable a practice, from a workflow point of view. I would think that anything that gets applied to master would be a candidate for inclusion in the stable release branch. It would be the job of the RM to determine a) if the bug applies, b) if the patch applies and c) if it's too big a new feature to include in stable. Given the quantity of code produced in a release cycle, I can see this being a massive job. Would it help to have additional Koha officer(s) responsible for verifying each Patch Pushed bug report is applicable to the stable release, and then flag it one way or the other? This would reduce the Release Maintainer's tasks to just c) above: determining if this is something that should be backported because it's a bug fix (not a new feature). Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.wa...@bywatersolutions.com Twitter: @sekjal
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
