jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Re: Bundle Persistence Manager
Date Tue, 20 Feb 2007 15:18:07 GMT

On 2/20/07, Tobias Bocanegra <tobias.bocanegra@day.com> wrote:
> we (day software) offer our set of bundle persistence managers to the
> jackrabbit project. those pms combine the node and property states
> into a single bundle and store them together. this improves
> performance and reduces storage-memory overhead (no exact numbers
> available). The bundle pms also have a "bundle-cache" that does a
> memory sensitive caching of the bundles and a negative cache for
> non-existent bundles. small binary properties are inlined into the
> bundle rather than stored in the blob store.

Excellent, this will be a welcome addition to Jackrabbit!

With my PMC chair hat on:

Since this is a codebase that has been in development outside the ASF,
we need to follow the IP clearance process described in
http://incubator.apache.org/ip-clearance/. The exact steps to follow

1. You attach the contributed code in JCR-755 (preferably as a single
file so we can use a MD5 or SHA1 checksum to accurately refer to it)

2. You call a vote for the Jackrabbit PMC to accept the contribution
(this is required to ensure that the PMC is committed to taking over
the maintenance of the codebase)

3. Day files a software grant
(http://www.apache.org/licenses/software-grant.txt) for the
contributed code.

4. The ASF Secretary acknowledgest the grant.

5. I fill in the the IP clearance form and call a vote for the
Incubator PMC to check and accept the clearance.

6. Once accepted, I'll notify you of the green light to proceed.

7. You resolve JCR-755 by adding the contributed code to the
Jackrabbit codebase.

Let me know if you need help with any of the procedural details.

We should apply the same process also to the packaging codebase for JCR-733.

PS. We should have done this already when the SPI codebase was
introduced. The ASF board noted about this, but the issue was not
critical enough to require after-the-fact actions. In any case we
should do things by the book this time.


Jukka Zitting

View raw message