This was extracted (@ 2024-04-17 21:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Project Status: The project is ongoing with moderate activity. There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (18 years ago). There are currently 59 committers and 59 PMC members in this project. The Committer-to-PMC ratio is 1:1, because all committers automatically become PMC members. Community changes, past quarter: - No new PMC members. Last addition was Nuno Santos on 2023-11-14. - No new committers. Last addition was Nuno Santos on 2023-11-13. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The project website sources were migrated from SVN to Git in January. Due to its size, the generated website content still resides in SVN. In January the team voted to require Java 11 for the next feature release of Apache Jackrabbit (2.22.0). RMI support in Apache Jackrabbit was deprecated in February and the feature will be removed in the next feature release. ## Community Health: The project is generally healthy with a continuous stream of traffic mostly on JIRA issues and GitHub pull requests reflecting activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.20.14 was released on 2024-01-11 - jackrabbit-2.21.23 was released on 2024-02-08 - jackrabbit-2.21.25 was released on 2024-02-26 ## JIRA activity: - 147 JIRA tickets created in the last 3 months - 114 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Project Status: The project is ongoing with moderate activity. There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (18 years ago) There are currently 59 committers and 59 PMC members in this project. The Committer-to-PMC ratio is 1:1, because all committers automatically become PMC members. Community changes, past quarter: - Nuno Santos was added to the PMC on 2023-11-14 - Nuno Santos was added as committer on 2023-11-13 ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. In October a significant code contribution to Jackrabbit Oak was made by a non-committer (Lucas Weitzendorf). The contribution adds support for parallel compaction of a segment store. Throughout the last quarter the indexing component of Jackrabbit Oak has seen a lot of activity. The team has been working on a more efficient way to index large repositories. Migration to Jakarta APIs saw some progress with good collaboration between different Apache project teams. However, the migration requires many changes while the team also wants to keep modules compatible with the current version of the Servlet API. In December the classic Jackrabbit code base was migrated from SVN to Git. The only remaining module in SVN is the project website, but there are plans to migrate that as well. ## Community Health: The project is generally healthy with a continuous stream of traffic mostly on JIRA issues and GitHub pull requests reflecting activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.20.12 was released on 2023-09-08 - jackrabbit-oak-1.22.17 was released on 2023-09-15 - jackrabbit-2.21.20 was released on 2023-10-11 - jackrabbit-oak-1.58.0 was released on 2023-10-16 - jackrabbit-filevault-3.7.2 was released on 2023-11-04 - jackrabbit-2.20.13 was released on 2023-11-07 - filevault-package-maven-plugin-1.3.6 was released on 2023-11-16 - jackrabbit-oak-1.22.18 was released on 2023-12-01 - jackrabbit-oak-1.60.0 was released on 2023-12-06 - jackrabbit-2.21.21 was released on 2023-12-12 - jackrabbit-2.21.22 was released on 2023-12-19 ## JIRA activity: - 140 JIRA tickets created in the last 3 months - 131 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Project Status: The project is ongoing with moderate activity. There are no issues requiring board attention at this time. ## Membership Data: There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Dominique Pfister resigned on 2023-07-17 - No new committers. Last addition was Rishabh Daim on 2023-04-06. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The project team introduced a shaded version of Guava and replaced usage of plain Guava with the shaded version. Only one transitive dependency through an Azure SDK library is left. The plan is to remove this final dependency in the next Jackrabbit Oak release. On June 29th a vulnerability was reported to the security mailing list. The remote code execution in Jackrabbit RMI was handled with CVE-2023-37895 and releases with a fix published on July 25th. ## Community Health: The project is generally healthy with a continuous stream of traffic mostly on JIRA issues and GitHub pull requests reflecting activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-oak-1.22.16 was released on 2023-07-17 - jackrabbit-filevault-3.7.0 was released on 2023-07-19 - jackrabbit-2.21.18 was released on 2023-07-24 - jackrabbit-2.20.11 was released on 2023-07-24 - filevault-package-maven-plugin-1.3.4 was released on 2023-07-24 - jackrabbit-oak-1.54.0 was released on 2023-07-24 - jackrabbit-2.21.19 was released on 2023-08-11 - jackrabbit-oak-1.56.0 was released on 2023-09-01 ## JIRA activity: - 156 JIRA tickets created in the last 3 months - 118 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Project Status: The project is ongoing with moderate activity. There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (17 years ago) There are currently 59 committers and 59 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Rishabh Daim was added to the PMC on 2023-04-06 - Rishabh Daim was added as committer on 2023-04-06 ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The project team started to replace the plain Guava dependency in Jackrabbit Oak with a shaded version. This allows us to more easily update Guava without interfering with users of Jackrabbit Oak. Maintenance of Jackrabbit 2.16.x and Jackrabbit Oak 1.8.x ended in May. Announcements have been sent to inform users to migrate to more recent versions. ## Community Health: The project is generally healthy with a continuous stream of traffic mostly on JIRA issues and GitHub pull requests reflecting activity of the respective component. Concerns were raised on the private email list about lack of or little constructive participation by Jackrabbit committers on the FileVault subproject. There is a split within the committers. Some would like to actively evolve FileVault, while others are mostly happy with the status quo and prefer fewer changes. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-oak-1.50.0 was released on 2023-03-23 - jackrabbit-2.21.16 was released on 2023-04-05 - jackrabbit-oak-1.22.15 was released on 2023-04-07 - jackrabbit-2.20.10 was released on 2023-05-08 - jackrabbit-oak-1.52.0 was released on 2023-05-15 ## JIRA activity: - 167 JIRA tickets created in the last 3 months - 134 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (17 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Joerg Hoh on 2022-07-01. - No new committers. Last addition was Joerg Hoh on 2022-07-01. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The project team decided to require Java 11 as the minimum version for new feature releases. Apache Jackrabbit Oak 1.48.0 is the last release supporting Java 8. A roadmap has been outlined how to update the Guava dependency. The next Jackrabbit Oak release will make usage of deprecated APIs exposing Guava more visible by logging warn and error messages. Later this year the team plans to introduce a wrapped Guava version for Jackrabbit Oak internal use and then remove deprecated APIs. ## Community Health: The project is healthy with a continuous stream of traffic mostly on JIRA issues and GitHub pull requests reflecting activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - filevault-package-maven-plugin-1.3.2 was released on 2022-12-16 - jackrabbit-oak-1.46.0 was released on 2022-12-21 - jackrabbit-2.20.8 was released on 2023-01-09 - jackrabbit-filevault-3.6.8 was released on 2023-01-10 - jackrabbit-oak-1.22.14 was released on 2023-01-19 - jackrabbit-oak-1.48.0 was released on 2023-01-27 - jackrabbit-2.21.15 was released on 2023-02-10 - jackrabbit-2.20.9 was released on 2023-03-10 ## JIRA activity: - 168 JIRA tickets created in the last 3 months - 146 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (17 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Joerg Hoh on 2022-07-01. - No new committers. Last addition was Joerg Hoh on 2022-07-01. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. Discussion started to require Java 11 as a minimum version, because is it getting more difficult to build and run Apache Jackrabbit with Java 8. There is an increased interest in updating the Guava dependency. Unfortunately some Guava classes were used in OSGi packages exported by Jackrabbit. This means an update of Guava in Jackrabbit becomes a breaking change and must be done carefully. The plan is also to hide the Guava dependency from Jackrabbit consumers, so we can more easily update Guava in the future. ## Community Health: The project is healthy with a continuous stream of traffic mostly on the JIRA issues and GitHub pull requests reflecting the activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-filevault-3.6.4 was released on 2022-09-19 - jackrabbit-2.21.13 was released on 2022-10-16 - jackrabbit-oak-1.22.13 was released on 2022-10-17 - jackrabbit-2.20.7 was released on 2022-11-10 - jackrabbit-filevault-3.6.6 was released on 2022-12-05 - jackrabbit-2.21.14 was released on 2022-12-08 ## JIRA activity: - 150 JIRA tickets created in the last 3 months - 144 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class websites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications, and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (16 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Joerg Hoh was added to the PMC on 2022-07-01 - Joerg Hoh was added as committer on 2022-07-01 ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The team decided to introduce a GitHub action that adds a label to open pull requests for Jackrabbit Oak that are older than two years. The intention is to reduce the number of open or abandoned pull requests and notify contributors to follow up on their change request. Stale pull requests without further activity are then closed automatically after 30 days. ## Community Health: The project is healthy with a continuous stream of traffic mostly on the JIRA issues and GitHub pull requests reflecting the activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.21.11 was released on 2022-06-10 - jackrabbit-2.20.6 was released on 2022-07-07 - jackrabbit-oak-1.44.0 was released on 2022-07-15 - jackrabbit-oak-1.22.12 was released on 2022-07-19 - jackrabbit-2.21.12 was released on 2022-08-11 - jackrabbit-2.16.10 was released on 2022-09-10 ## JIRA activity: - 168 JIRA tickets created in the last 3 months - 144 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (16 years ago) There are currently 57 committers and 57 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jose Andrés Cordero on 2022-02-22. - No new committers. Last addition was Jose Andrés Cordero on 2022-02-22. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The team decided to drop support for maintenance branches of Jackrabbit 2.14 and Jackrabbit Oak 1.6. Announcement messages have been sent out to users to inform them about respective upgrade paths. ## Community Health: The project is healthy with a continuous stream of traffic mostly on the JIRA issues and GitHub pull requests reflecting the activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.20.5 was released on 2022-03-10 - jackrabbit-oak-1.6.23 was released on 2022-03-16 - filevault-package-maven-plugin-1.3.0 was released on 2022-03-26 ## JIRA activity: - 119 JIRA tickets created in the last 3 months - 88 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (16 years ago) There are currently 57 committers and 57 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Felix Meschberger was removed from the PMC on 2022-01-10 - Tobias Bocanegra was removed from the PMC on 2022-02-11 - Jose Andrés Cordero was added to the PMC on 2022-02-22 - Felix Meschberger was removed as committer on 2022-01-10 - Tobias Bocanegra was removed as committer on 2022-02-11 - Jose Andrés Cordero was added as committer on 2022-02-22 ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.42.0 made available on January 12th. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. Impact of the Log4j vulnerability on Jackrabbit modules was moderate. Only vault-cli used Log4j for logging. With JCRVLT-573 this module now also switched to logback and there is no more dependency on Log4j. As precaution even some transitive test dependencies on Log4j have been excluded (OAK-9639 and OAK-9645). ## Community Health: The project is healthy with a continuous stream of traffic mostly on the JIRA issues and GitHub pull requests reflecting the activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.21.9 was released on 2021-12-10 - jackrabbit-filevault-3.5.8 was released on 2021-12-22 - jackrabbit-2.16.9 was released on 2022-01-07 - jackrabbit-oak-1.42.0 was released on 2022-01-12 - jackrabbit-oak-1.22.10 was released on 2022-01-24 - jackrabbit-oak-1.8.26 was released on 2022-02-04 - jackrabbit-2.21.10 was released on 2022-02-10 - jackrabbit-oak-1.22.11 was released on 2022-02-24 - jackrabbit-filevault-3.6.0 was released on 2022-03-02 ## JIRA activity: - 137 JIRA tickets created in the last 3 months - 108 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (15 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Miroslav Smiljanic on 2020-10-27. - No new committers. Last addition was Miroslav Smiljanic on 2020-10-27. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular maintenance releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.6.22 made available on November 19th. According to planned release schedule of the project, the next feature release for Jackrabbit Oak is long overdue. The majority of Jackrabbit Oak users and committers seems to be using maintenance releases or 3rd party builds created from trunk, reducing the need for new feature releases. The PMC decided to retire the Jackrabbit Oak 1.4 maintenance branch. There will be no more releases from this branch. Users of 1.4.x are encouraged to use 1.40.0 or 1.22.8 instead. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. ## Community Health: The project is healthy with a continuous stream of traffic mostly on the JIRA issues and GitHub pull requests reflecting the activity of the respective component. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-filevault-3.5.4 was released on 2021-10-05 - jackrabbit-2.21.8 was released on 2021-10-08 - jackrabbit-oak-1.22.9 was released on 2021-10-11 - jackrabbit-filevault-maven-plugin-1.2.2 was released on 2021-10-18 - jackrabbit-2.20.4 was released on 2021-11-06 - jackrabbit-oak-1.8.25 was released on 2021-11-08 - jackrabbit-oak-1.6.22 was released on 2021-11-19 - jackrabbit-filevault-3.5.6 was released on 2021-11-25 ## JIRA activity: - 101 JIRA tickets created in the last 3 months - 89 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (15 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Miroslav Smiljanic on 2020-10-27. - No new committers. Last addition was Miroslav Smiljanic on 2020-10-27. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.40.0 that was made available on June 3rd. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The team migrated the Apache Jackrabbit Oak code base from SVN to Git. The migration went mostly smooth with some hiccups related to automated tooling. We now see a healthy increase of pull requests. Over the past three months 96 pull requests were opened, which is a 166% increase. ## Community Health: The project is healthy with a continuous stream of traffic mostly on the dev lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev lists as well as on the various JIRA issues. Commit activity is moderate, mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.20.3 was released on 2021-06-11 - jackrabbit-2.21.7 was released on 2021-07-09 - jackrabbit-oak-1.22.8 was released on 2021-07-20 - jackrabbit-2.16.8 was released on 2021-08-13 - jackrabbit-2.14.10 was released on 2021-09-09 ## JIRA activity: - 169 JIRA tickets created in the last 3 months - 144 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (15 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Miroslav Smiljanic on 2020-10-27. - No new committers. Last addition was Miroslav Smiljanic on 2020-10-27. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.40.0 that was made available on June 3rd. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. Beginning of May the team decided to drop support and deprecate the 2.12 branch of Apache Jackrabbit. Users are encouraged to upgrade to the latest stable versions 2.20 for Java 8 and 2.14 for Java 7 (https://s.apache.org/lm1f3). The team is preparing a migration of the Apache Jackrabbit Oak code base from SVN to Git. The vote for the migration happened on the oak-dev list (https://s.apache.org/mzrnx). ## Community Health: The project is healthy with a continuous stream of traffic mostly on the dev lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev lists as well as on the various JIRA issues. Commit activity is moderate mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.14.9 was released on 2021-03-11 - jackrabbit-oak-1.22.7 was released on 2021-04-13 - jackrabbit-2.21.6 was released on 2021-04-13 - jackrabbit-filevault-3.5.0 was released on 2021-05-25 - jackrabbit-oak-1.6.21 was released on 2021-06-02 - jackrabbit-oak-1.40.0 was released on 2021-06-03 ## JIRA activity: - 104 JIRA tickets created in the last 3 months - 106 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (15 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Miroslav Smiljanic on 2020-10-27. - No new committers. Last addition was Miroslav Smiljanic on 2020-10-27. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.38.0 that was made available on January 28th. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. Mid-February the team decided to drop support and deprecate the 1.2 branch of Apache Jackrabbit Oak. Users are encouraged to upgrade to the latest stable 1.38.0 version (https://s.apache.org/ih4ms). On March 1st a JCRSITE issue was created with spam content. The ticket INFRA-21489 was processed very quickly by the ASF infrastructure team. Thanks! At the same time the Jackrabbit team also noticed Jukka Zitting is set as the project lead for the JCRSITE. Jukka is not active anymore on the project and INFRA-21488 requests a change of the project lead. ## Community Health: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.21.5 was released on 2021-01-14 - jackrabbit-oak-1.22.6 was released on 2021-01-19 - jackrabbit-filevault-3.4.8 was released on 2021-01-22 - filevault-package-maven-plugin-1.1.6 was released on 2021-01-22 - jackrabbit-oak-1.38.0 was released on 2021-01-28 - jackrabbit-2.16.7 was released on 2021-02-11 - jackrabbit-filevault-3.4.10 was released on 2021-03-01 ## JIRA activity: - 110 JIRA tickets created in the last 3 months - 109 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (15 years ago) There are currently 58 committers and 58 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Amrit Verma was added to the PMC on 2020-09-28 - Miroslav Smiljanic was added to the PMC on 2020-10-27 - Amrit Verma was added as committer on 2020-09-15 - Miroslav Smiljanic was added as committer on 2020-10-27 ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.36.0 that was made available on November 17th. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. In October the team noticed security vulnerabilities with Apache Solr versions in use by Apache Jackrabbit Oak (CVE-2020-13941, CVE-2019-17558, CVE-2019-2386). The updated Solr versions with the fixes required a change of the Java version supported by the Jackrabbit Oak maintenance releases. So far Jackrabbit Oak 1.4.x and 1.6.x releases were able to run on Java 7 or newer. With the upgrade of Solr, the minimum version had to be lifted to Java 8 (https://s.apache.org/t40d0). Beginning of December the team decided to drop support and deprecate the 2.18 branch of Apache Jackrabbit. Users are encouraged to upgrade to the latest stable 2.20.x version (https://s.apache.org/llfe1). ## Community Health: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.12.11 was released on 2020-09-10 - jackrabbit-oak-1.34.0 was released on 2020-09-10 - jackrabbit-oak-1.22.5 was released on 2020-10-12 - jackrabbit-2.21.4 was released on 2020-10-22 - jackrabbit-2.20.2 was released on 2020-11-05 - jackrabbit-1.36 was released on 2020-11-17 - jackrabbit-oak-1.8.24 was released on 2020-12-08 ## JIRA activity: - 121 JIRA tickets created in the last 3 months - 121 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (14 years ago) There are currently 56 committers and 56 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Fabrizio Fortino on 2020-05-22. - No new committers. Last addition was Fabrizio Fortino on 2020-05-21. ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.32.0 that was made available on July 16th. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The project migrated CI builds to the new Jenkins service from CloudBees. Builds seem to take longer on the new Jenkins service. ## Community Health: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## Releases: - jackrabbit-2.20.1 was released on 2020-06-08 - jackrabbit-2.21.2 was released on 2020-07-08 - jackrabbit-oak-1.32.0 was released on 2020-07-16 - jackrabbit-oak-1.22.4 was released on 2020-07-17 - jackrabbit-2.21.3 was released on 2020-07-24 - jackrabbit-filevault-3.4.6 was released on 2020-08-03 - filevault-package-maven-plugin-1.1.4 was released on 2020-08-03 - jackrabbit-2.18.6 was released on 2020-08-27 - jackrabbit-oak-1.8.23 was released on 2020-08-27 ## JIRA activity: - 181 JIRA tickets created in the last 3 months - 153 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Jackrabbit was founded 2006-03-15 (14 years ago) There are currently 56 committers and 56 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Fabrizio Fortino was added to the PMC on 2020-05-22 - Vinod Holani was added to the PMC on 2020-05-11 - Martijn Hendriks was removed from the PMC on 2020-06-05 - Fabrizio Fortino was added as committer on 2020-05-21 - Vinod Holani was added as committer on 2020-05-09 - Martijn Hendriks was removed as committer on 2020-06-05 ## Project Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.30.0 that was made available on May 27th. The Apache Jackrabbit FileVault component successfully moved from SVN to GIT (INFRA-20285). Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. On March 26th the team retired the Apache Jackrabbit 2.8 branch. Users of Apache Jackrabbit are encouraged to upgrade to 2.20 for Java 8, 2.14 for Java 7 or 2.12 for Java 6. On March 31st the team retired the Apache Jackrabbit Oak 1.0 branch. Users of Apache Jackrabbit Oak are encouraged to upgrade to 1.26.0 for Java 8, 1.6.20 for Java 7 or 1.2.31 for Java 6. On April 6th the team retired the Apache Jackrabbit Oak 1.10 branch. Users of Apache Jackrabbit Oak are encouraged to upgrade to the latest release of the newest maintenance branch (1.22.3). ## Community Health: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. The report about a potential vulnerability to the security mailing list revealed that only a small group of mostly passive PMC members are subscribed to the security list. The PMC members were asked to subscribe to the security list in order to add active members to the list. In the last 3 months the project added two new committers and PMC members. Martijn Hendriks contacted the PMC and expressed his desire to resign. His resignation from the PMC and committer base became effective on June 5th after his confirmation that he also wants to be removed as a committer. ## Releases: - jackrabbit-2.18.5 was released on 2020-03-06 - jackrabbit-oak-1.22.2 was released on 2020-03-16 - jackrabbit-oak-1.8.21 was released on 2020-03-23 - jackrabbit-oak-1.26.0 was released on 2020-03-25 - jackrabbit-2.16.6 was released on 2020-04-07 - jackrabbit-oak-1.22.3 was released on 2020-04-21 - jackrabbit-2.21.1 was released on 2020-05-11 - jackrabbit-oak-1.8.22 was released on 2020-05-23 - jackrabbit-oak-1.30.0 was released on 2020-05-27 ## JIRA activity: - 224 JIRA tickets created in the last 3 months - 236 JIRA tickets closed/resolved in the last 3 months
Apache Jackrabbit: Board Report March 2020 ========================================== ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.24.0 that was made available on January 28th. The upcoming Jackrabbit Oak 1.26.0 release will finally remove usage of java.security.acl.Group, a deprecated interface that will be removed in Java 14. A security issue was reported on January 22nd on the private list. The issue was very well handled by Angela Schreiber and Julian Reschke and within a week new releases were made available that contained a fix. The security issue was initially discovered by Andrew Khoury and Russ Wright of Adobe. Details on the security issue are available in https://issues.apache.org/jira/browse/OAK-8870 and https://nvd.nist.gov/vuln/detail/CVE-2020-1940 Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. Jukka Zitting contacted the PMC and expressed his desire to go emeritus. His resignation from the PMC and committer base became effective after a 72 hour wait period on March 6th. ## PMC changes: - Currently 55 PMC members. - Jukka Zitting resigned on 2020-03-06 - No new PMC members. Last additions were Mohit Kataria and Nitin Gupta on 2019-08-08. ## Committer base changes: - Currently 55 committers. - Jukka Zitting resigned on 2020-03-06 - No new committers. Last additions were Mohit Kataria and Nitin Gupta on 2019-08-08. ## Releases: - jackrabbit-oak-1.10.7 was released on 2019-12-12 - jackrabbit-2.20.0 was released on 2020-01-07 - jackrabbit-oak-1.6.19 was released on 2020-01-13 - jackrabbit-oak-1.22.0 was released on 2020-01-16 - jackrabbit-oak-1.4.25 was released on 2020-01-20 - jackrabbit-oak-1.8.19 was released on 2020-01-23 - jackrabbit-oak-1.24.0 was released on 2020-01-28 - jackrabbit-oak-1.10.8 was released on 2020-01-28 - jackrabbit-oak-1.8.20 was released on 2020-01-31 - jackrabbit-oak-1.6.20 was released on 2020-02-05 - jackrabbit-oak-1.22.1 was released on 2020-02-13 - jackrabbit-2.21.0 was released on 2020-02-14 - jackrabbit-oak-1.4.26 was released on 2020-02-19 ## JIRA activity: - 157 JIRA tickets created in the last 3 months - 130 JIRA tickets closed/resolved in the last 3 months
Apache Jackrabbit: Board Report December 2019 ============================================= ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We continue making regular feature releases of Jackrabbit Oak. The most recent release was Jackrabbit Oak 1.20.0 that was made available on November 25th. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## PMC changes: - Currently 56 PMC members. - No new PMC members. Last additions were Mohit Kataria and Nitin Gupta on 2019-08-08. ## Committer base changes: - Currently 56 committers. - No new committers. Last additions were Mohit Kataria and Nitin Gupta on 2019-08-08. ## Releases: - jackrabbit-2.14.8 was released on 2019-09-12 - jackrabbit-oak-1.8.17 was released on 2019-09-16 - jackrabbit-filevault-3.4.0 was released on 2019-09-16 - jackrabbit-oak-1.10.5 was released on 2019-09-18 - jackrabbit-oak-1.18.0 was released on 2019-09-30 - jackrabbit-2.19.5 was released on 2019-10-10 - jackrabbit-oak-1.6.18 was released on 2019-10-15 - jackrabbit-2.18.4 was released on 2019-11-08 - jackrabbit-oak-1.10.6 was released on 2019-11-12 - jackrabbit-oak-1.20.0 was released on 2019-11-25 - jackrabbit-oak-1.8.18 was released on 2019-11-29 - jackrabbit-2.19.6 was released on 2019-12-10 ## JIRA activity: - 261 JIRA tickets created in the last 3 months - 255 JIRA tickets closed/resolved in the last 3 months
Apache Jackrabbit: Board Report September 2019 ============================================== ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the main development branch are continuously seeing moderate to high activity. We made our 8th feature release of Jackrabbit Oak (1.16) end of July. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. The project stopped supporting Jackrabbit releases from the old 2.10 branch and encouraged users to upgrade to more recent stable versions (https://s.apache.org/c2a1d). Four new committers were added to the project and added to the PMC in the last 3 months. There is an increased interest in the filevault components, visible in higher JIRA activity and mailing list discussions on that topic. A hackathon planned for August was canceled because very few participants registered and no proposals were submitted for the hackathon (https://s.apache.org/i8be9). ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## PMC changes: - Currently 56 PMC members. - 4 new PMC members added in the last 3 months - Dominik Süß was added to the PMC on 2019-07-25 - Konrad Windszus was added to the PMC on 2019-07-22 - Mohit Kataria was added to the PMC on 2019-08-08 - Nitin Gupta was added to the PMC on 2019-08-08 ## Committer base changes: - Currently 56 committers. - 4 new committers added in the last 3 months - Dominik Süß was added as committer on 2019-07-25 - Konrad Windszus was added as committer on 2019-07-22 - Mohit Kataria was added as committer on 2019-08-08 - Nitin Gupta was added as committer on 2019-08-08 ## Releases: - jackrabbit-oak-1.8.14 was released on 2019-07-04 - jackrabbit-oak-1.10.3 was released on 2019-07-15 - jackrabbit-oak-1.8.15 was released on 2019-07-16 - filevault-package-maven-plugin-1.0.4 was released 2019-07-18 - jackrabbit-oak-1.16.0 was released on 2019-07-29 - jackrabbit-oak-1.10.4 was released on 2019-08-16 - jackrabbit-2.19.4 was released on 2019-08-26 - jackrabbit-oak-1.8.16 was released on 2019-08-29 - jackrabbit-2.18.3 was released on 2019-08-30 - jackrabbit-2.16.5 was released on 2019-09-05 ## JIRA activity: - 250 JIRA tickets created in the last 3 months - 234 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. We made our 7th feature release of Jackrabbit Oak (1.14) in June. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Jackrabbit Oak. We changed the release strategy for Jackrabbit Oak. The aim is to reduce the number of maintained branches in the long run and deliver new features to users more frequently. Feature releases are now planned roughly ever two months. See https://s.apache.org/9SYQ on oak-dev for details. A hackathon was held in Basel this quarter (https://s.apache.org/LRn6). Various topics were discussed during the hackathon, including the planned Apache MoinMoin Wiki decommission, making it easier for developers to run proposed changes through a CI/CD pipeline and a prototype for asynchronous commits. As part of the hackathon the Apache Jackrabbit MoinMoin Wiki was archived (https://s.apache.org/7rDN) and the project will no longer use a Wiki system. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring features and improvements in for the next Jackrabbit Oak release. ## PMC changes: - Currently 52 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Woonsan Ko on Tue Sep 25 2018 - The PMC elected Marcel Reutegger as the new chair effective April 17th. ## Committer base changes: - Currently 52 committers. - No new committers added in the last 3 months - Last committer addition was Woonsan Ko at Tue Sep 25 2018 ## Releases: - jackrabbit-2.14.7 was released on Tue Jun 04 2019 - jackrabbit-2.16.4 was released on Wed May 01 2019 - jackrabbit-2.18.1 was released on Fri Apr 12 2019 - jackrabbit-2.18.2 was released on Thu May 23 2019 - jackrabbit-2.19.2 was released on Fri Apr 05 2019 - jackrabbit-2.19.3 was released on Mon May 06 2019 - jackrabbit-oak-1.10.2 was released on Mon Mar 18 2019 - jackrabbit-oak-1.12.0 was released on Tue Apr 09 2019 - jackrabbit-oak-1.14.0 was released on Wed Jun 05 2019 - jackrabbit-oak-1.6.17 was released on Mon Apr 08 2019 - jackrabbit-oak-1.8.13 was released on Mon May 06 2019 - jackrabbit-filevault-3.2.8 was released on Fri Mar 22 2019 ## JIRA activity: - 301 JIRA tickets created in the last 3 months - 270 JIRA tickets closed/resolved in the last 3 months
WHEREAS, the Board of Directors heretofore appointed Michael Dürig (mduerig) to the office of Vice President, Apache Jackrabbit, and WHEREAS, the Board of Directors is in receipt of the resignation of Michael Dürig from the office of Vice President, Apache Jackrabbit, and WHEREAS, the Project Management Committee of the Apache Jackrabbit project has chosen by vote to recommend Marcel Reutegger (mreutegg) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Michael Dürig is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Jackrabbit, and BE IT FURTHER RESOLVED, that Marcel Reutegger be and hereby is appointed to the office of Vice President, Apache Jackrabbit, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Jackrabbit Project Chair, was approved by Unanimous Vote of the directors present.
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. We made our 5th major release of Oak (1.10) in January. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. We are currently discussing a new release strategy for Oak. The aim is to facilitate managing our many branches, releasing of tools and aligning with Oracle's changes in their release and support model for Java. See https://s.apache.org/oM0w, https://s.apache.org/0UKO and https://s.apache.org/tk9u on oak-dev for details. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring the features in for Oak 1.10. ## PMC changes: - Currently 52 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Woonsan Ko on Tue Sep 25 2018 ## Committer base changes: - Currently 52 committers. - No new committers added in the last 3 months - Last committer addition was Woonsan Ko at Tue Sep 25 2018 ## Releases: - 1.10.0 was released on Fri Jan 11 2019 - 1.10.1 was released on Mon Feb 25 2019 - 1.4.24 was released on Tue Jan 08 2019 - 1.6.16 was released on Fri Jan 11 2019 - 1.8.10 was released on Mon Dec 17 2018 - 1.8.11 was released on Mon Jan 14 2019 - 1.9.13 was released on Mon Dec 10 2018 - 2.10.9 was released on Mon Jan 07 2019 - 2.19.0 was released on Fri Dec 07 2018 - 2.19.1 was released on Mon Feb 04 2019 - 2.8.10 was released on Thu Feb 28 2019 ## JIRA activity: - 193 JIRA tickets created in the last 3 months - 183 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. We are running up to our 5th major release of Oak (1.10). Branching is expected to happen early January. A hackathon was held in Bucharest this quarter (https://wiki.apache.org/jackrabbit/Oakathon%20November%202018) where many ideas have been drafted and pondered. Amongst them improvements to our release model and better CI coverage for components depending on 3rd party services (i.e. cloud providers). Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring the features in for Oak 1.10. ## PMC changes: - Currently 52 PMC members. - Woonsan Ko was added to the PMC on Tue Sep 25 2018 ## Committer base changes: - Currently 52 committers. - Woonsan Ko was added as a committer on Tue Sep 25 2018 ## Releases: - Jackrabbit-2.14.6 was released on Thu Sep 06 2018 - Jackrabbit-2.17.6 was released on Mon Oct 01 2018 - Jackrabbit-2.17.7 was released on Fri Nov 23 2018 - Jackrabbit-2.18.0 was released on Fri Nov 30 2018 - Oak-1.2.30 was released on Tue Sep 11 2018 - Oak-1.4.23 was released on Wed Sep 26 2018 - Oak-1.6.14 was released on Wed Sep 12 2018 - Oak-1.6.15 was released on Wed Nov 14 2018 - Oak-1.8.8 was released on Tue Sep 25 2018 - Oak-1.8.9 was released on Mon Nov 05 2018 - Oak-1.9.10 was released on Thu Nov 01 2018 - Oak-1.9.11 was released on Mon Nov 12 2018 - Oak-1.9.12 was released on Mon Nov 26 2018 - Oak-1.9.9 was released on Tue Oct 09 2018 - Vault-3.2.4 was released on Thu Sep 27 2018 - Vault-3.2.6 was released on Fri Nov 30 2018 ## JIRA activity: - 236 JIRA tickets created in the last 3 months - 235 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. The direct binary access feature finally landed in trunk this quarter. This is a major new feature that required effort and coordination from many different domain experts in our comitter base. There is an ongoing effort to understand and be prepared for the impact of the changes in the release model of Java. This includes evaluating whether we can support newer Java versions on some of our branches. We expect to further improve modularisation of our code base to enable independent releases for non core moduls. Discussions and prototyping is expected to happen in the next couple of months. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the various Jira issues. ## PMC changes: - Currently 51 PMC members. - Last PMC addition was Matt Ryan on Mon Sep 10 2018 ## Committer base changes: - Currently 51 committers. - Matt Ryan was added as a committer on Sun Sep 09 2018 ## Releases: - jackrabbit-2.14.6 was released on Sun Sep 02 2018 - jackrabbit-2.16.2 was released on Tue Jun 12 2018 - jackrabbit-2.16.3 was released on Tue Jul 31 2018 - jackrabbit-2.17.4 was released on Tue Jul 10 2018 - jackrabbit-2.17.5 was released on Wed Jul 25 2018 - jackrabbit-2.8.8 was released on Tue Jul 03 2018 - jackrabbit-2.8.9 was released on Mon Jul 16 2018 - vault-3.2 was released on Thu Aug 09 2018 - vault-package-maven-plugin-1.0.3 was released on Fri Aug 31 2018 - oak-1.4.22 was released on Mon Jun 25 2018 - oak-1.6.13 was released on Wed Jul 25 2018 - oak-1.8.5 was released on Tue Jul 03 2018 - oak-1.8.6 was released on Tue Jul 31 2018 - oak-1.8.7 was released on Tue Aug 28 2018 - oak-1.9.5 was released on Tue Jul 03 2018 - oak-1.9.6 was released on Wed Jul 18 2018 - oak-1.9.7 was released on Tue Aug 14 2018 - oak-1.9.8 was released on Tue Aug 28 2018 ## JIRA activity: - 281 JIRA tickets created in the last 3 months - 263 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. This quarter saw the first few unstable releases from the 1.9 branch, which will eventually be leading to the next major release. There is currently an effort under way so simplify Oak deployments by supporting a broader range of Guava versions, which Oak depends on. Also modularisation is being further improved by refactoring and decoupling individual components. On the other end of the spectrum there is ideas, prototyping and evaluations being done regarding cloud friendly persistence back-ends. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the various Jira issues. ## PMC changes: - Currently 50 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Robert Munteanu on Mon May 22 2017 ## Committer base changes: - Currently 50 committers. - No new committers added in the last 3 months - Last committer addition was Alex Deparvu at Fri Jun 09 2017 ## Releases: - oak-1.2.29 was released on Mon Mar 12 2018 - oak-1.0.42 was released on Wed Mar 21 2018 - oak-1.4.21 was released on Wed Apr 04 2018 - oak-1.6.11 was released on Wed Apr 04 2018 - oak-1.6.12 was released on Mon May 28 2018 - oak-1.8.3 was released on Fri May 11 2018 - oak-1.8.4 was released on Thu Jun 07 2018 - oak-1.9.0 was released on Mon Apr 23 2018 - oak-1.9.1 was released on Thu May 10 2018 - oak-1.9.2 was released on Mon May 21 2018 - oak-1.9.3 was released on Mon Jun 04 2018 - jackrabbit-2.10.8 was released on Mon Jun 04 2018 - jackrabbit-2.12.9 was released on Mon May 07 2018 - jackrabbit-2.14.5 was released on Mon Apr 16 2018 - jackrabbit-2.17.2 was released on Wed Apr 04 2018 - jackrabbit-2.17.3 was released on Fri May 11 2018 ## JIRA activity: - 265 JIRA tickets created in the last 3 months - 225 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. This quarter saw the 5th major release of Jackrabbit Oak (1.8). With Oak 1.8 out the team is currently discussing future topics including supporting other persistence back ends, adapting to upcoming Java versions and how to support older Java versions while maintaining backward compatibility without losing the ability to invent. A potential security vulnerability was reported to us by the Apache Security Team on Dec. 25th. See https://s.apache.org/7l6s. After careful evaluation and consideration with the reporter no exploitable issue was identified. See https://s.apache.org/R3Ke. Nevertheless the affected code was improved to avoid a potential future vulnerability through reuse of that code in another context. See OAK-7119. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various Jira issues. Turn around on Jira issues is on the lower end this quarter. It is expected to rise again once feature work on the next release picks up. ## PMC changes: - Currently 50 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Robert Munteanu on Mon May 22 2017 - Roy T. Fielding resigned and was removed from the PMC on March 6th. See https://s.apache.org/l8Kj ## Committer base changes: - Currently 50 committers. - No new committers added in the last 3 months - Last committer addition was Robert Munteanu on Mon May 22 2017 - Roy T. Fielding resigned and was removed from committers on March 6th. https://s.apache.org/l8Kj - Removed orphaned account "alexparvulescu" from committers. This account belonged to Alex Parvulescu who went through a name change to Alex Deparvu and whos new account is "stillalex". ## Releases: - jackrabbit-2.16.1 was released on Tue Feb 06 2018 - jackrabbit-2.17.0 was released on Mon Dec 18 2017 - jackrabbit-2.17.1 was released on Tue Jan 30 2018 - jackrabbit-2.6.10 was released on Mon Mar 05 2018 - jackrabbit-2.8.7 was released on Fri Dec 29 2017 - oak-1.0.40 was released on Fri Jan 05 2018 - oak-1.0.41 was released on Mon Mar 05 2018 - oak-1.2.28 was released on Tue Jan 16 2018 - oak-1.2.29 was released on Mon Mar 12 2018 - oak-1.4.19 was released on Thu Jan 04 2018 - oak-1.4.20 was released on Mon Feb 12 2018 - oak-1.6.10 was released on Mon Mar 05 2018 - oak-1.6.8 was released on Tue Jan 09 2018 - oak-1.6.9 was released on Wed Feb 07 2018 - oak-1.7.14 was released on Wed Dec 20 2017 - oak-1.8.0 was released on Tue Jan 09 2018 - oak-1.8.1 was released on Mon Jan 22 2018 - oak-1.8.2 was released on Tue Feb 06 2018 ## JIRA activity: - 349 JIRA tickets created in the last 3 months - 337 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. We are running up to our 4th major release of Oak (1.8). Branching is expected to happen early January. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues and the desire of the individual contributors to bring the features in for Oak 1.8. ## PMC changes: - Currently 51 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Robert Munteanu on Mon May 22 2017 - The candidate who was offered PMC membership on Sept. 15th subsequently declined ## Committer base changes: - Currently 52 committers. - No new committers added in the last 3 months - Last committer addition was Robert Munteanu on Mon May 22 2017 - The candidate who was offered committership on Sept. 15th subsequently declined ## Releases: - jackrabbit-2.10.7 was released on Wed Dec 06 2017 - jackrabbit-2.12.8 was released on Wed Oct 04 2017 - jackrabbit-2.14.4 was released on Sun Oct 29 2017 - jackrabbit-2.15.7 was released on Sun Oct 22 2017 - jackrabbit-2.15.8 was released on Sun Nov 12 2017 - jackrabbit-2.16 was released on Mon Nov 20 2017 - jackrabbit-2.16.0 was released on Tue Nov 21 2017 - jackrabbit-2.8.6 was released on Sun Sep 24 2017 - vault-3.1.42 was released on Mon Nov 13 2017 - vault-package-maven-plugin-1.0.0 was released on Fri Oct 27 2017 - oak-1.6.6 was released on Mon Oct 30 2017 - oak-1.6.7 was released on Tue Nov 28 2017 - oak-1.7.10 was released on Mon Oct 23 2017 - oak-1.7.11 was released on Tue Nov 07 2017 - oak-1.7.12 was released on Mon Dec 04 2017 - oak-1.7.8 was released on Mon Sep 25 2017 - oak-1.7.9 was released on Mon Oct 09 2017 ## JIRA activity: - 500 JIRA tickets created in the last 3 months - 521 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. Adobe donated the content-package-maven-plugin to us: a Maven plugin that simplifies the creation of content package maven artifacts. The content packages can later be used to install content into a JCR repository using the Apache Jackrabbit FileVault packaging runtime. Filevault was contributed 4 years ago, but we never had a tool to create the packaged during runtime. Adobe's plugin is publicly available, but only in binary form. This contribution brings the source and development closer to the filevault core. Retirement of Apache Jackrabbit 2.4: the Apache Jackrabbit PMC decided that since the 2.4 branch of the project looks like not being used any more to drop support and deprecate this version. Previous branch, tags and releases will still be available for future references, but will not show up on the download page any more. Users are encouraged to upgrade to the latest stable versions (2.14 for Java 7, 2.12 for Java 6). We held an Oak Hackathon August 21st to 25th in Basel - Switzerland, which was free and open to everyone. See https://wiki.apache.org/jackrabbit/Oakathon%20August%202017. There are various talks around Jackrabbit at this year's AdaptTo conference in Berlin Sept. 25th to 27th. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues. ## PMC changes: - Currently 51 PMC members. - No new PMC members added in the last 3 months. Prospects being discussed on the private list. - Last PMC addition was Robert Munteanu on Mon May 22 2017 ## Committer base changes: - Currently 52 committers. - No new committers added in the last 3 months. Prospects being discussed on the private list. - Last committer addition was Robert Munteanu on Mon May 22 2017 ## Releases: - jackrabbit-2.10.6 was released on Mon Jul 03 2017 - jackrabbit-2.14.2 was released on Sat Jul 08 2017 - jackrabbit-2.15.4 was released on Fri Jun 23 2017 - jackrabbit-2.15.5 was released on Mon Jul 31 2017 - jackrabbit-2.15.6 was released on Thu Sep 07 2017 - jackrabbit-2.4.8 was released on Mon Jul 17 2017 - jackrabbit-2.6.9 was released on Mon Sep 04 2017 - vault-3.1.40 was released on Mon Jun 26 2017 - oak-1.0.39 was released on Tue Aug 15 2017 - oak-1.2.27 was released on Wed Aug 02 2017 - oak-1.4.17 was released on Mon Jul 17 2017 - oak-1.4.18 was released on Wed Aug 30 2017 - oak-1.6.2 was released on Mon Jun 12 2017 - oak-1.6.3 was released on Wed Jul 12 2017 - oak-1.6.4 was released on Wed Aug 16 2017 - oak-1.6.5 was released on Mon Sep 04 2017 - oak-1.7.2 was released on Mon Jun 19 2017 - oak-1.7.3 was released on Mon Jul 03 2017 - oak-1.7.4 was released on Wed Jul 19 2017 - oak-1.7.5 was released on Mon Jul 31 2017 - oak-1.7.6 was released on Tue Aug 22 2017 ## JIRA activity: - 364 JIRA tickets created in the last 3 months - 325 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. The PMC resolved the impact of the recently published SHA-1 collisions in the development branch. Back ports to maintenance branches are under consideration. The last quarter saw a much needed and anticipated refactoring of the Oak code base leading to an overall improved and simplified module structure. While some of this work is still ongoing we expect it to have a positive effect on the overall evolvability and maintainability of the code base. We will be holding an Oak Hackathon August 21st to 25th in Basel, Switzerland (https://wiki.apache.org/jackrabbit/Oakathon%20August%202017). Attendance is open and free to everybody wanting to hack Oak. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity is moderate to high mirroring the activity on the JIRA issues. ## PMC changes: - Currently 51 PMC members. - Robert Munteanu was added to the PMC on Mon May 22 2017 ## Committer base changes: - Currently 51 committers. - Robert Munteanu was added as a committer on Mon May 22 2017 ## Releases: - jackrabbit-2.12.7 was released on Mon Apr 03 2017 - jackrabbit-2.14.1 was released on Mon May 29 2017 - jackrabbit-2.15.2 was released on Mon May 01 2017 - jackrabbit-2.15.3 was released on Fri Jun 09 2017 - oak-1.0.38 was released on Tue Mar 28 2017 - oak-1.2.25 was released on Tue Apr 11 2017 - oak-1.2.26 was released on Mon Jun 05 2017 - oak-1.4.15 was released on Mon Apr 03 2017 - oak-1.4.16 was released on Mon Jun 05 2017 - oak-1.6.2 was released on Mon Jun 12 2017 - oak-1.7.0 was released on Wed May 24 2017 - oak-1.7.1 was released on Tue Jun 06 2017 - vault-3.1.38 was released on Mon Mar 27 2017 ## JIRA activity: - 451 JIRA tickets created in the last 3 months - 397 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. This quarter saw the 4th major release of Jackrabbit Oak (1.6). There is an ongoing effort to stabilise our continuous integration (Jenkins) infrastructure. The deployment of the Jira plug-in resulted in further insight and improvements. It also revealed that over 25% of the issues are caused by infrastructure problems rather than our project. The PMC is currently evaluating the impact of the recently published SHA-1 collisions on our products. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component. There is a wide range of topics being discussed on the dev and user lists as well as on the various JIRA issues. Commit activity was moderate to high this quarter with a plunge around the Christmas break. ## PMC changes: - Currently 50 PMC members. - Andrei Dulceanu was added to the PMC on Mon Dec 19 2016 ## Committer base changes: - Currently 50 committers. - Andrei Dulceanu was added as a committer on Fri Dec 16 2016 ## Releases: - Jackrabbit-2.12.6 was released on Tue Dec 06 2016 - Jackrabbit-2.13.5 was released on Wed Dec 07 2016 - Jackrabbit-2.10.5 was released on Mon Jan 16 2017 - Jackrabbit-2.12.6 was released on Tue Dec 06 2016 - Jackrabbit-2.13.5 was released on Wed Dec 07 2016 - Jackrabbit-2.13.6 was released on Wed Dec 14 2016 - Jackrabbit-2.13.7 was released on Mon Dec 19 2016 - Jackrabbit-2.14.0 was released on Tue Jan 03 2017 - Jackrabbit-2.15.0 was released on Mon Jan 09 2017 - Jackrabbit-2.4.7 was released on Mon Jan 30 2017 - Jackrabbit-2.6.8 was released on Mon Feb 06 2017 - Jackrabbit-2.8.4 was released on Mon Jan 23 2017 - Jackrabbit-2.8.5 was released on Mon Feb 20 2017 - Jackrabbit Oak-1.0.36 was released on Tue Jan 03 2017 - Jackrabbit Oak-1.0.37 was released on Mon Feb 13 2017 - Jackrabbit Oak-1.2.22 was released on Mon Dec 12 2016 - Jackrabbit Oak-1.2.23 was released on Tue Jan 10 2017 - Jackrabbit Oak-1.4.11 was released on Mon Dec 12 2016 - Jackrabbit Oak-1.4.12 was released on Tue Jan 10 2017 - Jackrabbit Oak-1.4.13 was released on Tue Feb 07 2017 - Jackrabbit Oak-1.5.15 was released on Thu Dec 08 2016 - Jackrabbit Oak-1.5.16 was released on Mon Dec 19 2016 - Jackrabbit Oak-1.5.17 was released on Wed Jan 04 2017 - Jackrabbit Oak-1.5.18 was released on Wed Jan 18 2017 - Jackrabbit Oak-1.6.0 was released on Mon Jan 23 2017 ## JIRA activity: - 715 JIRA tickets created in the last 3 months - 632 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee [Michael Dürig] ## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Jackrabbit content repository is stable, largely feature complete and actively being maintained. Jackrabbit Oak is an effort to implement a scalable and performant hierarchical content repository as a modern successor to the Apache Jackrabbit content repository. It is targeted for use as the foundation of modern world-class web sites and other demanding content applications. In contrast to its predecessor, Oak does not implement all optional features from the JSR specifications and it is not a reference implementation. ## Issues: There are no issues requiring board attention at this time. ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing moderate to high activity. Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. New features are mainly driven by dependencies from Oak. In reaction of the recent move of the JSON license to Category X the PMC removed usages of respective libraries from all versions of all products released within the Jackrabbit project. See See JCR-4068 and OAK-5171. ## Health report: The project is healthy with a continuous stream of traffic on all mailing lists reflecting the activity of the respective component / sub-project. Commit activity is moderate to high in preparation of new major release early next year. The oak-dev list is seeing a broad variety of topics being discussed. ## PMC changes: - Currently 49 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Tomek Rękawek on Mon Mar 21 2016 - On Nov. 30th the PMC offered PMC membership to Andrei Dulceanu, who subsequently accepted. Formally joining the PMC is blocked by account creation being stuck and nobody reacting to my inquiries. See https://issues.apache.org/jira/browse/INFRA-13096. ## Committer base changes: - Currently 49 committers. - No new committers added in the last 3 months - Last committer addition was Tomek Rekawek at Mon Mar 21 2016 - On Nov. 30th the PMC offered committeship to Andrei Dulceanu, who subsequently accepted. Formally joining as committer is blocked by account creation being stuck and nobody reacting to my inquiries. See https://issues.apache.org/jira/browse/INFRA-13096. ## Releases: - jackrabbit-2.12.5 was released on Mon Nov 07 2016 - jackrabbit-2.12.6 was released on Tue Dec 06 2016 - jackrabbit-2.13.4 was released on Mon Oct 10 2016 - jackrabbit-2.13.5 was released on Wed Dec 07 2016 - jackrabbit-2.4.6 was released on Mon Sep 19 2016 - jackrabbit-2.6.6 was released on Sat Sep 17 2016 - jackrabbit-2.6.7 was released on Mon Sep 26 2016 - jackrabbit-2.8.3 was released on Thu Sep 15 2016 - vault-3.1.30 was released on Thu Sep 29 2016 - oak-1.0.34 was released on Mon Oct 03 2016 - oak-1.0.35 was released on Mon Nov 14 2016 - oak-1.2.19 was released on Tue Sep 13 2016 - oak-1.2.20 was released on Wed Oct 12 2016 - oak-1.2.21 was released on Tue Nov 15 2016 - oak-1.2.22 was released on Mon Dec 12 2016 - oak-1.4.10 was released on Thu Nov 10 2016 - oak-1.4.11 was released on Mon Dec 12 2016 - oak-1.4.8 was released on Mon Oct 03 2016 - oak-1.4.9 was released on Fri Oct 21 2016 - oak-1.5.10 was released on Tue Sep 13 2016 - oak-1.5.11 was released on Fri Sep 30 2016 - oak-1.5.12 was released on Tue Oct 11 2016 - oak-1.5.13 was released on Tue Nov 08 2016 - oak-1.5.14 was released on Mon Nov 21 2016 - oak-1.5.15 was released on Thu Dec 08 2016 - oak-Segment Tar 0.0.12 was released on Mon Sep 19 2016 - oak-Segment Tar 0.0.14 was released on Mon Oct 10 2016 - oak-Segment Tar 0.0.16 was released on Mon Oct 24 2016 ## JIRA activity: - 562 JIRA tickets created in the last 3 months - 605 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee [Michael Dürig]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class web sites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications and it
is not a reference implementation.
## Issues:
We received the following question from the board in response to
our last report:
"is Oak sufficiently different to warrant its own new project?
Remember, we discourage umbrella projects. If Oak is simply a
"product" then as gs states please say so and identify it."
Oak is well within the scope of the Jackrabbit PMC. Technically it
strives for fresh solutions to the initial requirements taking into
account new challenges from the technology landscape. To that
respect it can be seen as an evolution of the initial content
repository. At some point we expect Oak to replace the previous
implementation. The exact process is yet to be defined.
The same pattern is also observed in the community: while most
activity is currently on Oak, it is largely the same set of people
also taking care of the Jackrabbit content repository. There is
currently no clear sub-community with diverging activities or
interests that would warrant splitting the project.
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the unstable development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Oak.
## Health report:
The project is healthy with a continuous stream of traffic
on all mailing lists reflecting the activity of the respective
component / sub-project.
Commit activity is moderate to high as there is substantial new
work being done in certain areas.
The oak-dev list is seeing a broad variety of topics being
discussed.
## PMC changes:
- Currently 49 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Tomek Rękawek on Mon Mar 21 2016
## Committer base changes:
- Currently 49 committers.
- No new committers added in the last 3 months
- Last committer addition was Tomasz Rekawek at Mon Mar 21 2016
## Releases:
- oak-1.0.32 was released on Mon Jul 11 2016
- oak-1.0.33 was released on Mon Aug 22 2016
- oak-1.2.16 was released on Mon Jun 13 2016
- oak-1.2.17 was released on Mon Jul 11 2016
- oak-1.2.18 was released on Wed Aug 10 2016
- oak-1.4.4 was released on Mon Jun 27 2016
- oak-1.4.5 was released on Wed Jul 13 2016
- oak-1.4.6 was released on Tue Aug 09 2016
- oak-1.5.4 was released on Wed Jun 22 2016
- oak-1.5.5 was released on Wed Jul 06 2016
- oak-1.5.6 was released on Thu Jul 21 2016
- oak-1.5.7 was released on Mon Aug 01 2016
- oak-1.5.8 was released on Mon Aug 15 2016
- oak-1.5.9 was released on Tue Aug 30 2016
- oak-Segment Tar 0.0.10 was released on Fri Aug 26 2016
- oak-Segment Tar 0.0.2 was released on Wed Jun 22 2016
- oak-Segment Tar 0.0.4 was released on Thu Jul 14 2016
- oak-Segment Tar 0.0.6 was released on Fri Jul 22 2016
- oak-Segment Tar 0.0.8 was released on Tue Aug 02 2016
- jackrabbit-2.10.4 was released on Fri Sep 09 2016
- jackrabbit-2.12.2 was released on Thu Jun 23 2016
- jackrabbit-2.12.3 was released on Tue Aug 16 2016
- jackrabbit-2.12.4 was released on Mon Sep 05 2016
- jackrabbit-2.13.0 was released on Sun Jul 10 2016
- jackrabbit-2.13.1 was released on Fri Jul 15 2016
- jackrabbit-2.13.2 was released on Thu Aug 25 2016
- jackrabbit-2.13.3 was released on Mon Sep 12 2016
- jackrabbit-2.8.2 was released on Fri Jul 15 2016
- vault-3.1.28 was released on Mon Aug 22 2016
## JIRA activity:
- 364 JIRA tickets created in the last 3 months
- 325 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Jackrabbit committee [Michael Dürig] June 2016
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
The Jackrabbit Oak sub-project is an effort to implement a
scalable and performant hierarchical content repository for use as
the foundation of modern world-class web sites and other demanding
content applications. In contrast to the initial implementation
Oak does not implement all optional features from the JSRs and
is not a reference implementation.
## Issues:
There are no issues requiring board attention at this time
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the unstable development branch are
continuously seeing high activity. This quarter saw the third
major release of Oak (1.4).
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling.
A XSS vulnerability was discoverd and fixed. See
* https://issues.apache.org/jira/browse/JCR-3950
* https://mail-search.apache.org/pmc/private-arch/jackrabbit-private/
201602.mbox/%3C56C8B688.3000703@apache.org%3E
*
## Health report:
The project is healthy with a continuous stream of traffic
on all mailing lists reflecting the activity of the respective
component / sub-project.
Commit activity is high as we just entered a new release cycle.
The oak-dev list is seeing some interesting and controversial
discussions.
## PMC changes:
- Currently 49 PMC members.
- Tomek Rękawek was added to the PMC on Mon Mar 21 2016
## Committer base changes:
- Currently 49 committers.
- Tomasz Rekawek was added as a committer on Mon Mar 21 2016
## Releases:
- oak-1.0.29 was released on Tue Mar 22 2016
- oak-1.0.30 was released on Thu Apr 21 2016
- oak-1.0.31 was released on Wed Jun 01 2016
- oak-1.2.13 was released on Wed Mar 23 2016
- oak-1.2.14 was released on Wed Apr 20 2016
- oak-1.2.15 was released on Mon May 16 2016
- oak-1.4.1 was released on Thu Mar 24 2016
- oak-1.4.2 was released on Tue May 03 2016
- oak-1.4.3 was released on Tue May 31 2016
- oak-1.5.0 was released on Tue Mar 29 2016
- oak-1.5.1 was released on Mon Apr 11 2016
- oak-1.5.2 was released on Fri May 13 2016
- jackrabbit-2.10.2 was released on Wed Mar 23 2016
- jackrabbit-2.10.3 was released on Mon May 09 2016
## JIRA activity:
- 376 JIRA tickets created in the last 3 months
- 301 JIRA tickets closed/resolved in the last 3 months
## Description: The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). ## Issues: There are no issues requiring board attention at this time ## Activity: Apache Jackrabbit Oak receives most attention nowadays. All maintenance branches and the unstable development branch are continuously seeing high activity. The PMC is currently in the process of voting on the next major release (1.4). Apache Jackrabbit itself is mostly in maintenance mode with most of the work going into bug fixing and tooling. ## PMC changes: - Currently 48 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Vikas Saurabh on Fri Nov 06 2015 ## Committer base changes: - Currently 48 committers. - No new committers added in the last 3 months - Last committer addition was Vikas Saurabh at Wed Nov 04 2015 ## Releases: - Jackrabbit-2.12.0 was released on Tue Feb 09 2016 - Jackrabbit-2.12.1 was released on Fri Feb 26 2016 - Oak-1.0.26 was released on Tue Jan 19 2016 - Oak-1.0.27 was released on Tue Feb 09 2016 - Oak-1.0.28 was released on Wed Mar 02 2016 - Oak-1.2.10 was released on Wed Jan 20 2016 - Oak-1.2.11 was released on Wed Feb 10 2016 - Oak-1.2.12 was released on Wed Mar 02 2016 - Oak-1.3.13 was released on Mon Jan 04 2016 - Oak-1.3.14 was released on Mon Jan 18 2016 - Oak-1.3.15 was released on Wed Feb 03 2016 - Oak-1.3.16 was released on Tue Feb 16 2016 - Oak-1.4 was released on Wed Mar 02 2016 - Vault-3.1.26 was released on Sat Jan 09 2016 ## JIRA activity: - 374 JIRA tickets created in the last 3 months - 369 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
## Activity:
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling.
Apache Jackrabbit Oak receives most attention nowadays. Both the
1.0 and 1.2 maintenance branches and the 1.3 unstable branch are
continuously seeing high activity.
In September .adaptTo() Berlin 2015 featured a session on
Jackrabbit Oak.
## Issues:
There are no issues requiring board attention at this time
## PMC changes:
- Currently 48 PMC members.
- Vikas Saurabh was added to the PMC on Fri Nov 06 2015
## Committer base changes:
- Currently 48 committers.
- Vikas Saurabh was added as a committer on Wed Nov 04 2015
## Releases:
- Oak-1.0.21 was released on Thu Sep 17 2015
- Oak-1.0.22 was released on Sat Oct 03 2015
- Oak-1.0.23 was released on Wed Oct 28 2015
- Oak-1.0.24 was released on Mon Nov 16 2015
- Oak-1.2.6 was released on Thu Sep 17 2015
- Oak-1.2.7 was released on Mon Oct 05 2015
- Oak-1.2.8 was released on Mon Nov 16 2015
- Oak-1.3.6 was released on Mon Sep 14 2015
- Oak-1.3.7 was released on Thu Oct 01 2015
- Oak-1.3.8 was released on Mon Oct 12 2015
- Oak-1.3.9 was released on Mon Oct 26 2015
- Oak-1.3.10 was released on Mon Nov 09 2015
- Oak-1.3.11 was released on Mon Nov 23 2015
- Jackrabbit-2.11.1 was released on Fri Oct 02 2015
- Jackrabbit-2.11.2 was released on Sun Oct 25 2015
- Jackrabbit-2.11.3 was released on Thu Dec 03 2015
- Jackrabbit-vault-3.1.24 was released on Mon Sep 28 2015
## Mailing list activity:
- users@jackrabbit.apache.org:
- 617 subscribers (down -3 in the last 3 months):
- 128 emails sent to list (83 in previous quarter)
- dev@jackrabbit.apache.org:
- 344 subscribers (up 2 in the last 3 months):
- 370 emails sent to list (296 in previous quarter)
- oak-commits@jackrabbit.apache.org:
- 32 subscribers (up 0 in the last 3 months):
- 952 emails sent to list (978 in previous quarter)
- oakcommits@jackrabbit.apache.org:
- 5 subscribers (up 0 in the last 3 months)
- oak-issues@jackrabbit.apache.org:
- 29 subscribers (up 0 in the last 3 months):
- 3797 emails sent to list (4212 in previous quarter)
- announce@jackrabbit.apache.org:
- 248 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (2 in previous quarter)
- oak-dev@jackrabbit.apache.org:
- 195 subscribers (up 4 in the last 3 months):
- 728 emails sent to list (856 in previous quarter)
## JIRA activity:
- 411 JIRA tickets created in the last 3 months
- 378 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
## Activity:
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling.
Apache Jackrabbit Oak receives most attention nowadays. Both the
1.0 and 1.2 maintenance branches and the 1.3 unstable branch are
continuously seeing high activity.
.adaptTo() Berlin 2015 will be featuring a session on Jackrabbit
Oak in September.
## Issues:
There are no issues requiring board attention at this time
## LDAP committee group/Committership changes:
- Currently 47 committers and 47 LDAP committee group members.
- New LDAP committee group members:
- Stefan Egli was added to the LDAP committee group on Mon Jul 20 2015
- Dominique Jäggi was added to the LDAP committee group on Thu Jul 30 2015
- Francesco Mari was added to the LDAP committee group on Fri Aug 28 2015
- Julian Sedding was added to the LDAP committee group on Fri Aug 28 2015
- New commmitters:
- Dominique Jäggi was added as a committer on Wed Jul 29 2015
- Julian Sedding was added as a committer on Fri Aug 28 2015
- Stefan Egli was added as a committer on Mon Jul 20 2015
- Francesco Mari was added as a committer on Thu Aug 27 2015
## Releases:
- oak 1.0.17 was released on Sun Jul 12 2015
- oak 1.3.0 was released on Mon Jun 15 2015
- oak 1.3.1 was released on Thu Jun 25 2015
- oak 1.3.2 was released on Mon Jul 06 2015
- oak 1.3.4 was released on Fri Aug 21 2015
- 2.11.0 was released on Wed Aug 12 2015
- oak 1.0.18 was released on Sun Aug 02 2015
- oak 1.0.16 was released on Mon Jun 29 2015
## Mailing list activity:
- users@jackrabbit.apache.org:
- 621 subscribers (down -9 in the last 3 months):
- 83 emails sent to list (82 in previous quarter)
- dev@jackrabbit.apache.org:
- 343 subscribers (down -4 in the last 3 months):
- 300 emails sent to list (411 in previous quarter)
- oak-commits@jackrabbit.apache.org:
- 32 subscribers (down -1 in the last 3 months):
- 1931 emails sent to list (1537 in previous quarter)
- oakcommits@jackrabbit.apache.org:
- 5 subscribers (up 0 in the last 3 months)
- oak-issues@jackrabbit.apache.org:
- 29 subscribers (up 1 in the last 3 months):
- 4246 emails sent to list (3440 in previous quarter)
- announce@jackrabbit.apache.org:
- 249 subscribers (up 3 in the last 3 months):
- 2 emails sent to list (8 in previous quarter)
- oak-dev@jackrabbit.apache.org:
- 189 subscribers (down -4 in the last 3 months):
- 761 emails sent to list (747 in previous quarter)
## JIRA activity:
- 413 JIRA tickets created in the last 3 months
- 375 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
## Activity:
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling.
Apache Jackrabbit Filevault is seeing moderate activity with regular
releases containing mostly bug fixes and sporadically new features.
Apache Jackrabbit Oak receives most attention nowadays. Both the
1.0 and 1.2 maintenance branches and the 1.3 unstable branch are
continuously seeing high activity.
A vulnerability has been reported to the Jackrabbit PMC on May 6th
by an external party. The issue was immediately addressed by the PMC
and fixes along with disclosure of the issue were released on May 21st.
See https://mail-search.apache.org/members/private-arch/security/
201505.mbox/%3C555DA644.8080908@greenbytes.de%3E
## Issues:
The Apache Jackrabbit project is in good shape. We have no board-level
issues at this time.
## PMC/Committership changes:
- Currently 43 committers and 43 PMC members in the project.
- Shashank was added to the PMC on Thu Mar 26 2015
- Shashank was added as a committer on Wed Mar 25 2015
## Releases:
- 2.8.1 was released on Thu Jun 04 2015
- oak 1.0.14 was released on Mon May 18 2015
- oak 1.0.13 was released on Mon Apr 20 2015
- 2.10.1 was released on Thu May 21 2015
- 2.10.0 was released on Thu Mar 26 2015
- oak 1.2.0 was released on Mon Apr 13 2015
- oak 1.2.2 was released on Mon May 04 2015
## Mailing list activity:
- users@jackrabbit.apache.org:
- 630 subscribers (down -9 in the last 3 months):
- 83 emails sent to list (83 in previous quarter)
- dev@jackrabbit.apache.org:
- 346 subscribers (down -3 in the last 3 months):
- 410 emails sent to list (214 in previous quarter)
- oak-commits@jackrabbit.apache.org:
- 33 subscribers (down -4 in the last 3 months):
- 1577 emails sent to list (1348 in previous quarter)
- oakcommits@jackrabbit.apache.org:
- 5 subscribers (up 0 in the last 3 months)
- oak-issues@jackrabbit.apache.org:
- 28 subscribers (up 2 in the last 3 months):
- 3583 emails sent to list (1887 in previous quarter)
- announce@jackrabbit.apache.org:
- 248 subscribers (down -6 in the last 3 months):
- 8 emails sent to list (6 in previous quarter)
- oak-dev@jackrabbit.apache.org:
- 192 subscribers (down -2 in the last 3 months):
- 757 emails sent to list (412 in previous quarter)
## JIRA activity:
- 404 JIRA tickets created in the last 3 months
- 336 JIRA tickets closed/resolved in the last 3 months
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
## Activity:
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling.
Apache Jackrabbit Filevault is seeing moderate activity with regular
releases containing mostly bug fixes and sporadically new features.
Apache Jackrabbit Oak receives most attention nowadays. Both the
1.0 maintenance branch an the 1.1 unstable branch - leading up to
the next stable release 1.2 - are continuously seeing high activity.
## Issues:
The Apache Jackrabbit project is in good shape. We have no board-level
issues at this time.
## PMC/Committership changes:
- Currently 42 committers and 42 PMC members in the project.
- No new PMC members added in the last 3 months
- No new committers added in the last 3 months
- Last PMC addition was Amit Jain at Tue Aug 26 2014
- Last committer addition was Amit Jain at Tue Aug 26 2014
## Releases:
- 1.0.9 was released on Mon Dec 22 2014
- 1.0.11 was released on Tue Feb 03 2015
- 1.1.5 was released on Fri Jan 23 2015
- 2.9.1 was released on Fri Feb 06 2015
- 1.1.3 was released on Fri Dec 12 2014
- 1.1.4 was released on Tue Jan 13 2015
- 1.1.6 was released on Mon Feb 09 2015
- 3.1.16 was released on Mon Feb 23 2015
- 3.1.14 was released on Fri Dec 19 2014
- 1.0.10 was released on Mon Feb 02 2015
## Mailing list activity:
- users@jackrabbit.apache.org: 639 subscribers (down -4 in the last 3 months):
85 emails sent to list (70 in previous quarter)
- dev@jackrabbit.apache.org: 349 subscribers (down -4 in the last 3 months):
232 emails sent to list (340 in previous quarter)
- oak-commits@jackrabbit.apache.org: 38 subscribers (down -1 in the last 3
months):
1334 emails sent to list (1301 in previous quarter)
- oak-issues@jackrabbit.apache.org: 26 subscribers (down -2 in the last 3
months):
1861 emails sent to list (2092 in previous quarter)
- announce@jackrabbit.apache.org: 254 subscribers (down -2 in the last 3
months):
6 emails sent to list (3 in previous quarter)
- oak-dev@jackrabbit.apache.org: 196 subscribers (up 12 in the last 3 months):
416 emails sent to list (578 in previous quarter)
## JIRA activity:
- 284 JIRA tickets created in the last 3 months
- 269 JIRA tickets closed/resolved in the last 3 months
@Brett: clarify report regarding email activity for oak-dev and oak-commits
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following maintenance releases from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 1.0.6 on September 25th * Apache Jackrabbit Oak 1.0.7 on October 14th * Apache Jackrabbit Oak 1.0.8 on November 4th We made the following unstable release from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 1.1.0 on October 6th * Apache Jackrabbit Oak 1.1.1 on October 13th * Apache Jackrabbit Oak 1.1.2 on November 10th We made the following release from the Jackrabbit FileVault sub project: * Apache Jackrabbit FileVault 3.1.8 on October 27th o Community / Development * No new committers or PMC members joined the Jackrabbit team since June 2014. * .adaptTo() Berlin in September and ApacheCon EU Budapest in November featured sessions on Jackrabbit Oak.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following unstable release from Jackrabbit trunk: * Apache Jackrabbit 2.9 on August 28th We made the following maintenance releases from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 1.0.2 on July 14th * Apache Jackrabbit Oak 1.0.3 on July 28th * Apache Jackrabbit Oak 1.0.4 on August 4th * Apache Jackrabbit Oak 1.0.5 on August 29th o Community / Development * Amit Jain joined the Jackrabbit team as committer and PMC member in June. * .adaptTo() Berlin 2014 will be featuring a session on Jackrabbit Oak in September.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following stable release from Jackrabbit trunk: * Apache Jackrabbit 2.8 on May 12th We made the following unstable release from Jackrabbit trunk: * Apache Jackrabbit 2.7.5 on March 17th We made the following releases from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 0.19 on March 24th * Apache Jackrabbit Oak 0.20 on April 8th * Apache Jackrabbit Oak 1.0 on May 20th * Apache Jackrabbit Oak 1.0.1 on June 26th We made the following release from the Jackrabbit FileVault sub project: * Apache Jackrabbit FileVault 3.1 on March 31st * Apache Jackrabbit FileVault 3.1.2 on April 5th * Apache Jackrabbit FileVault 3.1.6 on April 22nd o Community / Development * Apache Jackrabbit Oak has finally hit the stage with its first major release in May. Apache Jackrabbit Oak is a new JCR implementation with a completely new architecture. Based on concepts like eventual consistency and multi-version concurrency control, and borrowing ideas from distributed version control systems and cloud-scale databases, the Oak architecture is a major leap ahead for Apache Jackrabbit. * Davide Gianella joined the Jackrabbit team as committer and PMC member in June. * Various sessions about Jackrabbit and Oak have been submitted / accepted to international conferences like ApacheCon, ApacheConEU, .adaptTo(Berlin).
No report was submitted.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following stable release from Jackrabbit trunk: * Apache Jackrabbit 2.6.5 on December 13th We made the following unstable release from Jackrabbit trunk: * Apache Jackrabbit 2.7.4 on February 11th We made the following releases from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 0.13 on December 13th * Apache Jackrabbit Oak 0.14 on January 13th * Apache Jackrabbit Oak 0.15 on January 27th * Apache Jackrabbit Oak 0.16 on February 10th * Apache Jackrabbit Oak 0.17.1 on February 26th * Apache Jackrabbit Oak 0.18 on March 11th o Community / Development * No new committers or PMC members joined the Jackrabbit team since February 2013.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following stable release from Jackrabbit trunk: * Apache Jackrabbit 2.6.4 on October 11th We made the following unstable release from Jackrabbit trunk: * Apache Jackrabbit 2.7.1 on September 16th * Apache Jackrabbit 2.7.2 on November 8th * Apache Jackrabbit 2.7.3 on December 9th The following patch releases were made from earlier maintenance branches: * Apache Jackrabbit 2.4.5 on October 11th We made the following releases from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 0.9 on September 20th * Apache Jackrabbit Oak 0.10 on October 9th * Apache Jackrabbit Oak 0.11 on November 21st * Apache Jackrabbit Oak 0.12 on November 28th We made the following release from the Jackrabbit FileVault sub project: * Apache Jackrabbit FileVault 3.0 on October 1st o Community / Development * The Jackrabbit project received a donation of Adobe's FileVault. The process was tracked under JCR-3612. IP clearance passed August 10th [1] and subsequently lead to a first release as listed above. * No new committers or PMC members joined the Jackrabbit team since February 2013. [1] http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/201308.mbox/%3CCAB+dfiknHR3gpNzeee3K867jcC1E5Z7XZt3m0d2fqfbuExiByQ@mail.gmail.com%3E
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following stable release from the 2.6 branch: * Apache Jackrabbit 2.6.3 on August 1st o Community / Development No new committers or PMC members joined the Jackrabbit team since February 2013.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following stable release from Jackrabbit trunk: * Apache Jackrabbit 2.6.1 on May 13th * Apache Jackrabbit 2.6.2 on May 29th We made the following unstable release from Jackrabbit trunk: * Apache Jackrabbit 2.7.0 on May 13th The following patch releases were made from earlier maintenance branches: * Apache Jackrabbit 2.4.4 on May 13th We made a release from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 0.7 on May 20th * Apache Jackrabbit Oak 0.8 on May 27th o Community / Development No new committers or PMC members joined the Jackrabbit team since February 2013. o Infrastructure Jackrabbit web site migration is done. To make updating easier we will probably migrate most of the site's content to the Wiki and go with a simpler main page that points to all relevant resources.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following stable release from Jackrabbit trunk: * Apache Jackrabbit 2.6 on February 14th We made the following unstable 2.5.x release from Jackrabbit trunk: * Apache Jackrabbit 2.5.3 on January 13th We made a release from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 0.6 on January 28th o Community / Development * Manfred Baedke, Tommaso Teofili and Cédric Damioli joined the Jackrabbit team as committers and PMC members. o Infrastructure Jackrabbit web site migration is pending for infra, see https://issues.apache.org/jira/browse/INFRA-5919
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following unstable 2.5.x release from Jackrabbit trunk: * Apache Jackrabbit 2.5.2 on September 23rd We made a release from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 0.5 on September 30th o Community / Development * Chetan Mehrotra and Mete Atamel joined the Jackrabbit team as committers and PMC members. * Work on Jackrabbit Oak continues strong: At .adaptTo(Berlin) 2012 there was a presentation on Oak and an Oak related hackathon both of which where well attended. A further Hackathon was held at ApacheCon EU. * There was a discussion on the future of Jackrabbit and Jackrabbit Oak on the dev@ list. The emerging consensus seems to be that Oak will be kept in Jackrabbit and might eventually become Jackrabbit 3.0 (See http://markmail.org/message/ga4mn2x2xqsvzwg6). o Infrastructure We are still in progress of migrating from Confluence to the new CMS.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following unstable 2.5.x releases from Jackrabbit trunk: * Apache Jackrabbit 2.5.1 on August 6th The following patch releases were made from earlier maintenance branches: * Apache Jackrabbit 2.4.3 on September 3rd This quarter also saw the first releases of the OCM code base in a while: * Apache Jackrabbit OCM 2.0 on July 10th Finally we made two releases from the Jackrabbit Oak sub project: * Apache Jackrabbit Oak 0.4 on August 13th * Apache Jackrabbit Oak 0.3 on July 5th o Community / Development * Randall Hauch joined the Jackrabbit team as committer and PMC member. * Work on Jackrabbit Oak is still going strong: there where again two Hackathons in the last quarter during which great progress was made and which lead to the release of Oak 0.3. and 0.4. Another Hackathon will take place in September co-located with the .adaptTo(Berlin) 2012 conference (http://adaptto.mixxt.de/networks/events/show_event.65841). Being part of .adaptTo() allows us to further broaden the community and spark more interest in Apache Jackrabbit Oak. * Jukka Zitting and Michael Dürig submitted a talk about Oak for .adaptTo(Berlin) 2012 (http://adaptto.mixxt.de/). * Jukka Zitting and Michael Dürig submitted a talk about Oak for ApacheCon Europe 2012. o Infrastructure We are still in progress of migrating from Confluence to the new CMS.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following unstable 2.5.x releases from Jackrabbit trunk. * Apache Jackrabbit 2.5.0 on June 2nd The following patch releases were made from earlier maintenance branches: * Apache Jackrabbit 2.2.12 on April 23rd * Apache Jackrabbit 2.4.1 on April 3rd * Apache Jackrabbit 2.4.2 on June 11th This quarter also saw the first releases from the Jackrabbit Oak subproject: * Apache Jackrabbit Oak 0.2.1 on May 7th * Apache Jackrabbit Oak 0.1 on April 3rd Note, there is no Oak 0.2 release since the release vote failed due to a license header issue. The issue was quickly resolved and the release re-cut into 0.2.1 o Community / Development * Unico Hommes and Christian Stocker joined the Jackrabbit team as committers and PMC members. * Work on Jackrabbit Oak is gaining momentum: there where two Hackathons in the last quarter during which great progress was made. This eventually lead to the releases 0.1. and 0.2.1 as initially planned. Currently we are discussing whether, how and what we want to contribute to the .adaptTo(Berlin) 2012 conference in September. .adaptTo(Berlin) is a technical meet up focused on the technical stack of Apache Sling including Apache Jackrabbit and Apache Felix and is addressed to all developers using this stack or parts of it. Being part of that event would allow us to broaden the community and further spark interest for Apache Jackrabbit Oak. * Alex Parvulescu has successfully taken up the role of a release manager. * There is renewed interest on the OCM codebase, driven by Ard Schrijvers. We expect to be able to cut a new, long overdue OCM release in near future. * ModeShape, a JCR implementation from JBoss, is working with us to improve the JCR test suite. To better facilitate this cooperation we may want to split the test suite away from the main Jackrabbit release schedule. * Jukka Zitting resigned as chairman of the Jackrabbit PMC due to his new role at the Incubator. Michael Dürig was elected and acknowledged as new chairman. o Infrastructure We are still in progress of migrating from Confluence to the new CMS.
WHEREAS, the Board of Directors heretofore appointed Jukka Zitting to the office of Vice President, Apache Jackrabbit, and WHEREAS, the Board of Directors is in receipt of the resignation of Jukka Zitting from the office of Vice President, Apache Jackrabbit, and WHEREAS, the Project Management Committee of the Apache Jackrabbit project has chosen by vote to recommend Michael Dürig as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jukka Zitting is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Jackrabbit, and BE IT FURTHER RESOLVED, that Michael Dürig be and hereby is appointed to the office of Vice President, Apache Jackrabbit, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Jackrabbit Project Chair, was approved by Unanimous Vote of the directors present.
The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases The biggest news this quarter was the first stable Jackrabbit 2.4 release, about a year after Jackrabbit 2.2 was branched. * Apache Jackrabbit 2.4.0 on February 9th In the run-up to 2.4, we cut the following unstable 2.3.x releases: * Apache Jackrabbit 2.3.7 on January 24th * Apache Jackrabbit 2.3.6 on January 2nd * Apache Jackrabbit 2.3.5 on December 16th We made one patch release from the earlier 2.2 maintenance branch: * Apache Jackrabbit 2.2.11 on February 11th We also completed the end-of-life period of the last Jackrabbit 1.x maintenance branch, making the stable 2.x branches the only actively maintained versions of Jackrabbit. o Community / Development No new committers or PMC members were added in this quarter. The work towards Jackrabbit 3 entered a major new phase as we decided to promote the effort from prototypes in the Jackrabbit sandbox to a new Jackrabbit subproject codenamed "Oak". This is a major rewrite of Jackrabbit, which is why we wanted to clearly separate the effort from work on the main Jackrabbit codebase. It is yet undecided whether the Oak codebase will eventually replace Jackrabbit trunk to become Jackrabbit 3.0 or if we want to rebrand the effort and branch it off to a separate TLP, possibly through the Incubator. Meanwhile we plan to start publishing early access versions of the Oak codebase as a series of monthly "Apache Jackrabbit Oak 0.x" releases (as the codename "Oak" is not unique enough for use as a standalone "Apache Oak" brand). Jukka Zitting wishes to resign as chairman of the Jackrabbit PMC due to his new role at the Incubator, so we have started the process of electing a new chairman. o Infrastructure We are still in progress of migrating from Confluence to the new CMS.
The Apache Jackrabbit content repository is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following unstable 2.3.x releases from Jackrabbit trunk. * Apache Jackrabbit 2.3.4 on November 29th * Apache Jackrabbit 2.3.3 on November 15th * Apache Jackrabbit 2.3.2 on November 2nd * Apache Jackrabbit 2.3.0 on October 3rd The following patch releases were made from earlier maintenance branches: * Apache Jackrabbit 2.2.10 on November 22nd * Apache Jackrabbit 2.2.9 on October 3rd * Apache Jackrabbit 2.1.6 on October 3rd * Apache Jackrabbit 2.0.5 on October 3rd * Apache Jackrabbit 1.6.5 on October 3rd o Community / Development Bart van der Schans and Justin Edelson joined the Jackrabbit team as committers and PMC members. We adopted an even/odd versioning scheme for stable/unstable releases and started cutting unstable 2.3.x releases directly from trunk. A stable 2.4.0 release and the accompanying stable 2.4 maintenance branch is planned for January 2012. The end of life of Jackrabbit 1.x was announced, with 1.6.5 being the last 1.x release we plan to make. Active work on the new microkernel prototype targeting Jackrabbit 3.0 continues. o Infrastructure We started working on migrating from Confluence to the new CMS.
The Apache Jackrabbit content repository is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made one Jackrabbit 2.2.x patch release in this quarter: * Apache Jackrabbit 2.2.8 on August 23rd o Legal / Branding No open issues. o Community / Development No new committers or PMC members were added since our last report. Apache Jackrabbit was nominated for the 2011 Swiss Open Source Award in the community category. We attended the award ceremony on Tuesday, Sep 13th, and gave a short presentation about Jackrabbit, but the award went to another project. We are planning to cut the Jackrabbit 2.3.0 release from trunk in near future. To increase the rate at which latest work in the trunk gets released (it is already nine months since Jackrabbit 2.2), we are considering an odd/even versioning strategy where all odd releases like 2.3.x are cut directly from trunk, and even-numbered stable maintenance branches like 2.4 get created every now and then for production-ready releases. Meanwhile we will be cutting new patch releases from earlier maintenance branches, including the old 1.6 branch whose end of life status will be announced along with the last patch release. Also, active work on the new microkernel prototype targeting Jackrabbit 3.0 continues. o Infrastructure The planned migration from Confluence to the new CMS soon is still pending for action on our part.
Congratulations on being nominated for the 2011 Swiss Open Source award. Both Jackrabbit project and Clerezza podling were nominated.
The Apache Jackrabbit(TM) content repository is a fully conforming implementation of the Content Repository for Java(TM) Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made three Jackrabbit 2.1.x and 2.2.x patch releases in this quarter: * Apache Jackrabbit 2.2.7 on June 7th * Apache Jackrabbit 2.1.5 on June 7th * Apache Jackrabbit 2.2.5 on March 18th o Legal / Branding No open issues. o Community / Development Dave Brosius and Alex Parvulescu joined the Jackrabbit project as committers and PMC members. A new Jackrabbit 3 prototype has been started based on the proposed microkernel concept. o Infrastructure We will be migrating our web site from Confluence to the new CMS soon.
Apache Jackrabbit(TM) is a fully conforming implementation of the Content Repository for Java(TM) Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made three Jackrabbit 2.2.x patch releases in this quarter: * Apache Jackrabbit 2.2.4 on February 15th * Apache Jackrabbit 2.2.2 on January 26th * Apache Jackrabbit 2.2.1 on January 11th o Legal / Branding No open issues. o Community / Development Our efforts to better identify key contributors and offer them committership are starting to bear fruit. In this quarter Berry van Halderen and Thomas Draier joined us as committers and PMC members, and we are expecting to welcome more members soon. We are happy to see Apache Chemistry reach TLP status, and contributed a supporting quote to the press release about their graduation. o Infrastructure We have consensus on moving our web site from Confluence to the new CMS, but have yet to start the migration.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases The biggest news this quarter is the release of Jackrabbit 2.2: * Apache Jackrabbit 2.2.0 on December 14th We also made a number of smaller patch releases: * Apache Jackrabbit 2.1.3 on December 7th * Apache Jackrabbit 2.1.2 on October 31st * Apache Jackrabbit 2.0.3 on October 31st * Apache Jackrabbit 1.6.4 on October 12th o Legal / Branding We have updated our project branding to match the new branding guidelines except for a few details that still need to be discussed on trademarks@. o Community / Development No new committers were added in this quarter, but a few old committers have become active again and we're seeing good levels of activity from other contributors. Day Software, the employer of many Jackrabbit committers, was recently acquired by Adobe. We expect this acquisition to have little impact on their contributions to Jackrabbit. o Infrastructure We are currently using a Confluence wiki for managing our project web site, but would like to migrate to an alternative system. The most promising alternatives are the new CMS or an svnpubsub-based site built with Maven.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We released one Jackrabbit 2.1 patch release in August: * Apache Jackrabbit 2.1.1 on August 11th o Legal We are aware of the new branding guidelines, but have yet to review our web site and other documentation for compliance. o Community / Development No new committers were added in this quarter. There's been some interest on the user list about people getting more involved in maintaining some less active parts of our codebase. We're trying to encourage and mentor such efforts. As usual, we saw a temporary dip in mailing list and development activity during the summer, but we're already back to normal. The Jackrabbit trunk has seen quite a few improvements especially in access control, thread-safety and performance, and we plan to ship these improvements in a Jackrabbit 2.2 release in near future. We received a vulnerability report through security@apache.org, but the problem turned out to be a normal bug with no security implications. o Infrastructure The new Hudson master seems to be working better than the previous one.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Jackrabbit 2.1 was released in April: * Apache Jackrabbit 2.1.0 on April 22nd We also made maintenance releases from the 1.6 and 1.4 branches: * Apache Jackrabbit 1.6.2 on June 7th * jackrabbit-core 1.4.12 on June 7th o Legal The question in LEGAL-50 about redistribution of the standard JCR API jar has now been officially resolved. Thanks to the legal team for the closure on this! With LEGAL-50 resolved, we have no open legal issues. We use RAT for automatic license header checks as a part of our normal Hudson CI builds, and the accuracy of our LICENSE and NOTICE files is manually reviewed before each release. o Community / Development No new committers were added in this quarter. This is our third consecutive quarter with no new committers. It looks like we need to pay more attention to helping out and mentoring contributors. We have traditionally maintained relatively high entry criteria for new committers. Community diversity remains an issue we pay attention to, as the bulk of Jackrabbit development is still done by one company. In this quarter we've had eight people committing to Jackrabbit trunk, six of whom are employees of Day Software. We satisfy the criteria of at least three independent active committers and the community is healthy. Thus I don't see diversity as an immediate problem for Jackrabbit, but it's a topic we are aware of especially in light of the few new committers we've recently attracted. o Infrastructure The Confluence upgrade caused some breakage on our web site and required manual fixing. We are not too happy with our current Confluence auto-export setup, and are considering other options. Some of our Hudson builds have been failing due to generic Hudson problems. We're hoping that the new master server will solve these issues. We're also looking forward to a chance to set up a Sonar instance for Apache projects.
Doug to initiate a discussion as to what items the board should periodically request be included in reports (example: diversity) to the mailing list.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Jackrabbit 2.0 was released in January after all the main issues in previous beta releases had been fixed: * Apache Jackrabbit 2.0 beta5 on January 11th * Apache Jackrabbit 2.0 beta6 on January 18th * Apache Jackrabbit 2.0.0 on January 27th We also made one maintenance release from the 1.6 branch: * Apache Jackrabbit 1.6.1 on January 21st o Legal We have updated our NOTICE files as discussed in LEGAL-62 and LEGAL-59. o Community / Development No new committers were added in this quarter. With Jackrabbit 2.0 out, we've started discussing about what we want to achieve in Jackrabbit 3, our next major release. These design discussions have been pretty lively and it's good to see many voices from outside the core development team participating in the email threads. The first bits of related prototype code have already hit our sandbox area in svn. o Infrastructure No open issues.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Jackrabbit 2.0 reached beta status with the following releases: * Apache Jackrabbit 2.0 alpha11 on September 23rd * Apache Jackrabbit 2.0 beta1 on October 30th * Apache Jackrabbit 2.0 beta3 on November 25th * Apache Jackrabbit 2.0 beta4 on December 12th We also made two releases from the old 1.4 maintenance branch: * jackrabbit-core 1.4.10 on September 15th * jackrabbit-core 1.4.11 on September 23rd We made two releases of the Jackrabbit parent POM: * org.apache.jackrabbit:jackrabbit:4 on September 14th * org.apache.jackrabbit:jackrabbit:5 on October 4th o Legal We're tracking the LEGAL-50 and LEGAL-62 issues for further comments, but currently we have no open legal action items. We are interested in figuring out how the new trademark policy affects our logo, website and releases, and what steps we need to take to meet the policy. o Community / Development Jackrabbit participated in the Content Technology track and the NoSQL meetup at ApacheCon US 2009. The development branch related to database connection pooling has been merged back to Jackrabbit trunk and the results are included in the Jackrabbit 2.0 beta4 release. We've discussed with Apache Sling about taking over some OSGi bundling code they've written for Jackrabbit. On the other hand there is some code in Jackrabbit that's only being used by Sling and that might end up being adopted by them. We're considering making parts of our svn tree writable by members of both projects to simplify such cooperation. o Infrastructure We received some spam through Nabble on our dev@ list, and have asked Nabble to disable posts through the web interface. We reconfigured the Jackrabbit entry on Ohloh to get code statistics from the Git mirror at git.apache.org since the svn history seen by Ohloh didn't include the time when Jackrabbit was still incubating.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases The big news this quarter is the release of Jackrabbit 1.6.0: * Apache Jackrabbit 1.6.0 on August 11th The following patch releases were made from earlier maintenance branches: * Apache Jackrabbit 1.5.7 on August 3rd * jackrabbit-core 1.4.10 on September 15th We made two internal releases of the Jackrabbit parent POM: * org.apache.jackrabbit:parent:3 on June 26th * org.apache.jackrabbit:parent:4 on September 15th We also continued releasing Jackrabbit 2.0 alphas: * Apache Jackrabbit 2.0 alpha3 on July 3rd * Apache Jackrabbit 2.0 alpha4 on July 14th * Apache Jackrabbit 2.0 alpha7 on August 10th * Apache Jackrabbit 2.0 alpha8 on August 18th * Apache Jackrabbit 2.0 alpha9 on August 26th o Legal We have asked (see LEGAL-50) the legal team to review the terms under which we are redistributing the JCR API jar. The purpose of this is to complete the legal records, and this issue is not a blocker to our current releases. Recent legal discussions regarding the contents of the NOTICE files (see for example LEGAL-62) suggest that we have been including some unnecessary information in our NOTICEs. We will review our NOTICE files before the 2.0 release to comply with the consensus on legal-discuss@. o Community / Development Sébastien Launay joined the Jackrabbit team as a committer and PMC member. With the 1.6 release our JCR 1.0 work has entered maintenance mode and we're focusing on releasing Jackrabbit 2.0 shortly after JCR 2.0 becomes available. We reached JCR 2.0 feature-completeness with the 2.0 alpha9 release, and that release was also used for the JCR 2.0 RI and TCK candidates. The JSR 283 final approval ballot has just passed, and we expect the final JCR 2.0 release to follow soon. The main author of the JCROM project that implements an alternative to the Jackrabbit OCM (object content mapping) component contacted us about bringing the JCROM code to Jackrabbit and possibly merging with our existing OCM code. o Infrastructure We are now using the Nexus server at repository.apache.org for staging and deploying our releases to the central Maven repository. The monthly Google Analytics reports we set up earlier this year don't seem to be reaching the dev@ list anymore. To work around this we're now sharing the reports via svn and our web site.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following releases from the 1.5 branch: * Apache Jackrabbit 1.5.4 on April 7th * Apache Jackrabbit 1.5.5 on April 28th * Apache Jackrabbit 1.5.6 on June 4th We also made the first alpha release of the upcoming Jackrabbit 2.0: * Apache Jackrabbit 2.0 alpha1 on June 4th o Legal The current Jackrabbit trunk and the 2.0 alpha1 release have a system dependency to an early "for review only" version of the JCR 2.0 API jar from JSR 283. No major concerns were raised when this case was discussed on the legal-discuss@ mailing list. o Community / Development Jackrabbit was present at the ApacheCon EU where we also organized a quite successful JCR meetup. The CMIS effort that started in the Jackrabbit sandbox has now become the Apache Chemistry project in the Incubator. The other podling with Jackrabbit as the sponsoring PMC, Apache Sling, is just about to graduate into a standalone TLP. The JCR 2.0 specification (JSR 283) is expected to become final in a few months, as soon as we've completed the required RI and TCK work in Jackrabbit trunk. We're producing source-only alpha releases of the 2.0 codebase to give people a chance to review all the new features and to better track our progress. We are also planning to release Jackrabbit 1.6 as the last minor release from the 1.x branch that's still based on the JCR 1.0 API. o Infrastructure We are about to start using the Nexus installation at repository.apache.org for staging and deploying our releases to the Maven repository.
Again: any noteworthy regarding the release that the PRC can help with? Jukka to pursue.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following two releases from the 1.5 branch: * Apache Jackrabbit 1.5.2 on January 20th * Apache Jackrabbit 1.5.3 on February 27th The 1.5.2 release contained a fix to the security issue CVE-2009-0026 (Cross site scripting issues in webapp). This was the first security issue we had received through security@, and we had some initial confusion on how we should react to such issues. The security team was very helpful in guiding us. We also made the following component releases from the older 1.4 branch: * jackrabbit-core 1.4.7 on January 20th * jackrabbit-core 1.4.8 on January 29th * jackrabbit-core 1.4.9 on March 3rd To get the JCR Commons subproject started we created and released a standalone Jackrabbit parent POM: * org.apache.jackrabbit:parent:2 on February 6th o Legal No issues at the moment. o Community / Development Michael Duerig joined the Jackrabbit team as a committer and PMC member. The JCR Commons subproject was started after related discussion and a vote. We are still in the process of setting up this new subproject. To respond to earlier feedback from the board: we decided *not* to move these components to Apache Commons to avoid splitting the development community. There is continuous interest in the JCR-based CMIS implementation we are developing in our sandbox. Florent Guillaume, who is not (yet) an Apache committer, is working on a related codebase in an external Mercurial repository under the working name "Chemistry". There are concerns over the development being split over different source repositories. For now we hope to bring all development into Apache svn and plan to manage the effort as organic growth within the Jackrabbit project, possibly targetting a subproject once the effort matures. Another option is to push the effort to the Incubator as a new podling. Starting with the 1.5.3 release our release notes include a section that acknowledges everyone who has contributed to that release. The contents of this section is based on the contribution report in Jira. Work in Jackrabbit trunk continues and I expect us to release Jackrabbit 1.6.0 in a few months. After the 1.6 release we'll most likely start targeting Jackrabbit 2.0 for release later this year. Jackrabbit 2.0 will require Java 5 as the base platform. o Infrastructure We have migrated our Hudson CI builds to the new minerva.apache.org slave server. The CI builds are now configured to deploy snapshots to the new repository.apache.org server. We are planning to start using the repository.apache.org server also for staging Maven releases. The Jackrabbit zone that we used earlier for CI builds is being removed as we no longer need it. We have configured monthly Google Analytics reports to be sent to our development mailing lists. This is not truly optimal as each report needs to be separately approved by a moderator (due to the variable sender address), but for now this works well enough as a mechanism of sharing site statistics with everyone interested.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We released Apache Jackrabbit 1.5.0 on December 8th. We also made the following patch releases from the 1.4 branch: * jackrabbit-core 1.4.6 on October 7th * jackrabbit-classloader 1.4.1 on October 2nd * jackrabbit-jcr-server 1.4.1 on September 30th o Legal We use Google Analytics to track usage of our web site. We posted a privacy policy that mentions the Analytics use on our web site and continue to work with legal-discuss@ to resolve concerns that were raised about the use of Google Analytics. o Community Claus Koell joined the Jackrabbit team as a committer and PMC member. The slump in community activity over late summer seems to be gone and we're back to normal levels of mailing list and commit activity. Based on interest to the CMIS implementation effort (see below), we have extended write access in our sandbox area in svn to all Apache committers. We are considering starting a "JCR Commons" subproject for managing the development and release of a number of our components that are not tightly coupled with the Jackrabbit content repository implementation. This subproject would keep using our existing mailing lists but would have its own web site (under http://jackrabbit.apache.org/commons/) and separate issue trackers and release cycles for each component. See http://markmail.org/message/qqlvlwpgi5oauak6 for more details. o Development Development in trunk continues with post-1.5 features, and I expect us to release Jackrabbit 1.6 early next year. Jackrabbit 2.0 (and the JSR 283 reference implementation) will probably be released later next year. A new sandbox component was started for an effort to implement the proposed Content Management Interoperability Services (CMIS) specification on top of a JCR content repository. o Infrastructure We created a new Jira project (JCRCMIS) for the CMIS implementation effort and plan to create more assuming the JCR Commons subproject gets started. We've enabled wiki markup and the patch-available workflow in the JCRCMIS project. If these features work well, we will enable them also in our main JCR project in Jira.
No identified concerns over "indemnify and hold harmless" clause.
The board is very happy with the initiative taken to publish a privacy policy.
We noted that Apache Commons is an option available to them, should they wish to explore that alternative.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases No releases were made since the last report. o Legal We use Google Analytics to track usage of our web site. We are working with site-dev@ and legal-discuss@ to resolve the recent concerns about how the site usage data can be made available equally to everyone. o Community No new committers or PMC members were added since the last report. There has been a decrease in mailing list and commit activity in the past quarter and we've seen some cases of issues or questions being dropped. This is partly because of the summer vacations but also due to a number of core committers having been otherwise occupied. We'll keep an eye on the situation and expect things to normalize soon. We will participate and present Apache Jackrabbit in the upcoming ApacheCon US. o Development We keep working towards Jackrabbit 1.5 in near future and Jackrabbit 2.0 (and the JSR 283 reference implementation) later on. o Infrastructure No issues at the moment.
Henning to communicate that every project that uses Google Analytics needs to have a published privacy policy.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Since the last report we made a number of small component releases and one older maintenance release. The releases were: * March 26, 2008: jackrabbit-core 1.4.2 * April 2, 2008: jackrabbit-jcr-commons 1.4.2 * April 9, 2008: jakcrabbit-jcr-rmi 1.4.1 * May 8, 2008: Apache Jackrabbit 1.3.4 * May 8, 2008: jackrabbit-core 1.4.3 * May 9, 2008: jackrabbit-core 1.4.4 * June 9, 2008: jackrabbit-core 1.4.5 o Legal The license issue noted in the previous report (external party using our code without proper attribution) has been resolved. We have been clarifying our LICENSE and NOTICE files based on recent discussions on legal-discuss@ and the incubating sling-dev@ mailing lists. o Community Esteban Franqueiro and Alexander Klimetschek became committers and PMC members of Apache Jackrabbit. Many members of our community attended ApacheCon EU and we also organized a free-for-everyone JCR community gathering along the conference. o Development We are working towards Jackrabbit 1.5 in near future and Jackrabbit 2.0 (and the JSR 283 reference implementation) later on. o Infrastructure We switched to Hudson for our CI builds. We requested and got FishEye indexing for our codebase. The svn.eu.apache.org mirror is much appreciated as most of our committers are based in Europe.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Apache Jackrabbit 1.4 was released in January. We are considering switching to releasing individual components in a more frequent and fine-grained manner. So far Jackrabbit releases have contained new versions of all Jackrabbit components. The first component release, jackrabbit-core 1.4.1, was made in February. o Legal Apache Jackrabbit uses or bundles no cryptographic code, so there is no need for export control notifications. We have identified a minor license violation by an external party bundling Jackrabbit code without meeting all the ALv2 requirements (no NOTICE file, etc.). With help from the legal team, we have notified the party in question and expect the issue to be resolved soon. o Community The Jackrabbit PMC has voted to invite Esteban Franqueiro to be a Jackrabbit committer and PMC member. We are waiting for the CLA to proceed with the committer account and other administrative bits. We are planning to have a JCR community gathering event right next to the ApacheCon EU next month in Amsterdam. o Development The 1.4 release was well received, and with increased usage we've also seen many requests to make the default installation and out-of-the-box experience smoother for new users. We're working on addressing those needs. The ongoing work towards the JCR 2.0 reference implementation continues, and with major new features and changes entering the codebase we may see some instability of the trunk during the months ahead. On the other hand there's recently been much focus on improving test coverage and more test automation, which should help us maintain stability of the codebase. Some of our users are not yet ready to upgrade from 1.3 to 1.4, so we are working on the 1.3 maintenance branch to produce a 1.3.4 release with selected bug fixes and improvements from newer releases. o Infrastructure Our web site is now managed using Confluence. We have had problems with our private Continuum installation in the Jackrabbit zone, and so we are currently migrating our CI builds to the Hudson zone.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Apache Jackrabbit 1.3.3 was released in October. We are currently working on the 1.4 release. Jackrabbit 2.0, with JCR 2.0 support, will likely be released next year. o Community Martijn Hendriks and Ard Schrijvers were added as a committers and PMC members. The recent decision by the Apache Jakarta PMC to close the Slide project has brought a number of people interested in WebDAV to the Jackrabbit mailing lists. Most notably there is interest in extending and further developing the WebDAV client library in Jackrabbit. We may well end up working together with the new Apache HttpComponents project on this front. o Development The main development focus at the moment it on the 1.4 release, but there's already some work towards implementing the new JCR 2.0 features being specified by Jsr 283. Once the 1.4 release is out we will need to decide when and how to split Jackrabbit into separate JCR 2.0 development and JCR 1.0 maintenance branches. A sandbox project was started for prototyping the Jackrabbit Next Generation Persistence proposal that tries to address some long term architectural issues in Jackrabbit. o Infrastructure We have acquired a Confluence wiki space for managing our project web site but we have yet to migrate the web site contents.
Approved by General Consent.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Apache Jackrabbit 1.3.1 was released in July. We are currently working on the 1.4 release, due out later this year. Jackrabbit 2.0, with JCR 2.0 support, will likely be released next year. o Community Christoph Kiehl and Thomas Müller were added as a committers and PMC members. Brian Moseley resigned to emeritus status. The Jackrabbit PMC decided to sponsor the new incubating Sling project. There is lots of community overlap and interest in seeing more open source tools built on top of the JCR API. Our two Google Summer of Code projects ended successfully, even though the amount of community interaction related to the projects was lower than expected. The resulting JCR example applications will be used as a part of Jackrabbit documentation. There will be a JCR session in ApacheCon US, and JCR training (assuming enough attendance) in both ApacheCon US and OS Summit Asia. The Sling project will also be presented. o Development We are seeing lots of development related especially to query features and a new storage model for binary content. There has also been interest in threads and locking behaviour within Jackrabbit core. We are promoting two prominent subprojects, the OCM and SPI layers, to release components in Jackrabbit 1.4. JSR 283 has released the public draft of the upcoming JCR 2.0 specification, and we have started working on implementing the new new features. The goal is to make Jackrabbit 2.0 (or an early snapshot of the release) the reference implementation of JSR 283. o Infrastructure We are considering switching from MoinMoin to Confluence for our wiki and using Confluence to manage also our official web site.
Approved by General Consent.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases Apache Jackrabbit 1.3 was released in April. We are currently working on the 1.3.1 release, and initial planning for a 1.4 release later this year and 2.0 next year has begun. o Community Christophe Lombart was added as a committer and PMC member. An object-content mapping tool was successfully moved from the incubating Graffito project into a Jackrabbit subproject. Jackrabbit received lots of attention in ApacheCon EU where we had one tutorial and one normal session on Jackrabbit and JCR. A Jackrabbit BOF session also took place, although it ended up being quite unstructured. We have two Google Summer of Code projects in progress this summer. Both projects have been relatively quiet so far, but hopefully we'll get them up to speed soon. Jacco van Weert has announced a nice JCR Controller tool on the user mailing list and is interested in bringing it to Jackrabbit through the Apache Incubator. o Development Jackrabbit is being actively developed on a number of fronts. Increasing numbers of good patches are coming in, and various technical and architectural issues are being actively debated on the mailing lists. The public draft of the upcoming JCR 2.0 specification will probably be soon released by JSR 283. We are planning to use the public draft as the main requirements document when implementing the changes and new features required to make Jackrabbit 2.0 the reference implementation of JSR 283.
It was suggested that, following the Jackrabbit example (which was from the Incubator report guidelines), that all TLP projects provide a small description of what the TLP "does".
Approved by General Consent.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We released three versions of Apache Jackrabbit; 1.2.1 in January, 1.2.2 in February, and 1.2.3 in March. The 1.2 release candidate needed to be cancelled and repackaged as 1.2.1 due to a last-minute issue that was raised during the release vote. This prompted a discussion on release candidates and versioning, which in turn resulted in some improvements to our release process. We are currently working on the 1.3 release. o Community Przemyslaw Pakulski was added as a committer and PMC member. The user mailing list that was launched last year has reached the activity level of the development list and continues steady growth. The total mailing list activity is now higher than ever before. One session and one tutorial on JCR/Jackrabbit have been scheduled for the upcoming ApacheCon EU. We are also planning to organize a Jackrabbit BOF during the conference. Based on the experiences from last summer, we are proposing a Google Summer of Code 2007 project to build a JCR demo application based on Apache Jackrabbit. There is interest in starting a new incubating content analysis toolkit project named Tika. Hopefully the project will as a side effect build more bridges between the Lucene and Jackrabbit communities. o Development The 1.2 releases include a new beta-level clustering feature that is attracting much interest. Many corner cases are being ironed out based on feedback and bug reports from the user community, and it seems that we can soon declare the feature stable. The main new feature in the 1.3 release is a set of "bundle persistence manager" components contributed by Day. These components bring a major performance boost to many Jackrabbit user cases. The contributed IP has been cleared and is now being integrated into the Jackrabbit codebase. There have been a number of cases where users have suggested some internal changes to better handle specific performance and other requirements. Unfortunately few of such discussions have resulted in proposed patches. We should do better to encourage patch submissions. o Infrastructure The Solaris zone we requested is now up and running. We have a Continuum installation doing nightly builds and continuous integration tests for all the Jackrabbit release components. So far we've seen zero build-breaking commits.
Approved by General Consent.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project has progressed nicely since the September status report. We have no board-level issues at this time. o Releases We have released two versions of Apache Jackrabbit: 1.1 in October and 1.1.1 in December. The 1.2 release is scheduled to happen by the end of the year. o Community No new committers have been added since September. One contributor was just elected for committership, but the process is still pending on us receiving the required CLAs. The number of active contributors has grown lately, and I expect to see new committers being elected in near future. Most notably we've seen a number of contributions from employees of Cognifide, a consulting company with JCR expertise. A CCLA has been requested. There were two short Apache Jackrabbit presentations during the ApacheCon US and some discussion on potential cooperation with other related Apache projects. o Development The Jackrabbit build environment was recently upgraded to Maven 2 along with a restructuring of the Jackrabbit component projects. An initial clustering implementation was added to Jackrabbit core and will go out as a beta feature in the 1.2 release. The Jackrabbit dependencies to Apache Lucene and Apache Derby were upgraded to more recent versions. A number of forward-looking design discussions have occurred on the mailing list, often based on feedback from outside the core development group. o Infrastructure We've requested a Solaris zone for setting up nightly builds and automating integration tests and Maven reporting.
Approved by General Consent.
The Apache Jackrabbit project has progressed steadily since our last status report. We have no board-level issues at this time. o We voted in Julian Reschke as a new committer and PMC member. o The Apache Jackrabbit 1.1 release is scheduled to happen at the end of September. o The recent face-lift of our web site received some attention due to the "customized" Apache feather logo included in the design. The issue was discussed within the PRC and for now we are back to using the standard Apache logo to link back to the foundation. o Day Software has contributed an initial SPI layer for the JCR API based on earlier work within the JSR 283 expert group. The ongoing SPI effort has potential to clarify and better modularize the Jackrabbit core. o We have discussed with the incubating Apache Graffito project on perhaps moving the generic object-content mapping tool they are developing into the Apache Jackrabbit project where the tool could enjoy a wider community of interested users and developers. The feedback within both projects has been positive. o Our Google Summer of Code project ended successfully with a backup tool that implements almost all of the planned features. The missing feature (restoring version histories) identified a need for structural changes within the Jackrabbit core and we are working on solving this issue. The GSoC experience also sparked a good discussion on the policies of accepting code changes.
Justin asked if the contribution for SPI recorded as a grant? Jim noted that we had not received a software grant for the code, but that Day Software does have a CCLA on file. Greg was to contact the PMC to get clarification on whether the SPI contribution required a grant.
At this point Justin asked if the ASF should have a policy on moving code between projects? It was noted that the Apache License allows for any PMC to use code in any other PMCs codebase, since it is assigned to the ASF and not to a PMC. Cliff noted that there is ongoing discussion regarding the scope of patents in this case, and what is meant by "the work" when code is copied or moved. Cliff will continue to work this patent angle, but the board agreed that we have no policy in place other than all code is available for reuse by all PMCs, which is implicit and implied in the license.
Approved by General Consent
WHEREAS, the Board of Directors heretofore appointed Roy T. Fielding to the office of Vice President, Apache Jackrabbit, and WHEREAS, the Board of Directors is in receipt of the resignation of Roy T. Fielding from the office of Vice President, Apache Jackrabbit; NOW, THEREFORE, BE IT RESOLVED, that Roy T. Fielding is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Jackrabbit, and BE IT FURTHER RESOLVED, that Jukka Zitting be and hereby is appointed to the office of Vice President, Apache Jackrabbit, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 6A, Change the Chair of the Jackrabbit PMC, was approved by Unanimous Vote.
The Apache Jackrabbit project has had a relatively quiet two months since our last report. We have not added any new committers and we have no board issues at this time. We successfully released Apache Jackrabbit 1.0.1 on June 2nd and are currently working on a 1.1 release. Most of the effort has been around cleaning up the edge cases as more new developers send in bug reports related to their own application's use of the 1.0 release. We also have one active SoC project working on a backup system for JCR repositories. Hopefully, we'll be seeing more patches soon from developers outside the core committers. I would be happier if we had some new blood to nominate for the PMC. At some point over the next two months, I am hoping to turn over the Jackrabbit PMC chair position to someone else on the project. Being chair of two different projects is a bit too distracting and I think more people need to learn how to do it.
Tabled due to time constraints.
The Apache Jackrabbit project has had a relatively quiet month since our last report. We have no board issues at this time. The response to our 1.0 release has been very positive and the number of active participants on the dev list has increased substantially. Many of the Jackrabbit developers attended the JSR 283 face-to-face meeting in Basel, Switzerland, on May 2-3. The JSR 283 EG agreed that Jukka Zitting could publish a summary of what was being planned for future JCR API revisions to the public Apache lists. Issue items and proposals for the JCR 1.1 and 2.0 APIs are being tracked at <https://jsr-283.dev.java.net/>. All of the Jackrabbit committers are also members of the JSR 283 expert group.
Approved by General Consent.
Over the past month, Apache Jackrabbit completed its graduation from incubator, moved to its new home at jackrabbit.apache.org, and made our big 1.0 release using the mirrors. http://jackrabbit.apache.org/ http://www.apache.org/dist/jackrabbit/RELEASE-NOTES.txt The only thing of board interest is that we have implemented the file header proposed on legal-discuss last year. /* * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. The ASF licenses this file to You * under the Apache License, Version 2.0 (the "License"); you may not * use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */
Approved by General Consent.
6. Special Orders
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to the Content Repository for Java Technology API and its implementation as the Apache Jackrabbit content repository, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Jackrabbit PMC", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Jackrabbit PMC be and hereby is responsible for the creation and maintenance of open-source software and documentation related to the Content Repository for Java Technology API and its implementation as the Apache Jackrabbit content repository and tool sets, based on software licensed to the Foundation; and be it further RESOLVED, that the office of "Vice President, Apache Jackrabbit" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Jackrabbit PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Jackrabbit PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Jackrabbit PMC: Tobias Bocanegra <tobias.bocanegra@day.com> Roy T. Fielding <fielding@gbiv.com> Stefan Guggisberg <stefan.guggisberg@gmail.com> Serge Huber <shuber2@jahia.com> Felix Meschberger <Felix.Meschberger@day.com> Brian Moseley <bcm@osafoundation.org> David Nuescheler <david.nuescheler@gmail.com> Dominique Pfister <dominique.pfister@day.com> Peeter Piegaze <peeter.piegaze@day.com> Edgar Poce <edgarpoce@gmail.com> Marcel Reutegger <marcel.reutegger@gmx.net> Paul Russell <prussell@apache.org> Angela Schreiber <anchela@day.com> Sylvain Wallez <sylvain@apache.org> Jukka Zitting <jukka.zitting@gmail.com> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Roy T. Fielding be appointed to the office of Vice President, Jackrabbit, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Jackrabbit PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Jackrabbit Project; and be it further RESOLVED, that the Apache Incubator PMC shall, upon deciding that the Jackrabbit incubating project has graduated, transfer all oversight and responsibility for the Jackrabbit incubating project and its artifacts to the Apache Jackrabbit PMC. Resolution 6A, Establish the Apache Jackrabbit Project, was approved by Unanimous Vote.
Jackrabbit accomplished its first official incubating release with version 0.9 of the Apache Jackrabbit reference implementation and JCR-RMI tools. Day Software has confirmed that the version 0.9 jars have passed the JCR 1.0 TCK with the current exclude list. We are now getting reorganized for graduation from the Incubator to our own top-level project at the Apache Software Foundation. The Jackrabbit committers voted on March 11, 2006, to request graduation. In addition, we made a call to refresh the list of active committers for an accurate presentation to the board; Stefano Mazzocchi, Gianugo Rabellino, Tim Reilly, and Andrew Savory have requested emeritus status, meaning that they won't be listed on the initial project management committee but are welcome to come back if they choose to rejoin the project at a later time.
Jackrabbit added four new committers to the project this quarter: Serge Huber Felix Meschberger Brian Moseley Angela Schreiber in recognition of their outstanding and sustained contributions to the project. Jukka Zitting has volunteered to be the RM for our first set of incubating releases. We plan to seek graduation from incubator as soon as we have a track record for a successful release vote.
The Apache Jackrabbit podling is slowly recovering from the impact of finalizing JSR 170, initializing JSR 283 (the next JCR specification revision EG), and the summer holiday schedule. We are in the process of reconfiguring our source directories for an eventual 1.0 release and Maven 2 support. No new committers were added this quarter, though we expect more to be added soon.
Jackrabbit has attracted public interest from many different projects, both open source and commercial in nature, and has over 250 people reading the developer list. During the past quarter we added one new committer, Edgar Poce, and cleared the minimum threshold of three independent committers. The big news is that JCR, the Content Repository for Java Technology 1.0 API, has been completed by the JSR 170 expert group and received final approval from the J2SE/EE executive committee at the end of May. We are currently working on restructuring the Jackrabbit project directories in preparation of an eagerly anticipated first release candidate and passing the official TCK, at which point we are hoping to graduate from Incubator to TLP status for the 1.0 release.
http://incubator.apache.org/jackrabbit/ http://incubator.apache.org/projects/jackrabbit.html Jackrabbit is doing well as a project and is attracting interest both within other Apache projects (Lenya and Graffito in particular) as well as from new folks in the Java community. We added two new committers, Jukka Zitting and Dominique Pfister, and have received sustained contributions from Serge Huber, Edgar Poce, Angela Schreiber, Felix Meschberger, and others. Jackrabbit's only problem right now is continued reliance on JCP EG private discussions due to the unfinished nature of the JSR 170 Content Repository for Java Technology API. JSR 170 is expected to be submitted for final draft status in early May, after which all of the discussion can be moved to Apache lists. We anticipate graduating from Incubator sometime soon after that.
The Jackrabbit project has completed all of the Incubator checklist items in terms of moving to Apache and getting the IP transfer done. With the help of Maven, we have a full website set up at http://incubator.apache.org/jackrabbit/ with a few link bugs due to the svn/viewcvs integration. Our big task from now to graduation is to get the community more involved in development, planning features, integrating with some of the DB projects, and scoping out interesting applications to build on top of the interface.