I would better remove the fix version completely. The main difference between oak-segment-tar and the rest of Oak is that there is no final cut for this bundle and a version like 1.6 makes very little sense to oak-segment-tar. If an issue is to be solved at some unspecified point in the future and there is no well defined commitment towards the very next version, I would just leave the fix version empty.
2016-07-27 16:21 GMT+02:00 Marcel Reutegger <[email protected]>: > Hi, > > On 27/07/16 16:13, Michael Dürig wrote: >> >> I'm planning to release oak-segment-tar next Friday [1]. >> >> If there are any objections please let me know. Otherwise I'll proceed >> with the release on Friday and reschedule any open issues targeted at >> 0.0.8. > > > No objections, but one suggestion. > > With every oak-segment-tar release a rather large number of issues are > rescheduled. Would it make sense to adopt a similar process of assigning > fix versions as we do with the other modules? Initially a issue would > have a fix version of 1.0 and once resolved the fix version is set to > the upcoming release version. > > Regards > Marcel
