Felix Meschberger wrote: > > I think, issues resolved/closed and included in a release must not be > opened anymore. Otherwise we come into states where issues spawn more > than one release and it is not clear anymore, what part of the issue > work is in which release. > > Rather I think for such situations we should: > > * create a new issue > * link the two issues > * optionally change the resolution of the closed fix to > something "not completely fixed, see linked issue) Yes, I'm just thinking of users looking into an issue which shows "fixed in version x.y" and they think it's fixed in version x.y - usually you don't look immediately at linked bugs. So a new resolution would make sense - especially as this bug is not fixed :)
>> I personally don't think that we need new states for documentation or >> testing. Usually people are either doing this anyway, or are never doing >> it - so a new state doesn't help. > > It does not force us to do tests or documentation, but it may remind us > to not forget about it (as was the case here). Yes, but we should be carefull as this should not block a release :) > It may not completely help, but I suppose it won't harm either. On the > other hand it may help with documentation, in that we can consider > documentation state issues specially. Yes, it doesn't harm - the only problem I see (and it might be minor) is that other projects at Apache don't have these states. Carsten -- Carsten Ziegeler [email protected]
