Community
Participate
Working Groups
Given the patches produced for bug 445122, I wanted to note a few "reminders", especially relevant if we would need yet even more patches! 1. The "feature patch" itself should have a qualifier too. The ones for bug 445122 had simply "1.0.0". That's fine as long as there is only one ... but, better if future ones had a qualifier that "mimicked" the original feature ... but but with "current date". 2. The "license" (EUA) distributed with feature patch should be identical to the "current" one (dated 2014). I would mark these as "minor", but if there are "future" patches, then the severity would rise anyway, so will leave as normal bug.
For these kinds of patches we typically have been versioning them as 1.0.x where x is how many fixes have been made so far (zero based). The important version qualifier is on the bundles inside of the patch that it will apply, but I understand your point and have no objection to having the feature patch itself carry a qualifier also. Our patches are always cumulative (so 1.0.3 would contain all previous patches in 1.0.0, 1.0.1 and 1.0.2 of that feature patch). I also agree with updating the license.
Good point about the "service field" increment. I guess the qualifiers are most important if we produce one set for early testing, and then decide a day or two later to "redo" it, before it's released. [I should add, I'd like to get to the point where we could "build" these with our usual framework, since then it would include "source bundles" and we could "unit test" everything, run through comparator, and other "enterprise-quality" aspects. This is mostly to say "you are not alone" in producing these ... but will depend on other work items, etc. to get to the point of improving our framework a little to handle these easily].
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.
