You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by Jukka Zitting <ju...@gmail.com> on 2008/04/02 22:06:40 UTC

Known issues in release notes (Was: svn commit: r644024 - /jackrabbit/branches/1.4/jackrabbit-jcr-rmi/RELEASE-NOTES.txt)

Hi,

On Wed, Apr 2, 2008 at 10:52 PM,  <fm...@apache.org> wrote:
>  +  Known Issues:
>  +  [JCR-300]  Streamline the JCR-RMI network interfaces
>  +  [JCR-301]  Improve the JCR-RMI Value classes
>  +  [JCR-781]  RMI: Allow custom socket factories
>  +  [JCR-1317] Add a MBean method to programatically create a new Workspace.
>  +  [JCR-1457] Restart of RMI-component fails (because it's not ...

I've typically only included bug reports in the list of known issues,
as those are the only ones that users really need to be aware of if
they expect the component to work as documented.

The Jira query I've used for generating the known issue lists is:

    Project: Jackrabbit
    Issue Type: Bug
    Components: <release component(s)>
    Resolution: Unresolved

For jcr-rmi the only known issue based on that criteria would have
been JCR-1457, but it seems more of an jackrabbit-webapp issue and
I've updated it accordingly.

BR,

Jukka Zitting

Re: Known issues in release notes (Was: svn commit: r644024 - /jackrabbit/branches/1.4/jackrabbit-jcr-rmi/RELEASE-NOTES.txt)

Posted by Felix Meschberger <fm...@gmail.com>.

Hi Jukka,

Am Mittwoch, den 02.04.2008, 23:06 +0300 schrieb Jukka Zitting:
> Hi,
> 
> On Wed, Apr 2, 2008 at 10:52 PM,  <fm...@apache.org> wrote:
> >  +  Known Issues:
> >  +  [JCR-300]  Streamline the JCR-RMI network interfaces
> >  +  [JCR-301]  Improve the JCR-RMI Value classes
> >  +  [JCR-781]  RMI: Allow custom socket factories
> >  +  [JCR-1317] Add a MBean method to programatically create a new Workspace.
> >  +  [JCR-1457] Restart of RMI-component fails (because it's not ...
> 
> I've typically only included bug reports in the list of known issues,
> as those are the only ones that users really need to be aware of if
> they expect the component to work as documented.

Makes sense.

> 
> The Jira query I've used for generating the known issue lists is:
> 
>     Project: Jackrabbit
>     Issue Type: Bug
>     Components: <release component(s)>
>     Resolution: Unresolved
> 
> For jcr-rmi the only known issue based on that criteria would have
> been JCR-1457, but it seems more of an jackrabbit-webapp issue and
> I've updated it accordingly.

In this case, there would be no known issues. The better ;-) I will fix
this before release.

Regards
Felix