You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Julian Reschke <ju...@greenbytes.de> on 2015/05/22 13:54:26 UTC
2.* release plans, was: [ANNOUNCE] Apache Jackrabbit 2.10.1 released
On 2015-05-22 07:52, Julian Reschke wrote:
> OK,
>
> we have dealt with the emergency, but there's some aftermath left to do.
>
> - We need to do proper releases of 2.8, 2.6, 2.4, 2.2, and 2.0.
>
> - Once done with that, we should announce end-of-life for 2.2 and 2.0.
>
> Do we have any volunteers for doing some of the releases?
>
> Best regards, Julian
In the meantime I have
1) created versions for future 2.4/6/8 release in JIRA, and
2) prepared the release notes for 2.0/2/4/6/8 in Subversion
With respect to starting the release: we probably need wait until early
next week, otherwise we'll have a weekend and a public holiday (at least
here) within the 72 hours period.
Best regards, Julian
Re: 2.* release plans, was: [ANNOUNCE] Apache Jackrabbit 2.10.1
released
Posted by Marcel Reutegger <mr...@adobe.com>.
Hi,
this is fixed in Jackrabbit 2.10.1. See:
https://svn.apache.org/repos/asf/jackrabbit/tags/jackrabbit-2.10.1/jackrabb
it-core/src/main/java/org/apache/jackrabbit/core/query/lucene/NodeIndexer.j
ava
and JCR-3871 for the related JIRA issue.
Regards
Marcel
On 27/05/15 20:31, "hsp" wrote:
>Hi,
>
>There is a NPE problem in jack 2.10 .
>in line
>at
>org.apache.jackrabbit.core.query.lucene.NodeIndexer.isSupportedMediaType(N
>odeIndexer.java:934)
>
>
> supportedMediaTypes = parser.getSupportedTypes(null);
>
>would be
> supportedMediaTypes = parser.getSupportedTypes(new ParseContext());
>
>
>
>
>
>
>--
>View this message in context:
>http://jackrabbit.510166.n4.nabble.com/ANNOUNCE-Apache-Jackrabbit-2-10-1-r
>eleased-tp4662462p4662501.html
>Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
Re: 2.* release plans, was: [ANNOUNCE] Apache Jackrabbit 2.10.1
released
Posted by hsp <pi...@ibest.com.br>.
Hi,
There is a NPE problem in jack 2.10 .
in line
at
org.apache.jackrabbit.core.query.lucene.NodeIndexer.isSupportedMediaType(NodeIndexer.java:934)
supportedMediaTypes = parser.getSupportedTypes(null);
would be
supportedMediaTypes = parser.getSupportedTypes(new ParseContext());
--
View this message in context: http://jackrabbit.510166.n4.nabble.com/ANNOUNCE-Apache-Jackrabbit-2-10-1-released-tp4662462p4662501.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
Re: 2.* release plans, was: [ANNOUNCE] Apache Jackrabbit 2.10.1
released
Posted by Marcel Reutegger <mr...@adobe.com>.
Hi,
it has been a while since I last did a release on a windows
box. IIRC I used putty/pageant on a regular windows command
line.
I will do the 2.8 release.
Regards
Marcel
On 27/05/15 10:25, "Julian Reschke" wrote:
>On 2015-05-22 13:54, Julian Reschke wrote:
>> On 2015-05-22 07:52, Julian Reschke wrote:
>>> OK,
>>>
>>> we have dealt with the emergency, but there's some aftermath left to
>>>do.
>>>
>>> - We need to do proper releases of 2.8, 2.6, 2.4, 2.2, and 2.0.
>>>
>>> - Once done with that, we should announce end-of-life for 2.2 and 2.0.
>>>
>>> Do we have any volunteers for doing some of the releases?
>>>
>>> Best regards, Julian
>>
>> In the meantime I have
>>
>> 1) created versions for future 2.4/6/8 release in JIRA, and
>>
>> 2) prepared the release notes for 2.0/2/4/6/8 in Subversion
>>
>> With respect to starting the release: we probably need wait until early
>> next week, otherwise we'll have a weekend and a public holiday (at least
>> here) within the 72 hours period.
>
>...in the meantime I tried to do a release:prepare. It currently fails
>for me (Windows, Cygwin). Does anybody else who is on Windows have
>instructions on how to get this done?
>
>Alternatively, it would be great if other committers with release
>experience could help out for some of these branches.
>
>Best regards, Julian
Re: 2.* release plans, was: [ANNOUNCE] Apache Jackrabbit 2.10.1 released
Posted by Julian Reschke <ju...@greenbytes.de>.
On 2015-05-22 13:54, Julian Reschke wrote:
> On 2015-05-22 07:52, Julian Reschke wrote:
>> OK,
>>
>> we have dealt with the emergency, but there's some aftermath left to do.
>>
>> - We need to do proper releases of 2.8, 2.6, 2.4, 2.2, and 2.0.
>>
>> - Once done with that, we should announce end-of-life for 2.2 and 2.0.
>>
>> Do we have any volunteers for doing some of the releases?
>>
>> Best regards, Julian
>
> In the meantime I have
>
> 1) created versions for future 2.4/6/8 release in JIRA, and
>
> 2) prepared the release notes for 2.0/2/4/6/8 in Subversion
>
> With respect to starting the release: we probably need wait until early
> next week, otherwise we'll have a weekend and a public holiday (at least
> here) within the 72 hours period.
...in the meantime I tried to do a release:prepare. It currently fails
for me (Windows, Cygwin). Does anybody else who is on Windows have
instructions on how to get this done?
Alternatively, it would be great if other committers with release
experience could help out for some of these branches.
Best regards, Julian