Are the issues Jukka has listed below required for AR2?
If not, how about a release is created and announced?
If they are, all but one (RIVER-268) have been assigned, and 5 have a
status of open. Out of these what are blockers for the release?
Thanks
Dennis
On Oct 16, 2008, at 620AM, Jukka Zitting wrote:
But it's a good idea to send summary updates on all the remaining open
issues so people have an idea of what still needs to be done before
the release. The current list of open issues tagged for AR2 is:
Tasks
[RIVER-268] Javadoc and API docs(specs) in project
New features
[RIVER-292] The service browser should provide support for the
ServiceUI ...
[RIVER-295] Support configurable option to prevent from popup
windows ...
Improvements
[RIVER-147] PreferredClassProvider protected method to determine ...
[RIVER-160] add TrustEquivalence to browser's list of ...
[RIVER-218] FiddlerImpl catch Throwable blocks should also catch
Throwable
Bug fixes
[RIVER-213] (DOC) - JoinManger has typo in javadoc (missing </
code> ...
[RIVER-257] Fiddler - should implement toString() for the various ...
[RIVER-258] JoinManager - race when terminate is called after
attribute ...
[RIVER-265] PreferredClassProvider performs 'unlucky' caching
I'm not sure if all of these are really needed for AR2.
BR,
Jukka Zitting
