Marshall Schor wrote:
+1 to marking things fixed in 2.1 as fixed in 2.1.
+1
Did your comment mean to imply that for things that are not real bug
fixes but rather are just porting, we should mark as "blank"? I don't
think I like that idea.
Here's a couple of thoughts. My (slight, easy to talk me out of it)
preference is to just go ahead and mark everything in Jira that is
included in 2.1, as being included in 2.1. Yes, that will be a big
list. But we can say why it's so big.
Alternatively, we could create another release number - call it
2.1-migration-to-Apache for instance, and mark those things that we
think should not be in the 2.1 "fix" list, as being in this other list.
That way, we're clearly documenting things, making it easier for the
reviewers (and future users) to understand what's going on.
-Marshall
It would be difficult to cleanly distinguish between IBM-to-Apache
migration issues and version 2.1 issues, and I don't think it's really
worth the effort. Let's just mark everything we did for 2.1 as 2.1,
that seems reasonable.
--Thilo
