Thanks for the suggestions Benjamin! I've re-purposed one of the dashboard queries to track "Issues affecting 0.28.x that are resolved in versions later than 0.28". https://issues.apache.org/jira/issues/?filter=12338701 ^ That will show up on the dashboard too.
There are 26 issues in that list, which we'll triage. I suspect most of these will not be backported if they aren't already. On Mon, Nov 7, 2016 at 5:31 AM, Benjamin Bannier < [email protected]> wrote: > Hi Joseph and Anand, > > > We are planning to cut this patch release within three workdays - that > would be around Monday next week. So, if you have any patches that need to > get into 0.28.3 make sure that either it is already in the 0.28.x branch or > the corresponding ticket has a target version set to 0.28.3. > > There are still a number of rather unpleasant issues filed against 0.28 > which are only fixed in versions > 0.28.3. > > https://issues.apache.org/jira/browse/MESOS-5224 > https://issues.apache.org/jira/browse/MESOS-5685 > https://issues.apache.org/jira/browse/MESOS-5727 > https://issues.apache.org/jira/browse/MESOS-5763 > https://issues.apache.org/jira/browse/MESOS-6391 > > Maybe it would be worthwhile to backport some of these. > > FYI, I used the following query which still required some manual filtering: > > project = Mesos AND \ > affectedVersion in (0.28, 0.28.0, 0.28.1, 0.28.2, 0.28.3) AND \ > (fixVersion not in (0.28.3) OR fixVersion < 0.28.3) AND \ > status = Resolved and type = Bug > > This might to be like a worthwhile addition to patch release dashboards > (if somebody with more JIRA foo could come up with an actually working > query). > > > Cheers, > > Benjamin
