james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Brewin" <sbre...@synsys.com>
Subject RE: [jira] Resolved: (JAMES-150) NullPointer Exception when mail does not contain any Received: headers
Date Mon, 09 Feb 2004 18:35:06 GMT
Serge Knystautas wrote:
> Steve Brewin wrote:
> >>We need to sort out releases quick... to mark this as fixed
> >>for release
> >>2.1, something that went out over a year ago, won't really help us.
> >
> > Oops, you are right! I was getting confused between
> branches and releases. I
> > wonder if we can close releases in Jira so its not possible
> to select a
> > passed release as a fix target. This would stop this kind of error.
> Not really.  Basically the fix-for and reported-against use the same
> list of versions.  You can archive versions, but then someone can't
> report an issue against that release.  We *can* mark versions as
> released or not, so it's a bit easier to see what is
> considered release.
> > I don't know if its possible in Jira to rename releases. If
> not, then a
> > release name of "Next" won't help as all fixes for all
> releases will end up
> > with a release of "Next"!
> We can rename and reorder versions, and you can also delete a version
> and say which version all issues marked to that should be
> changed to.  I
> didn't mean "Next" was a great name, but just if in the short-term we
> weren't sure what the next release name woud be.
> > Having a concrete release name, such as "2.2a17" for a fix
> target seems
> > easiest to me. Only being able to select future releases as
> fix targets
> > would help prevent dumb errors.
> Ok cool.  You should be able to go into Administration and edit the
> releases for this project, and hopefully the interface will make some
> sense.  I can do that later tonight if you don't have time/interest.

OK. Things should be straightened out now.

I believe 2.2.0a15 was the last release, so 2.2.0a16 will be the next. If
I'm wrong we can rename releases as you pointed out.

- Added versions '2.2.0a15' and '2.2.0a16'.
- Switched all versions except '2.2.0a16', '3.0' and 'unspecified' to
- Updated the fetchmail issues to fit the above reality.

Not sure what to do about 'unspecified', so I left it as unreleased. I
reckon it should be released and we should use 'Unknown' for a fix with no
target release version. Hopefully, this would mean that 'unspecified' is
only used for reporting problems. What do you think?

-- Steve

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message