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/01/11 14:28:35 UTC

[VOTE] Release Apache Jackrabbit 1.4

Hi,

I have posted a candidate for the Apache Jackrabbit 1.4 release at

    http://people.apache.org/~jukka/jackrabbit/1.4/

See the included RELEASE-NOTES.txt file for details on release
contents and latest changes. The release candidate was built from
http://svn.apache.org/repos/asf/jackrabbit/tags/1.4.

The release candidate consists of the traditional source and binary
packages as well as a staged org/apache/jackrabbit Maven repository
where the new artifacts have been included.

Please vote on releasing these packages as Apache Jackrabbit 1.4. The
vote is on for the next 72 hours and passes if at least three +1 votes
are cast.

   [ ] +1 Release the packages as Apache Jackrabbit 1.4
   [ ] -1 Do not release the packages because...

For the record, the MD5 checksums of the release artifacts are:

    8cad76e3501645225ee587bc07e06ced  sources/jackrabbit-1.4-src.jar
    a510565faf28da1ce79d5de74b1daf84  binaries/jackrabbit-api-1.4.jar
    c74eeca4ee3a80469ba2662f5dbb801e  binaries/jackrabbit-classloader-1.4.jar
    7f6e85527ab6a68c16e44d08b8d34999  binaries/jackrabbit-core-1.4.jar
    ded20e01c143afbc6a0528882c4021e9  binaries/jackrabbit-jca-1.4.jar
    2a8f44eeae36a601f9cea05cf8ac5d88  binaries/jackrabbit-jca-1.4.rar
    083fe6c2389fd37fdafe0354efbb9d12  binaries/jackrabbit-jcr2spi-1.4.jar
    867005110fea76c003172179239604eb  binaries/jackrabbit-jcr-commons-1.4.jar
    c69939a4d307be5808a542cadc6eaa49  binaries/jackrabbit-jcr-rmi-1.4.jar
    e929bc02149a41343ea1e4c1b521a47b  binaries/jackrabbit-jcr-server-1.4.jar
    3c664e2feda68a21d9fb4a151ff521b4  binaries/jackrabbit-jcr-servlet-1.4.jar
    7d83bb06fad80d56e439875a1c6e7cf4  binaries/jackrabbit-jcr-tests-1.4.jar
    51d57719e42dc07abf76a0d40d8a542c  binaries/jackrabbit-ocm-1.4.jar
    9377818268fbc7f48336ca85f4a120b9  binaries/jackrabbit-ocm-1.4-jdk14.jar
    88370f12106d98c06211ece95059e487
binaries/jackrabbit-ocm-nodemanagement-1.4.jar
    b1f5a9d3ff4ca29bb431873e8d0de8c6  binaries/jackrabbit-spi-1.4.jar
    30f588c345090fa5b23184372f51310e  binaries/jackrabbit-spi2jcr-1.4.jar
    42ec91d0cd72611a640cdcadbcd5b9ad  binaries/jackrabbit-spi-commons-1.4.jar
    ca355d0bafdf7102fe3bc5f99d7b3a9f
binaries/jackrabbit-text-extractors-1.4.jar
    1c480f30f44cb01245c8ec4238cc54b8  binaries/jackrabbit-webapp-1.4.jar
    235a7d11611f210ef87302f535caabe6  binaries/jackrabbit-webapp-1.4.war
    b40b8afb710a405bfe18b30624f4b7eb  binaries/jackrabbit-webdav-1.4.jar

Here's my +1 vote.

PS. See http://www.nabble.com/Release-auditing-guidelines-p8481069.html
for release auditing guidelines I wrote last year.

BR,

Jukka Zitting

Re: [VOTE] Release Apache Jackrabbit 1.4

Posted by Esteban Franqueiro <es...@bea.com>.
> Hi,
>
> On Jan 11, 2008 4:26 PM, Esteban Franqueiro <es...@bea.com> wrote:
>> In the release notes, shouldn't there be a note about the data store?
>
> I mention a "new storage model for binary content" in addition to
> listing the data store feature issues in the change log.

Ja! Sorry, I must have overlooked that paragraph.

> We don't yet have too much documentation especially on migrating
> existing repositories to using the data store and the default
> configuration still doesn't use it, so I didn't want to put too much
> emphasis on the feature. I'd consider the date store as a beta-level
> new feature in 1.4.

I agree. And regarding that I'm still going to stress-test the data store. I would've like to be 
able to do it before the actual release, but I couldn't as I'm still updating our app to 1.4 (BTW, 
the answers I got were very useful).
Regards,

Esteban Franqueiro
esteban.franqueiro@bea.com 


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

Re: [VOTE] Release Apache Jackrabbit 1.4

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Jan 11, 2008 4:26 PM, Esteban Franqueiro <es...@bea.com> wrote:
> In the release notes, shouldn't there be a note about the data store?

I mention a "new storage model for binary content" in addition to
listing the data store feature issues in the change log.

We don't yet have too much documentation especially on migrating
existing repositories to using the data store and the default
configuration still doesn't use it, so I didn't want to put too much
emphasis on the feature. I'd consider the date store as a beta-level
new feature in 1.4.

BR,

Jukka Zitting

Re: [VOTE] Release Apache Jackrabbit 1.4

Posted by Esteban Franqueiro <es...@bea.com>.
Hi Jukka.
In the release notes, shouldn't there be a note about the data store?
Regards,

Esteban Franqueiro
esteban.franqueiro@bea.com

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

Re: [VOTE] Release Apache Jackrabbit 1.4

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Jan 11, 2008 4:16 PM, Marcel May <ma...@consol.de> wrote:
> Bundled DB PM + JNDI issue 1305
> (https://issues.apache.org/jira/browse/JCR-1305)
> This causes troubles in an application server environment and only
> requires a very
> small fix as suggested in the issue.
>
> It would be great if we could get this fixed for 1.4 release.

I was considering that, but decided that we need to draw the line
somewhere and just put the release out instead of adding more small
changes. The delta between 1.4-rc1 and 1.4 is probably already too
big.

We can treat JCR-1305 as a bug and include it in a 1.4.1 release as
long as we implement it in a way that shouldn't affect existing
configurations. Something like:

    if (user == null || password == null) {
        return ds.getConnection();
    } else {
        return ds.getConnection(user, password);
    }

BR,

Jukka Zitting

Re: [VOTE] Release Apache Jackrabbit 1.4

Posted by Marcel May <ma...@consol.de>.
-1 (non binding):
 
Bundled DB PM + JNDI issue 1305 
(https://issues.apache.org/jira/browse/JCR-1305)
This causes troubles in an application server environment and only 
requires a very
small fix as suggested in the issue.

It would be great if we could get this fixed for 1.4 release.

Cheers,
Marcel

Re: [VOTE] Release Apache Jackrabbit 1.4

Posted by Stefan Guggisberg <st...@gmail.com>.
hi jukka

i downloaded the source code, verified the signatures and checksums,
built the binaries from source, ran the test suites and checked the license
headers:

+1 Release the packages as Apache Jackrabbit 1.4

cheers
stefan

On Jan 11, 2008 2:28 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> I have posted a candidate for the Apache Jackrabbit 1.4 release at
>
>     http://people.apache.org/~jukka/jackrabbit/1.4/
>
> See the included RELEASE-NOTES.txt file for details on release
> contents and latest changes. The release candidate was built from
> http://svn.apache.org/repos/asf/jackrabbit/tags/1.4.
>
> The release candidate consists of the traditional source and binary
> packages as well as a staged org/apache/jackrabbit Maven repository
> where the new artifacts have been included.
>
> Please vote on releasing these packages as Apache Jackrabbit 1.4. The
> vote is on for the next 72 hours and passes if at least three +1 votes
> are cast.
>
>    [ ] +1 Release the packages as Apache Jackrabbit 1.4
>    [ ] -1 Do not release the packages because...
>
> For the record, the MD5 checksums of the release artifacts are:
>
>     8cad76e3501645225ee587bc07e06ced  sources/jackrabbit-1.4-src.jar
>     a510565faf28da1ce79d5de74b1daf84  binaries/jackrabbit-api-1.4.jar
>     c74eeca4ee3a80469ba2662f5dbb801e  binaries/jackrabbit-classloader-1.4.jar
>     7f6e85527ab6a68c16e44d08b8d34999  binaries/jackrabbit-core-1.4.jar
>     ded20e01c143afbc6a0528882c4021e9  binaries/jackrabbit-jca-1.4.jar
>     2a8f44eeae36a601f9cea05cf8ac5d88  binaries/jackrabbit-jca-1.4.rar
>     083fe6c2389fd37fdafe0354efbb9d12  binaries/jackrabbit-jcr2spi-1.4.jar
>     867005110fea76c003172179239604eb  binaries/jackrabbit-jcr-commons-1.4.jar
>     c69939a4d307be5808a542cadc6eaa49  binaries/jackrabbit-jcr-rmi-1.4.jar
>     e929bc02149a41343ea1e4c1b521a47b  binaries/jackrabbit-jcr-server-1.4.jar
>     3c664e2feda68a21d9fb4a151ff521b4  binaries/jackrabbit-jcr-servlet-1.4.jar
>     7d83bb06fad80d56e439875a1c6e7cf4  binaries/jackrabbit-jcr-tests-1.4.jar
>     51d57719e42dc07abf76a0d40d8a542c  binaries/jackrabbit-ocm-1.4.jar
>     9377818268fbc7f48336ca85f4a120b9  binaries/jackrabbit-ocm-1.4-jdk14.jar
>     88370f12106d98c06211ece95059e487
> binaries/jackrabbit-ocm-nodemanagement-1.4.jar
>     b1f5a9d3ff4ca29bb431873e8d0de8c6  binaries/jackrabbit-spi-1.4.jar
>     30f588c345090fa5b23184372f51310e  binaries/jackrabbit-spi2jcr-1.4.jar
>     42ec91d0cd72611a640cdcadbcd5b9ad  binaries/jackrabbit-spi-commons-1.4.jar
>     ca355d0bafdf7102fe3bc5f99d7b3a9f
> binaries/jackrabbit-text-extractors-1.4.jar
>     1c480f30f44cb01245c8ec4238cc54b8  binaries/jackrabbit-webapp-1.4.jar
>     235a7d11611f210ef87302f535caabe6  binaries/jackrabbit-webapp-1.4.war
>     b40b8afb710a405bfe18b30624f4b7eb  binaries/jackrabbit-webdav-1.4.jar
>
> Here's my +1 vote.
>
> PS. See http://www.nabble.com/Release-auditing-guidelines-p8481069.html
> for release auditing guidelines I wrote last year.
>
> BR,
>
> Jukka Zitting
>

[RESULT] [VOTE] Release Apache Jackrabbit 1.4

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Jan 11, 2008 3:28 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Please vote on releasing these packages as Apache Jackrabbit 1.4. The
> vote is on for the next 72 hours and passes if at least three +1 votes
> are cast.

The vote passes with the following three binding +1 votes and one
non-binding -1 vote.

    +1 Jukka Zitting
    +1 Felix Meschberger
    +1 Stefan Guggisberg
    -1 Marcel May (non-binding)

(I will try to address Marcel's concern in 1.4.1.)

Thanks for voting! I'll put the release up for the mirrors and follow
up tomorrow with the official release announcement.

BR,

Jukka Zitting

Re: [VOTE] Release Apache Jackrabbit 1.4

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Jan 11, 2008 4:56 PM, Felix Meschberger <fm...@gmail.com> wrote:
> [...]ArrayHitsTest.java

Ah, sorry for missing that. I thought I had covered everything already
in JCR-1283 and didn't pay too much attention on changes that went in
after that.

> does not have a license header at all. Likewise almost all configuration
> files do not have headers either. I suggest that headers are added to
> these configuration files, where the file syntax supports comments, such
> as XML files etc.

I think it's only the jaas.config files that miss license headers. The
JAAS configuration format doesn't allow comments, so we'll have to
live without them.

BR,

Jukka Zitting

Re: [VOTE] Release Apache Jackrabbit 1.4

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

I checked the signatures and license headers, and with a single
exception (see below) the headers are ok (according to rat) and I think
we can live with the exception.

+1

Thanks Jukka for working this out !

The exception: The test case in the src package

jackrabbit-1.4/jackrabbit-core/src/test/java/org/apache/jackrabbit/core/query/lucene/hits/ArrayHitsTest.java

does not have a license header at all. Likewise almost all configuration
files do not have headers either. I suggest that headers are added to
these configuration files, where the file syntax supports comments, such
as XML files etc.

Regards and have a nice weekend
Felix

Am Freitag, den 11.01.2008, 15:28 +0200 schrieb Jukka Zitting:
> Hi,
> 
> I have posted a candidate for the Apache Jackrabbit 1.4 release at
> 
>     http://people.apache.org/~jukka/jackrabbit/1.4/
> 
> See the included RELEASE-NOTES.txt file for details on release
> contents and latest changes. The release candidate was built from
> http://svn.apache.org/repos/asf/jackrabbit/tags/1.4.
> 
> The release candidate consists of the traditional source and binary
> packages as well as a staged org/apache/jackrabbit Maven repository
> where the new artifacts have been included.
> 
> Please vote on releasing these packages as Apache Jackrabbit 1.4. The
> vote is on for the next 72 hours and passes if at least three +1 votes
> are cast.
> 
>    [ ] +1 Release the packages as Apache Jackrabbit 1.4
>    [ ] -1 Do not release the packages because...
> 
> For the record, the MD5 checksums of the release artifacts are:
> 
>     8cad76e3501645225ee587bc07e06ced  sources/jackrabbit-1.4-src.jar
>     a510565faf28da1ce79d5de74b1daf84  binaries/jackrabbit-api-1.4.jar
>     c74eeca4ee3a80469ba2662f5dbb801e  binaries/jackrabbit-classloader-1.4.jar
>     7f6e85527ab6a68c16e44d08b8d34999  binaries/jackrabbit-core-1.4.jar
>     ded20e01c143afbc6a0528882c4021e9  binaries/jackrabbit-jca-1.4.jar
>     2a8f44eeae36a601f9cea05cf8ac5d88  binaries/jackrabbit-jca-1.4.rar
>     083fe6c2389fd37fdafe0354efbb9d12  binaries/jackrabbit-jcr2spi-1.4.jar
>     867005110fea76c003172179239604eb  binaries/jackrabbit-jcr-commons-1.4.jar
>     c69939a4d307be5808a542cadc6eaa49  binaries/jackrabbit-jcr-rmi-1.4.jar
>     e929bc02149a41343ea1e4c1b521a47b  binaries/jackrabbit-jcr-server-1.4.jar
>     3c664e2feda68a21d9fb4a151ff521b4  binaries/jackrabbit-jcr-servlet-1.4.jar
>     7d83bb06fad80d56e439875a1c6e7cf4  binaries/jackrabbit-jcr-tests-1.4.jar
>     51d57719e42dc07abf76a0d40d8a542c  binaries/jackrabbit-ocm-1.4.jar
>     9377818268fbc7f48336ca85f4a120b9  binaries/jackrabbit-ocm-1.4-jdk14.jar
>     88370f12106d98c06211ece95059e487
> binaries/jackrabbit-ocm-nodemanagement-1.4.jar
>     b1f5a9d3ff4ca29bb431873e8d0de8c6  binaries/jackrabbit-spi-1.4.jar
>     30f588c345090fa5b23184372f51310e  binaries/jackrabbit-spi2jcr-1.4.jar
>     42ec91d0cd72611a640cdcadbcd5b9ad  binaries/jackrabbit-spi-commons-1.4.jar
>     ca355d0bafdf7102fe3bc5f99d7b3a9f
> binaries/jackrabbit-text-extractors-1.4.jar
>     1c480f30f44cb01245c8ec4238cc54b8  binaries/jackrabbit-webapp-1.4.jar
>     235a7d11611f210ef87302f535caabe6  binaries/jackrabbit-webapp-1.4.war
>     b40b8afb710a405bfe18b30624f4b7eb  binaries/jackrabbit-webdav-1.4.jar
> 
> Here's my +1 vote.
> 
> PS. See http://www.nabble.com/Release-auditing-guidelines-p8481069.html
> for release auditing guidelines I wrote last year.
> 
> BR,
> 
> Jukka Zitting