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: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Activity on the project over the last quarter is higher than the previous quarter, with around 60 commits to main from 5 individuals compared to just 23 commits from 2 individuals in the previous. We do tend to see an increase in commits over the last weeks of December and early January as people have more time off during the holidays. We have a vote going in the PMC for a potential committer and will hopefully have something positive there to report next quarter. ## Activity Work on Jakarta EE 10 is still the main focus. Progress has been made and although we've not setup all the TCKs and have complete numbers, we are far more complete than before. Discussion is in progress on doing a first milestone of TomEE 10. Some of this work was to incorporate the latest BatchEE into TomEE and get the Jakarta Batch TCK tests passing. This involved filing a TCK Challenge against some TCK test code we felt was relying on non-standard behavior. Praise to Richard Zowalla for bringing this to the Jakarta Batch spec and getting it approved without conflict. A release of TomEE 9.1.2 was shipped in December with several library upgrades addressing CVEs. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 9.1.2 on December 19th, 2023
@Justin: follow up on mail list moderation
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Activity on the project over the last quarter remains low with approximately 23 commits to main since our previous report (9/17). We started a "Health of this project -- should we keep going?" thread on our user list in attempt to create more awareness of our need for more contributors. Three people identified themselves as interested, but have not followed through in the months since. A thread "TomEE 10 in the pipe or not ?" was started by cross posting on both the users list and dev lists asking for updates on the community's progress. These kinds of posts do not give us hope that the project's need for more resources and consequence of not having them is being understood. ## Activity As mentioned above, activity has been low. The 20-ish commits to main in the last quarter have largely been for library upgrades. One of those commits did come a contibutor who is not a committer was a small tweak on existing code, with roughly 9 lines added and 8 removed. A release of Apache TomEE 8.0.x was created containing library upgrades to address CVEs. This may be the last version of 8.0.x unless one is made before the EOL date of December 31st. Efforts to do a release of Apache TomEE 9.1.x are in progress, also containing library upgrades. A second vote is up and likely to complete. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.16 on November 11th, 2023
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Activity on the project over the last quarter has been low with just 10 commits to main in the previous three months from today (9/17). We seem to be steadily trending downward over the years. Here's an analysis of commits broken up by calendar quarter since work first started on TomEE 1.0. Year Q1 Q2 Q3 Q4 Average ---- --- --- --- --- ------- 2023 30 42 7 26 2022 248 175 78 107 152 2021 66 141 41 34 70 2020 33 147 123 94 99 2019 446 190 214 120 242 2018 156 58 141 555 227 2017 58 88 108 104 89 2016 116 114 174 69 118 2015 234 263 65 127 172 2014 234 353 396 363 336 2013 434 264 195 188 270 2012 632 671 632 597 633 2011 111 266 486 400 315 The project has actively been trying to increase participation. Users on the user list are frequently encouraged to help and given the "every contribution helps" perspective. The few that have shown interest are given very warm and encouraging responses with a great deal of coaching to feel comfortable asking questions, not get discouraged, not be hard on themselves and are encouraged to start small and get the encouragement a quick win before trying bigger tasks. Despite our efforts, almost no one makes it to the point where they can contribute to core code in any capacity. Contributions typically stop at minor doc updates and library upgrades. Those that do show enough promise to make it to committer tend to not continue contributing very long. We've added 7 committers in the last 6 years and of that list only one contributes regularly. Two in the list stopped contributing once they gained the committer title, three stopped committing in the first year. Lowering the bar to commit hasn't really helped. A significant bar to entry has always been that the TCKs we implement were restricted and not available to the public. These were all open sourced in 2018/2019 and we had hoped this would be key in enabling more members of the community to help with the main work of the project, getting compliance tests to pass and shipping certified releases. This hasn't really helped and in fact the new faster pace at which specifications are released seems to only hurt us. We had reported build times as a potential deterrent (they were 4-5 hours) and worked with Infra to help setup builds in AWS. This was complete last quarter. So far we have had only one PR from a contributor to test out this new system and that PR has remained in a breaks-the-build state for 2 weeks. We will keep trying, but overall it seems like very few are in a position to contribute. There is a high bar in terms of time and experience we simply cannot control or reduce. Fixing one TCK test can take a very experienced person one week full-time. You need to research cryptic text in specifications, do deep debugging in code you don't know to find causes, and find intricate solutions that do not cause new failures elsewhere. Due to the time involved it isn't something you can do without the support of your employer and it doesn't appear anyone who uses TomEE has interest in investing in the project at that level. ## Activity As mentioned above, activity has been low -- 10 commits to main in the last 90 days. No new releases have been shipped. The work done has largely been around the integration between TomEE and CXF, specifically to get CXF 4.0 fully integrated. We have seen a new face arrive and offer to help in this area and has openend a PR to help setup the new Jakarta REST TCK suite from Jakarta EE 10. It's not fully working and breaks the build, but is still very positive. Any kind of start is a good start. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: None
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Contributions over the last quarter have been slower over the previous quarter. I suspect some of this is due people focusing on other initiatives post-TomEE 9.0.0 final release. TomEE 9 took nearly 3 years and was effectively created twice due to the change of direction in how we approached the javax-to-jakarta migration. We had noted issues with build times taking excessively long due to the size of our codebase and age of the build machines, which are over 10 years old. The project is currently incorporating the recently completed work to enable builds in AWS, which should have very significant impact the project as we struggle with 5-hour builds on any change. The project would like to send great thanks to all the Infra team for thier support and bringing this to life. We are very excited and look forward to reporting more on this in future reports. ## Activity Work on TomEE 10 did start immediately after the release of TomEE 9.0.0 with a handful of PRs to increase the level of various specifications and upgrade to the newest implementations. Unfortunately, nearly all the PRs broke the build and we quickly wound up with a few hundred test failures. We did have this exact experience at the start of TomEE 9 and the build ended up staying broken for over a year. The 5-hour build time did contribute to that, though is not the cause. The cause is as stated in the previous report; PRs that break the build being submitted and merged and the submitter infrequently helping to address the failures. An attempt to manage this was made by putting all the broken PRs into a dedicated branch, so work could continue in main. The obvious impact the temporary branch had 90% of the activity and work could not happen on main without merge conflicts. It was pointed out as a bad idea and the temporary branch with all the broken PRs was closed and people were told to resubmit their PRs to main once they are able to pass a build. So far no one has done this and work on Jakarta EE 10 remains nacent. We do think the shorter build times made possible through Infra's AWS work will have positive impact. Most the PRs that break the build come from well-meaning contributors who don't have that much time to contribute. These people, who only have a few hours to spare, are the most impacted by the several-hour build times. Most work has been on maintenance of TomEE 9, which relied on the now discontinued Tomcat 10.0. To remedy this a TomEE 9.1 release was created based on Tomcat 10.1, which is actively maintained. The impact of this is that TomEE 9.1.0 can no longer be Jakarta EE 9.1 certified as Tomcat 10.1 uses a newer Servlet version than is allowed in a Jakarta EE 9.1 certified implementation (TomEE 9.0.0). This unfortunately means our celebration about being Java EE / Jakarta EE certified again after more than 10 years was very short lived; about 4 months. Our next chance will be when TomEE 10 is complete, which will likely be at least another year or more. The project concluded discussions on end-of-life policies, which were mentioned last report. As noted the paragraph above, maintaining releases is signficantly harder. Most patches cannot be backported due to changes in the javax-to-jakarta namespace. Most libraries are in a great deal of flux in how they intend to manage old javax code vs newer jakarta code. The result is libraries we need (old and new) are getting dropped, patches can't easily be backported and all maintenance is harder. The end-of-life policy decided on is to maintian the current major release and discontinue the previous major release six months after the new major version goes final. We think this more honestly reflects the resources we have based on the contributions we get. The end-of-life policy adopted for TomEE 8 is longer, however, and goes till December 31st, 2023. This was published in March and we hope that it gives people the awareness they need to spend the year migrating. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.15 on May 17, 2023 - Jakarta EE API 9.1.1 on May 21, 2023 - Apache TomEE 9.1.0 on June 12, 2023
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Contributions from non-committers over the last quarter have largely been in the areas of upgrading libraries and cleaning up properties. The challenge is, that these contributions are often untested and might introduce regressions, so we need to carefully run CI builds for every (little) pull request manually. Given that a TomEE full build takes around 8 hours on ASF hardware, this is a cumbersome adventure to monitor and track. Hopefully, INFRA can make some progress in providing ephermal runners hosted on AWS to ease this burden. List traffic, commits and number of releases is up significantly from the previous quarter as is often the case in the first quarter of the year. ## Activity After a considerable amount work, the project was able to pass all test required to claim Jakarta EE 9.1 Web Profile certification with TomEE 9.0.0. In addition, TomEE 9.0.0 is fully Micro Profile 5 compatible. First work started to move on to TomEE 10 which will target Jakarta EE 10 and MicroProfle 6.0. There is a long backlog of changes to the server that we've been delaying for the next major version, such as redoing how the server is built, eliminating drop-in war files and more that we've been discussing and are anxious to start now. As Jakarta EE 10 is the first release to have major new features since Java EE 8 and most Apache implementations still use the javax namespace there will be a major effort to migrate all related sources to the jakarta namespace. We are making good progress with these migrations. However,some more discussions are needed especially regarding the so-called "CDI Light" in CDI 4.0. We'll need to figure out how it can be implemented within OpenWebBeans. In addition, there were major changes in the tools to run the related specification TCKs as well as in the platform TCK itself. Our current setup does not work anymore, so we are currently in the process to figure out how we can run these tests in a performant way again. The project has begun discussion on end-of-life policies. In the past releases for older branches would simply stop being shipped with no formal decision or disclosure on shipping future releases. There is now a desire to formally decide on the future end-of-life date so users are aware and use the time to move to newer versions. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.14 on January 17, 2023 - Apache TomEE 9.0.0 on January 3, 2023 - Apache TomEE Patch Plugin 0.10.0 on January 2, 2023 - Jakarta EE API 10.0-M1, on January 11, 2023 - Jakarta EE API 9.1, on January 10, 2023
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Contributions from non-committers over the last quarter have largely been in the areas of upgrading libraries and minor tweaks to some specific documentation pages. The challenge with library upgrade contributions is they are often untested and introduce regressions that do not get addressed in the PR. Hopefully, we can better mentor new contributors to more completely help and be trusted with commit. Some of this challenge is created by the fact that PRs from non-contributors do not get built in the Apache Jenkins install due to strict security policy. While this policy makes sense and should remain, it would be very useful to have the ability to "green light" known contributors, perhaps by adding them to our project's .asf.yaml file. There have been two PRs from non-committers that did involve getting a TCK test to pass, which is extremely rare and a very promising development. ## Activity Work towards TomEE 9 final is going very well and there are good chances a vote could go up in the next few days. All remaining MicroProfile 5.0 TCK compliance failures reported last cycle were fixed. As of this weekend, results for the Jakarta EE 9.1 Web Profile TCK are 32743 passing and 2 failing. The remaining two failures are in the websocket section of the TCK and are known to be somewhat flakey as they test timeouts. Once the remaining 2 failures are fixed, we are clear to release TomEE 9.0 final. The community is very excited to move on to TomEE 10 which will target Jakarta EE 10 and MicroProfle 6.0. There is also a long backlog of changes to the server that we've been delaying for the next major version, such as redoing how the server is built, eliminating drop-in war files and more that we've been discussing and are anxious to start. As Jakarta EE 10 is the first release to have major new features since Java EE 8 and most Apache implementations still use the javax namespace there will be a major effort to migrate all their source to the jakarta namespace. Most use bytecode transformation tools to support the jakarta namespace, which will no longer work as the javax and jakarta APIs have finally diverged due to new features only in the jakarta.* APIs. Some projects have been stronly resistant to migrating sources to the jakarta namespace, so there may be some challenges. So far Tomcat, TomEE, MyFaces and CXF have done the jakarta source code change. CXF, however, is not targeting Jakarta EE 10 in their next major version 4.0, so there will be some need to help them get that release finished so EE 10 work can start. OpenWebBeans, Johnzon, BVal, OpenJPA, BatchEE and ActiveMQ are all still on javax and use bytecode transformation. OpenWebBeans, Johnzon, OpenJPA and ActiveMQ Classic would all need to be migrated to jakarta in source as their related specifications do have new features. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.13 on October, 24th, 2022 - Apache TomEE 9.0.0.RC1 on November 11th, 2022
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health It's been another good quarter for attracting new contributors. At least one or two of the individuals we attracted last quarter are still around and contributing periodically. Areas of contribution have largely been around updates to our comparison page for the different flavors of TomEE, library upgrades and one contributor indicating intentions to help implement MicroProfile specs. It's defininitely difficult to contribute to an app server project as the breath of feature set is so large. We're happy to see when people adopt a tiny piece such as a specific document, and we hope to broaden that interest to other docs or other areas of the server -- both are good. ## Activity MicroProfile 5.0 support moved from discussion to action and the community has largely completed migrating from the Geronimo MicroProfile implementations to the SmallRye MicroProfile implemenations. All TCK tests are passing aside from MicrProfile OpenTracing and MicroProfile JWT. MicroProfile JWT support is implemented natively in TomEE, not using Geronimo or SmallRye, and down to 2 failures. With the switch we are effectively jumping from MicroProfile 2.0 compliance all the way to MicroProfile 5.0, which is the most current version. The outcome has been overwhelmingly positive and has allowed some extra time to start looking at and giving feedback on the draft specs for MicroProfile 6.0, which is still in development. Being able to spend even a sliver of time working on the next major version of a MicroProfile spec while it's being developed is a significant milestone for the project. This is something we previously could only have dreamed of as we were in a perpetual state of catching up. We look forward to increasing that contribution across all the specs we implement in the coming months and years. Our current plan is to finish and release a final TomEE 9 compliant with Jakarta EE 9.1 and MicroProfile 5.0 then immediately switch to TomEE 10 targeting the very recently released Jakarta EE 10 and soon-to-be released MicroProfile 6.0. Some TCK work still remains for Jakarta EE 9.1 compliance with about 15 failing tests out of over 32,000. If all goes well, we will hopefully be writing about the TomEE 9 final release in our next board report. An attempt was made in early August to release an updated TomEE 7.1.x with some small fixes, however, the vote did not pass as the binaries contained several unfixed CVEs. The last TomEE 7.1.x release was 7.1.4 released on September 25th, 2020. There did not appear to be interest in fixing all outstanding CVEs as several the respective communities of affected libraries have stopped maintaining those versions. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.12 on June 14th, 2022 - Apache TomEE jakartaee-api-9.1-M2 jar on June 20th, 2022 - Apache TomEE 9.0.0-M8 on July 5th, 2022
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health It's been a good quarter for attracting new contributors. In mid-March, we had a user respond to a release announcement with the same "where's my stuff" question he'd asked 7 times before over the last 2.5 years. It was used as an opportunity to drive the message to the community open source is a get-what-you-give ecosystem and people need to contribute for it to function. Since then we've had about 4 new people sumbit their first PR and a few more new faces indicate they're interested in contributing. We're doing our best to enable people in hopes to have at least 1 or 2 of them stay with us. In our previous report, we reported PRs from non-committers was low at just one and we were mindful that this number needs to go up. We're happy to see this improvement and we'll be reporting next cycle on if this pace continues. ## Activity The community is largely done with the shift from bytecode transformation to source code updates as they way it handles the javax-to-jakarta namespace change. The master source is now TomEE 9 and completely based on the jakarta namespace. As well TCK results for TomEE 8 and TomEE 9 are now identical, each passing 99% of the Jakarta EE 9.1 Web Profile TCK. The community is now working towards creating another milestone release of TomEE 9. Much of this work involves helping related projects such as Apache BVal and Geronimo Javamail and Activation get current with specifications and do releases. MicroProfile 5.0 compliance has also been an active discussion as TomEE 8 currently supports MicroProfile 2.0 via a combination of implementations across Geronimo, CXF and TomEE itself. After some discussion the community has decided to try replacing the Apache Geronimo MicroProfile implementations with those produced under the external SmallRye project, largely developed by Red Hat. The primary motivation was lack of resources to contribute to the Geronimo implementations, which are out-of-date. The work required to update them would span 3 major versions and a javax-to-jakarta namespace change. Though it is not ideal to switch away from an Apache implementation, not being current with Jakarta EE and MicroProfile specifications over the last few years has hurt the project. Work integrating the SmallRye implementations into TomEE 9 is 80% complete. Our goal is to ship a TomEE 9 this year that is current in both Jakarta EE 9.1 and MicroProfile 5.0 specifcations, which are the most recent versions at the time of this writing. Jakarta EE 10 is slated to be released in a few weeks, so we will soon be a bit behind, but we will be significantly more up to speed overall in comparison to the last several years. The community is still actively maintaining the TomEE 8 branch and a release of TomEE 8.0.12 is up for a vote now. ## PMC changes: - Currently 13 PMC members. - Last PMC addition Richard Zowalla on May 23rd, 2022 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.11 on April 23rd, 2022 - Apache TomEE Patch Plugin 0.9 on May 9th, 2022 - Apache TomEE javaee-api-8.0-6 jar on May 26th, 2022
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health List traffic, commits and number of releases is up significantly from the previous quarter as is often the case in the first quarter of the year, post holiday-lul. The PMC is currently voting on a potential new PMC member and in discussion on a potential new committer. PRs from non-committers, however, was low at just one. We are mindful that this number needs to go up. One of the four release votes from this quarter has been open 14 days pending another PMC vote, which reinforces the need for us to keep adding to the PMC. ## Activity The community has decided to change the major version of the main branch from TomEE 8.0 to TomEE 9.0, which is currently still in milestone. Further, the approach we used to handle the javax-to-jakarta namespace transition and achive Jakarta EE 9.1 certification on TomEE 9.0.0-M7 is being shifted away from bytecode modification. In the new approach all sources in the main branch will discontinue use of the respective javax packages and refer to the jakarta equivalents. Only where there is no available jakarta alternative will bytecode modification be used. This is the case for many sister projects we depend upon such as ActiveMQ, MyFaces, CXF and more. It is hoped that these projects will themselves transition to the jakarta namespace. In the case of CXF, this is in progress. The current state of this transition is in a large draft PR, currently at 80 commits and 26 days old. It is so far managable and contributions are being made by more than one person, however it is likely we'll need to merge it to a new branch at some point. Release date for TomEE 9.0.0 final is not yet known. Significant work will likely need to be done to get the TCK to pass again once all changes are complete. Currently, the PR for 9.0 still does not build due to missing jakarta dependencies. A significant amount of work has been done investigating use of Github Actions to automatically open PRS to maintain certain generated files and other purposes. A large thank you to Infra for allowing/enabling projects to benefit from this great feature. The project has also discontinued all use of Google Analytics and migrated over to the ASF Matomo instance. Again, thanks to Infra for answering questions and providing guidance in this department. ## PMC changes: - Currently 12 PMC members. - Last PMC addition Cesar Hernandez on February 10th 2021 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.9 on January 10th, 2022 - Apache TomEE Patch Plugin 0.8 on January 21st, 2022 - Apache TomEE 8.0.10 on February 22nd, 2022
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health List traffic and commits have been somewhat lower in the last quarter compared to the previous quarters which saw large spikes due to Jakarta EE 9.1 certification efforts and build stabilization in TomEE 8. We're expecting to see the predictable uptick in activity in January after the holiday lul. ## Activity Primary points of discussion over the last quarter has been how to move TomEE 9 to final and if our bytecode modification approach is sustainable. Apache TomEE 9.0 M7 was released as certified in May of 2021. This implements the javax to jakarta namespace switch through the use of bytecode modification tools: Eclipse Transformer & TomEE Patch Plugin. While this did help us work on pursuing Jakarta EE compliance in both TomEE 8 and TomEE 9 in parallel, it does have limitations we'd like to resolve before moving TomEE 9.0 to final release. The bytecode modification approach is good for transforming a single zip or a jar with no maven dependencies. However, in situations where Maven is used to resolve dependencies transitively, the simply aren't good tools or attractive techniques that can upgrade the old javax dependencies in all the poms across a large codebase. The compromise the project is considering is to move the main branch of TomEE from 8 to 9, do the javax-to-jakarta transformation in java source and Maven pom.xml files, then only use bytecode modification for external dependencies. The cost of this approach is now not only will updates to TomEE 8 not also be reflected in 9 automatically, but merging code changes between 8 and 9 largely impossible due to the breaking namespace change. It does, however, appear to be the least costly approach given the bytecode modification restrictions and impact on the developer experience. A separate discussion was started on forming some clear policy similar to Tomcat's on which branches are maintained and will receive CVE patches. This is likely to be influenced by the pending decision to branch TomEE 9 and do the breaking javax-to-jakarta namespace change in source as backporting will often be impossible, increasing the cost of maintaining older branches. ## PMC changes: - Currently 12 PMC members. - Last PMC addition Cesar Hernandez on February 10th 2021 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE Patch Plugin 0.7 on October 20th, 2021
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health The project continues to see good turnout on release votes for a second quarter. The latest release saw 11 +1 votes total with 5 of those votes being binding. Though we are in good shape, we should still consider more PMC additions to keep the trend going in the right direction. ## Activity Efforts shifted to TomEE 8 after the considerable amount of work the community underwent to reach Jakarta EE 9.1 certification with TomEE 9 for the day of the Jakarta EE 9.1 release announcement. During the push several tests in the main build were broken and as mentioned in the previous report the TomEE 8.0.7 binaries had issues and the community decided not to publish them to the website. The 8.0.7 binaries were placed on the mirror system to sync to archive.apache.org, then immediately taken down. After a short break to recharge, work over the subsequent weeks went to fixing the tests and restoring a passing build. The last of this work finished recently and TomEE 8.0.8 went up for vote 9/1 and successfully completed 9 days later. With TomEE 8.0.8 released work will likely shift back to TomEE 9, which is still in milestone, to close remaining gaps required to do a final release. Part of this will involve helping out Apache BVal get a passing TCK result with the new jakarta namespace. During the push for certification, the project temporarily switched TomEE 9 to Hibernate Bean Validator, which is compliant and Apache Licensed. The project had some unfinished tasks since the migration off the Apache CMS. The proceess to generate/publish html to the final repo was still very manual. This has now been automated with Jenkins jobs triggered if any of the documentation sources are updated. Because the process was previously manual, contributions to the website sometimes went a few weeks before the site someone regenerated the site and published them. Now that things are automated and published very quickly after a PR merge, we have noticed a resurgance of activity translating examples on the website to other Spanish and Portugese. ## PMC changes: - Currently 12 PMC members. - Last PMC addition Cesar Hernandez on February 10th 2021 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.8 on September 9, 2021
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health The project is very happy with the progress reported in the last report. Initiatives to release more frequently and add more committers and pmc members have all gone well. Our last release received 7 binding PMC votes and 11 votes overall, which is very good for us as some votes in the past struggled to get 3 binding votes. ## Activity The project flipped priorities on pursing Jakarta EE 8 and Jakarta EE 9 certification and made Jakarta EE 9 the primary focus. The Jakarta EE 9.1 release is completing Monday May 17th on the Eclipse side of the fence and the project very much wanted to be part of the announcements. On this note we'd like to thank Rob Tompkins and the board for accepting Guest membership in the Eclipse Foundation so that we can be listed in on the jakarta.ee website once certified. Other projects at Apache are not restricted and can be listed without Apache being a member of the Working Group. Implementations of the Jakarta EE Platform and Web Profile are treated differently and do need to be members of the Working Group to be on the certification page at jakarta.ee, so we are very grateful to everyone who made that possible. After a considerable amount work, the project was able to pass all test required to claim Jakarta EE 9.1 Web Profile certification. This is a historic milestone as the last certification we were able to achieve was Java EE 6 in 2011, 10 years ago. Apache's Java EE TCK license expired about 2 months before Java EE 7 was released. After access was restored through Jakarta EE, it's been a very long road working through all the tests after not having access for so many years. As of this week there are 16 certified implementations of Jakarta EE and Apache TomEE is the only one to ship the Apache implementations of various Jakarta specifications such as Tomcat, ActiveMQ, OpenJPA, OpenEJB, Johnzon, OpenWebBeans, BVal, Geronimo JavaMail, Geronimo Transactions, Geronimo Connectors, etc. All 15 other implementations use and share more or less the same, usually Eclipse, implementations. This means we have to match the resources of all other Jakarta EE implementations combined. We are very proud we were able to do this and that Apache and Apache TomEE offers true diversity to the ecosystem where it would not otherwise exist. In pursuit of certification there were some backwards incompatible changes made to the released TomEE 8.0.7, which is bytecode transformed into TomEE 9 and the basis of TomEE 9.0.0-M7, which is the officially certified release. Both versions went up for a release vote simultaneously as there is interdependence between them. However, due to the regressions in 8.0.7 the project has opted to not put 8.0.7 on the website and will only be leaving it on the mirror system briefly. The community plans to address all regressions and build failures and release a TomEE 8.0.8 as soon as possible. Other areas of focus likely to surface are improving the website to host the TCK results for each releases and take advantage of the Jakarta EE logo and of course discuss what criteria we think must be met for a TomEE 9.0.0 final release. ## PMC changes: - Currently 12 PMC members. - Last PMC addition Cesar Hernandez on February 10th 2021 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.7 on May 10, 2021 - Apache TomEE 9.0.0-M7 on May 10, 2021
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Reported in the last two board reports, the project has been focusing on releasing more frequently. January 2020 saw one release of TomEE 8, our main branch, and long gap till the next TomEE 8 release in August, 2020. We're proud to report we've done 4 releases of TomEE 8 since August, with an average of 2 months between releases. We've also reported delays in getting enough PMC votes to get releases out the door. Things there have also improved and we average 6-10 days each vote, with votes able to close early but just being held open to get more feedback. Also reported previously are efforts to expand the PMC to address some of the health issues. This quarter we have voted in a new committer, Richard Zowalla, and a new addition to the PMC -- name omitted from the report as the 72 hour lazy consenus from the board has not elapsed. The project is very happy with the progress and good start to 2021. We hope to keep up this momentum and will continue reporting on these fronts. ## Activity The primary focus has been completing Jakarta EE 8 certification and pursuing Jakarta EE 9 as a side effort. Both of these come from the same codebase and the Jakarta EE 9 release achived via tools that translate bytecode referencing javax packages to now use the equivalent jakarta packages. While this is overall successfull and we are passing 99% (187 failing tests) and 98% (431 failing tests) of the Jakarta EE 8 and Jakarta EE 9 Web Profile TCKs, we do see limitations for our embedded users, testing support and using different dependencies in TomEE 8 vs TomEE 9. For example, we'd like to use Tomcat 10 in TomEE 9 instead of Tomcat 9. Discussion is active on how we can address that and solutions being discussed include doing an actual javax-to-jakarta cutover in source. A large chunk of our remaining failures for Jakarta EE 8 Web Profile are only resolvable via test challenges that must be resolved in the respective Jakarta specification projects at Eclipse. The project has invested time shifting from Buildbot to Jenkins. The experience so far has been not great and our build time is roughly 2.5 hours on Buildbot and over 4 hours on Jenkins. The Jenkins install seems to have significantly fewer resources, which is painful as Jenkins is significantly better for Maven-based Java projects as it does track the pass/fail history of each individual test and can point out things like intermittent failures, frequently failed tests, etc. Some effort has been placed into investigating Github Actions to see if that can open new options. The project has successfully completed migration away from the Apache CMS, which is an activity that has been in progress since February of this year. Work continues on the website rebranding and updating of the technology used. David Jencks has put considerable effort into migrating the website to Antora, which the project is still hoping to leverage. We still have hopes to improve the documentation and further improve the website infrastructure, though no activity was done on that this quarter. ## PMC changes: - Currently 12 PMC members (pending). - 1 PMC members voted in the last 3 months (pending board approval) - Last PMC addition pending and sent to board Wed Feb 10 2021 - Previous PMC addition Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 - Previous committer added was Daniel Dias Dos Santos on June 23rd 2020 ## Releases: - Apache TomEE 8.0.5 on November 24, 2020 - Apache TomEE 9.0.0-M3 on November 24, 2020 - Apache TomEE 8.0.6 on January 25, 2021
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health The project has been attempting to release more rapidly, and ideally this would become a monthly activity, at least on the TomEE 8 branch, to follow the Tomcat release cycle. As reported last quarter, one problem is being able to obtain PMC votes in timely manner. PMC activity on votes has increased since the previous report, which is very positive. The project still sees the need to also add more PMC members to further address this. Hopefully, there will be more progress on that front next quarter. ## Activity The project has successfully completed migration away from the Apache CMS, which is an activity that has been in progress since February of this year. Work continues on the website rebranding and updating of the technology used. David Jencks has put considerable effort into migrating the website to Antorra, which the project is still hoping to leverage. Activity overall on the project was slightly lower this quarter as members of the project played a significant role in getting the Jakarta EE 9 final release out the door. This includes 30+ specifications which all needed to be in final form by last Friday. With this major work done, the activity in TomEE and many Apache projects that implement these specifications is likely to dramatically increase as we all work to pass these newly completed TCKs. This will be the first time in our history we can do this TCK work openly and the project is very excited. The project made TomEE 8.0.4 and 9.0.0-M2 releases available on August 7th. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 32 committers. - Last committer added was Daniel Dias Dos Santos on June 23rd 2020. ## Releases: - Apache TomEE javaee-api-8.0.5 on October 25th, 2020 - Apache TomEE 7.1.4 on September 25, 2020 - Apache TomEE 7.0.9 on September 25, 2020 - Apache TomEE 9.0.0-M2 on August 7, 2020 - Apache TomEE 8.0.4 on August 7, 2020
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health We're delighted to welcome a new committer to the project, Daniel Dias Dos Santos, who has continued to contribute to the project regularly after becoming a committer. The project has been attempting to release more rapidly, and ideally this would become a monthly activity, at least on the TomEE 8 branch, to follow the Tomcat release cycle. One problem is being able to obtain PMC votes in timely manner, and we are looking to address this be considering new PMC members. ## Activity Jakarta EE 8 is the last release with code under the javax namespace and Jakarta EE 9, aimed for release this fall, has all code migrated to the jakarta namespace in one large breaking change. Aside from the namespace change, the APIs are unchanged and intentionally identical. TomEE 8.x currently implements Jakarta EE 8 with around 95% passing and some work left to do to completely pass all TCK tests. Since the previous report the project has worked on providing a version of TomEE which uses the jakarta namespace. This has been achieved using using the Eclipse Transformer on the server at build time, and a new TomEE Maven Plugin which uses a novel technique to patch particularly tricky items in upstream libraries that the Eclipse Transformer is unable to handle. This technique allows the project to produce binaries for both the javax and jakarta namespaces from the same codebase, therefore reducing maintenance overhead for the project. The project made TomEE 8.0.3 and 9.0.0-M1 releases available on June 23rd, to co-incide with the Jakarta EE 9 milestone launch. TomEE 9.0.0-M1 passed 92% of the Jakarta EE 9 TCK at the point of release. Work continues on the website rebranding and updating of the technology used. David Jencks has put considerable effort into migrating the website to Antorra, and this is being rolled out. The previous website used the Apache CMS, which is being phased out, so this is a timely update. We're extremely grateful for David's hard work in this area. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 32 committers. - Last committer added was Daniel Dias Dos Santos on June 23rd 2020. ## Releases: - Apache TomEE 9.0.0-M2 on August 7, 2020 - Apache TomEE 8.0.4 on August 7, 2020 - Apache TomEE 7.1.3 on May 26, 2020 - Apache TomEE 7.0.8 on May 26, 2020
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health In last report it was mentioned we had more than doubled contributors in the last 14 months, from around 40 to now 98, however have only added one committer in that same timeframe. Discussion is ongiong on specific candidates with one vote very likely to start any day. Hopefully there will be some more activity in this area. ## Activity Conversation has started on how to handle the javax to jakarta namespace migration. Jakarta EE 8 is the last release with code under the javax namespace and Jakarta EE 9, aimed for release this summer, has all code migrated to the jakarta namespace in one large breaking change. Aside from the namespace change, the APIs are unchanged and intentionally identical. TomEE 8.x currently implements Jakarta EE 8 with around 95% passing and some work left to do to completely pass all TCK tests. Several discussions are ongoing presenting options on when to do the migration, including the potential to use of bytecode transformation to produce a "jakarta" version of TomEE allowing both Jakarta EE 8 and Jakarta EE 9 compliance to be worked on in the same branch. Additional discussion in this area is around which standalone APIs jars we should continue to produce and use. Historically, we've created ALv2 licensed API jars under the Geronimo project due to licensing restrictions of the Oracle produced jars. This is no longer needed as the new license, EPL 2.0 is an approved license. However, some APIs are actually implementations, such as javamail, so they may be continued for technical or industry health reasons. There is also discussion if there are still licensing advantages that may justify the overhead of producing our own API jars across the board. We have seens continued activity in the community, particularly in the area of maintaining Docker images, and re-working the website. Website activity was very strong at the start of the quarter, but quieted down in the second half about the same time COVID-19 began affecting everyone. Hopefully we can get that going again as significant amount of work was done. The community has recently released TomEE 8.0.1 in January, along with parallel releases of TomEE 7.1.2 and TomEE 7.0.7. A vote for TomEE 8.0.2 was put up, however a potential security vulnerability was noticed late last week which may cause the release to be aborted. This will be worked through the proper channels and no further details will be given in this report or publicly till there is a fix. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added was Cesar Hernandez on July 1st 2019. ## Releases: - Apache TomEE 8.0.1 on January 22, 2020 - Apache TomEE 7.1.2 on January 22, 2020 - Apache TomEE 7.0.7 on January 22, 2020
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Our mailing lists are quieter this quarter than the previous quarter. We do, however, anticipate this as the project tends to see an increase in November/December time as contributors enjoy spending some free time over the holiday period contributing to the project, and the volume drops once the holiday period is over. We are seeing greater participation from the PMC in creating board reports, in particular Jonathan Gallimore who created the majority of this report. We hope to see continued collaboration here. There was a slight delay getting enough binding votes on our last round of releases, which is a sign we should put some attention to expanding the PMC. Additionally we've more than doubled contributors in the last 14 months, from around 40 to now 98, however have only added one committer in that same timeframe, which is a sign we should consider being more aggressive granting commit. ## Activity The community has recently released TomEE 8.0.1 in January, along with parallel releases of TomEE 7.1.2 and TomEE 7.0.7. The latest 8.0.1 release fixes compliance issues around JAX-RS, provides some fixes for running with Java 11, removes some outdated and unused dependencies (Xalan and Serializer), and upgrades other dependencies (Tomcat and CXF) to mitigate the latest CVE vulnerabilities in those components, including: CVE-2019-12419: Apache CXF OpenId Connect token service does not properly validate the clientId CVE-2019-12406: Apache CXF does not restrict the number of message attachments CVE-2019-17563: Apache Tomcat Session fixation CVE-2019-12418: Apache Tomcat Local Privilege Escalation TomEE is not yet Jakarta EE 8 compliant, but work continues in this area. The release of Jakarta EE 9 is in progress and set to deliver in the June-August timeframe 2020. This will involve a namespace break from javax to jakarta that will impact not just TomEE but all Apache java projects that implement former-Java EE specifications. We expect a great deal of project-to-project communication on this and it is likely something we should ask projects to report on over the next year. All projects will need to know each other's status and the board should be aware of overall progress and potential project or community impacts. We have seen new activity in the community, particularly in the area of maintaining Docker images, and re-working the website. We're particularly grateful for David Jencks' work on the website, and welcome the collaboration between new contributors Rod Jenkins and Carl Mosca on the mailing list. We continue to support their efforts, and strive to be as welcoming as possible to new contributors. Our community speaks a number of different languages, which has enabled translations of our documentation, particularly around the large library of examples we include with the project. We have seen translations to Portuguese and Spanish, and have a new contributor translating documentation into Russian. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added was Cesar Hernandez on July 1st 2019. ## Releases: - Apache TomEE 8.0.1 on January 22, 2020 - Apache TomEE 7.1.2 on January 22, 2020 - Apache TomEE 7.0.7 on January 22, 2020
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Both the dev@ and user@ mailing lists have seen increased traffic over the last quarter, with messages numbers up 20% and 100% on the two lists respectively compared with the previous quarter. The project tends to see increased activity over the Christmas period with new users and contributors trying the project out for the first time over the holidays. ## Activity The community released TomEE 8.0.0 in September, after 3 milestoned releases. The TomEE 8 branch targets compliance with Jakarta EE 8. Although compliance has not yet been achieved with the Web MicroProfile it is deemed production ready. TomEE 8 runs on both Java SE 8 and Java SE 11. Work continues to achieve full Jakarta EE 8 Web Profile compliance. The community is about to release 7.1.2 and 7.0.7 maintenance releases which provide dependency updates and bug fixes. The dependency updates mitigate CVE issues in upstream components, including Jackson-Databind, Commons-Beanutils and Mojarra: CVE-2019-17091 (XSS in Mojarra) CVE-2019-13990 (XXE in Quartz) CVE-2019-10086 (ability for an attacker to access the classloader via the class property in commons-beanutils) Additionally, these will include fixes from commons-daemon for JVM crashes with X86 JVMs on certain X64 Windows servers, and fixes for transaction handling with JMS2. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added was Cesar Hernandez on July 1st 2019. ## Releases: - Apache TomEE 8.0.0 on September 16, 2019
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Activity The community released 7.1.1 and 7.0.6 in June. These 2 releases are very similar, with the key difference being 7.1.1 having a requirement of Java SE 8, and includes a number of MicroProfile specifications. This is a maintenance release which includes dependency updates for Tomcat to mitigate against: CVE-2019-0232 (RCE via CGI Servlet) CVE-2019-0199 (DoS via HTTP/2) CVE-2018-11784 (potential Open redirect attack) These releases also include some key fixes for the CMP support, which is based on dynamically translating CMP entity beans to JPA at deploy time. Specifically the fixes address issues for users providing custom ORM metadata in their applications. Apache TomEE makes use of Commons-Daemon for its Windows service which has seen recent updates to enable applications using UCRT to get correct environment variables. Work on Java 11 continues with intentions of releasing an Apache TomEE 8.0.0 final once complete. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added Roberto Cortez on Thu Sep 6 2018 - Cesar Hernandez invited to become a committer on July 1st 2019. Invitation accepted so we'll proceed with legal requirements and then with the announcement. Cesar started contributing on the mailing list in October 2018. He did some great contributions with examples, documentation. But more important he has been key in terms of enabling other contributors. He is responsive on the mailing list and he's also the most active in there. He's very welcoming and helps reviewing PRs. ## Releases: - Apache TomEE 8.0.0-M3 on May 29, 2019 - Apache TomEE 7.1.1 on June 21, 2019 - Apache TomEE 7.0.6 on June 21, 2019
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health The community did a concentrated push over the holidays to attract and get new contributors engaged. The most active window was mid November to February and in that time the project shattered every measurable record set in the near 20 years of project history. - highest contributors in a 3-month period: 43 (average was 8 in Oct/Nov) - highest spike in commits (previous 2012) - highest sustained volume (previous 2011) - highest dev list: 1326 messages (previous 520 in Sept 2007) Overall result is from mid November till now the project doubled in total contributors, from 32 to 83. Discussions in the PMC in adding some of them as committers are in progress now, including one vote. The PMC acknowledges issues with reports being delivered late to the board and commits to an immediate change of chair should any report be filed late in the next 12 months. Discussions on how to achieve this are underway and include both rotating reporting duties and change of chair. At present rotation of members drafting reports appears to be the preference. ## Activity Four major jumps and areas of focus have taken place in the last few months. The first has been to bring TomEE up from MicroProfile 1.2 support to MicroProfile 2.0 compliance. This work is complete and passing all MicroProfile 2.0 TCK tests. The second area has been a push to add more examples to the project, 26 new examples in total, 15 of those for MicroProfile specifications. The third focus was on the website itself, code that generates the site and basic documentation. The project had been maintaining one set of documentation applicable to all versions. We now have a Tomcat-like system with documentation root per version. The fourth area has been to translate the examples to other languages. 11 translated in total, 6 in Portuguese and 5 in Spanish. The result is the project has experienced a dramatic change, with many new contributors and work that can be done at all levels from any skillset. At this moment there are still 19 PRs in the queue and more showing up regularly. We are very thrilled and proud of everyone. It took 19 years to get 32 contributors and with a major focused effort by everyone simultaneously, we were able to smash 19 years of "new contributor" work in 3 months. It is difficult to sustain and contributions in the last 2 months are lower, but still far greater than the three month period before November. The lesson learned is there is a massive difference in outcome if one or two people push for years vs everyone pushing at once, even if briefly. We hope to do this again in December 2019 on the 20th anniversary of the project, with more committers able to help and hopefully smash some records again. TomEE 8.0.0-M3 was successfully released on May 29th. The community would like to get that codebase to run cleanly on Java 11 and then go for a final TomEE 8.0.0 release. Releases for TomEE 7.0.6 and 7.1.1 are currently under vote. These contain a number of dependency updates and fixes for these maintenance branches which both have a considerable userbase. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added Roberto Cortez on Thu Sep 6 2018 ## Releases: - Apache TomEE 8.0.0-M3 on May 29, 2019
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health The community did a concentrated push over the holidays to attract and get new contributors engaged. The most active window was mid November to February and in that time the project shattered every measurable record set in the near 20 years of project history. - highest contributors in a 3-month period: 43 (average was 8 in Oct/Nov) - highest spike in commits (previous 2012) - highest sustained volume (previous 2011) - highest dev list: 1326 messages (previous 520 in Sept 2007) Overall result is from mid November till now the project doubled in total contributors, from 32 to 83. Discussions in the PMC in adding some of them as committers are in progress now, including one vote. ## Activity Four major jumps and areas of focus have taken place in the last few months. The first has been to bring TomEE up from MicroProfile 1.2 support to MicroProfile 2.0 compliance. This work is complete and passing all MicroProfile 2.0 TCK tests. The second area has been a push to add more examples to the project, 26 new examples in total, 15 of those for MicroProfile specifications. The third focus was on the website itself, code that generates the site and basic documentation. The project had been maintaining one set of documentation applicable to all versions. We now have a Tomcat-like system with documentation root per version. The fourth area has been to translate the examples to other languages. 11 translated in total, 6 in Portuguese and 5 in Spanish. The result is the project has experienced a dramatic change, with many new contributors and work that can be done at all levels from any skillset. At this moment there are still 29 PRs in the queue and more showing up regularly. We are very thrilled and proud of everyone. It took 19 years to get 32 contributors and with a major focused effort by everyone simultaneously, we were able to smash 19 years of "new contributor" work in 3 months. It is difficult to sustain and contributions in the last 2 months are lower, but still far greater than the three month period before November. The lesson learned is there is a massive difference in outcome if one or two people push for years vs everyone pushing at once, even if briefly. We hope to do this again in December 2019 on the 20th anniversary of the project, with more committers able to help and hopefully smash some records again. Work on a TomEE 8.0.0-M3 release is in progress. The community would like to get that codebase to run cleanly on Java 11 and then go for a final TomEE 8.0.0 release. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added Roberto Cortez on Thu Sep 6 2018 ## Releases: - Apache TomEE 8.0.0-M2 on Jan 29, 2018
@Craig: start thread on changing reporting deadline
@Rich: propose new PMC chair due to consistently late reports
This is does not substitute for a board report and we will report next month. There was an ask by the Board for projects to indicate if they would like to use the official Jakarta EE logo once certified. That was discussed and all responses were a yes[1]. Short status of the project is that we've had the best quarter in the project history, shattering previous records on mailing lists communication, commits and new contributors by wide margins. There were over 40 new faces committing their first commit between December and January and we still see a new face weekly. This status is far too amazing to slip in at the last minute, which is why we'll be reporting next month, but we are quite proud of the massive turnaround. [1] https://lists.apache.org/thread.html/93a8d4672c9bcf24c66d863ab7995fa0f0da22f2a7051c74e5da68eb@%3Cdev.tomee.apache.org%3E
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Activity Activity has started to climb on the project with work on adding more MicroProfile compliance into TomEE. MicroProfile JWT was added as discussed in the last two board reports and was the only support for those periods. On Sep 7th the project released a new branch of TomEE, called 7.1, which is TomEE 7 + MicroProfile 1.x on Java 8. This release adds MicroProfile Config and MicroProfile FaultTolerance, both using the Geronimo implementations. The master branch switched from TomEE 7 to the future TomEE 8 and a milestone release of TomEE 8 was completed Oct 19th. The release contains Java EE 8 work which had been ongoing for a long period of time, plus MicroProfile Health Check, MicroProfile Metrics, MicroProfile Rest Client and MicroProfile Open API bringing the total number of MicroProfile specifications supported to 7. The Geronimo implementations were used for all these integrations. A maintenance release of TomEE 7.0.5 was completed July 24th and consists of bug fixes, minor dependency upgrades and patched security vulnerabilities. Nominated by Mark Struberg, the project voted in new committer Roberto Cortez on Sep 6th for his contributions to the project's MicroProfile efforts and releases. Discussions on other new potential committers are in progress, also started by Mark. Committer Jonathan Fisher who had been voted in last year, but never completed his CLA and account has now gone through the process and officially made his first commit this September. He's remained active since which has been very good for the project. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 - Romain Manni-Bucau stepped down from PMC Aug 13 2018 ## Committer base changes: - Currently 31 committers. - Last two committers added - Jonathan S Fisher on Wed Nov 1 2017 - Roberto Cortez on Thu Sep 6 2018 ## Releases: - Apache TomEE 7.0.5 on Jul 24, 2018 - Apache TomEE 7.1.0 on Sep 7, 2018 - Apache TomEE 8.0.0-M1 on Oct 19, 2018
No report was submitted.
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health Having spiked in the following due to the reported MicroProfile conflict, developer mailing list communication has settled into a more calm pace. Previous Quarter: - Jan, 42 - Feb, 202 - Mar, 212 This Quarter: - Apr 120 - May 70 - Jun 68 - Jul 80 (so far) ## Activity Merging of the MicroProfile JWT code into TomEE did eventually occur and lives in the TomEE 8 branch. No releases of TomEE 8 have occurred yet, though discussion of when to release that branch has started. Discussion on backporting MicroProfiles to a potential TomEE 7.1 based on Java 8 also has been discussed. There was some support for such a branch, though some thought after the coming TomEE 7.0.5 would be ideal. Efforts to release TomEE 7.0.5 are nearing completion, two votes already been attempted, the second still in progress. The release includes significantly greater compatibility with Java 9 and upgrades of 6 of the major libraries such as Tomcat, CXF, OpenWebBeans and OpenJPA. Support for Java 10 and 11 is still early stages. How the project will handle the faster Java release cycle in a general sense is unknown. TomEE itself has tended to have 6-8 month release cycles, so some adjustment in terms of speed is likely necessary in order to keep up. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 30 committers. - Last two committers added - Svetlin Zarev on Tue Oct 24 2017 - Jonathan S Fisher on Wed Nov 1 2017 ## Releases: - Apache TomEE 1.7.5 on Oct 24, 2017 - Apache TomEE 7.0.4 on Oct 10, 2017
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Issues The community had a situation similar to the previously reported June 27th incident that spawned the "Suffocating development environment" [1] thread. The subject matter was different, but the dynamics and people involved were largely the same with a commit that caused immediate harsh feedback and was immediately reverted. On February 2nd a discussion was started on potentially implementing MicroProfile JWT in TomEE, which started some at first healthy discussion on where this should go. There was a perspective that this has come up before, is yet unresolved and should be discussed. There was also the perspective that all code that implements the MicroProfile brand should belong to Geronimo and TomEE can use them, but never create them. As well that Geronimo is the proper place for a reusable components under the Java EE umbrella. On February 12 a commit came in [2] during this discussion, was perceived as attempting to circumvent the conversation, infringe on Geronimo's territory, and generated some immediately harsh responses [3][4]. The committer reverted his own commit and sent an email largely with the tone "I quit this project" [5]. A wider discussion was had on the incident [6] and some apologies were made for jumping to conclusions, however the underlying belief that Geronimo is the proper owner of the MicroProfile at Apache remains. In the last 12 months to date, only 3 people have committed to Geronimo, 2 of them are TomEE committers. There are no evildoers in any of this, but the overlap does add to the complexity of the issue and results in most of the discussion naturally taking place on the TomEE lists. ## Health Developer mailing list activity spiked up significantly due to the above discussion. Activity of any kind is a good thing as the lists have been generally quiet. Here are the stats from this reporting period vs the same period last year: 2017 - Jan, 38 - Feb, 39 - Mar, 60 2018 - Jan, 42 - Feb, 202 - Feb, 212 While people are no agreeing, they are talking which is a good step forward. As reported in December, commits had been dominated by largely one person for the first six months of 2017, but were dramatically transformed in the six months after the June 27th 2017 triple-commit-and-revert incident. So while the incident in this report may sound negative, it's my belief this is another step in the project regaining balance and growing. I suspect as before in six months time we'll see a major improvement that can be traced back to this event. ## Activity Implementation of the MicroProfile JWT specification was the major activity. The code allows for the validation of RSA signed JSon Web Tokens in TomEE sent over the 'Authorization' header of incoming HTTP requests. A PR was created consisting of a handful of integration changes and 19 new java files that was extensively reviewed by two others, one of whom is a new contributor. Due to the unclear stance of this subject in general, a vote was held on if the code should be merged. Results were 11 +1s, 1 0 and 1 -1. 6 were binding and 7 came from community members, which is also encouraging as voter turnout has been low. After discussion on the list and with the board, it was determined the -1 issues on the grounds the code should live in Geronimo is not a binding technical veto. A separate, non-technical vote, was held to determine if the project had desire to make the reusable library that seems to be desired. That vote concluded with 6 +1s, 1 +0 and 2 -1s. Both -1s were on the grounds the work should be done in Geronimo. No further work has been done yet. Work on Java 9 and 10 support has started in both the Apache TomEE 1.7.x and 7.0.x branches. Code dontations of Sheldon and Chatterbox, \ mentioned in the December report, have completed. Releases of that code have not yet been made. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 30 committers. - Last two committers added - Svetlin Zarev on Tue Oct 24 2017 - Jonathan S Fisher on Wed Nov 1 2017 ## Releases: - Apache TomEE 1.7.5 on Oct 24, 2017 - Apache TomEE 7.0.4 on Oct 10, 2017 [1] https://lists.apache.org/thread.html/1306bfc0bb78ef47517db6e3866bb750a72458796f9895545dc39cd6@%3Cdev.tomee.apache.org%3E [2] https://lists.apache.org/thread.html/8fe6bc10edb0ba82da1082fa8a4285d754630efd8980e6f044a8465f@%3Ccommits.tomee.apache.org%3E [3] https://lists.apache.org/thread.html/b60d0b98b9fc70361e760bba4ba5177d95010aa32409d1f9fe301c40@%3Cdev.tomee.apache.org%3E [4] https://lists.apache.org/thread.html/70aea236ef6fe414ae243ab1c1887040aff607f8c09704dcf02fb513@%3Cdev.tomee.apache.org%3E [5] https://lists.apache.org/thread.html/9c316ebb0e652a89c1d7a762e38b8eed887ae6f4f3226ea35ab076b6@%3Cdev.tomee.apache.org%3E [6] https://lists.apache.org/thread.html/33f9553894f4d192f50e6d9c3bf67c82c3a93795a7b4e1543f6f67b5@%3Cdev.tomee.apache.org%3E
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Activity: Last Board Report was on Dec 20th, 2017 and due to holidays there is not much activity to report, hence this report is brief. A reminder to the Board, the project is taking focused efforts to increase activity and enable potential committers. In the few days of the new year we are seeing familiar faces who are not yet committers return with a few PRs. In the last week the PMC has started discussion on a potential committer. Both of which are good signs of a gradual incline in activity. TomEE 7 remains the most active branch with fixes periodically going to TomEE 1.7.x. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 30 committers. - 2 new committers added in the last 3 months - Svetlin Zarev on Tue Oct 24 2017 - Jonathan S Fisher on Wed Nov 1 2017
## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Issues: The previous report noted the disagreement between committers on a thread "Suffocating development environment" [1] which involved one person reverting another person's commits three times in a row in the span of 50 minutes. Person insults and antagonism ensued on both sides in that time. The community had several open discussions and the overall situation turned into a positive catalyst. Switching to a RTC workflow was discussed for several weeks, but ultimately the CTR flow has remained. It is encouraging to see more discussion taking place on the dev@ list about recent commits and proposed patches. We are continuing to monitor this. ## Health report: Since the incident on June 27th and subsequent open community discussion, it appears "the fog has cleared" and we have seen a shift in the project. We have seen three measurable changes. 1. Commit diversity improved greatly. Here are the stats from master as reported by Github. Names left off to protect the innocent. Each line represents a contributor. January 1st to June 27th - 127 commits 7,716 ++ 2,519 -- - 7 commits 438 ++ 376 -- - 5 commits 92 ++ 62 -- - 1 commit 42 ++ 9 -- - 1 commit 23 ++ 14 -- - 1 commit 8 ++ 5 -- - 1 commit 1 ++ 1 -- - 1 commit 110 ++ 3 -- June 28th to Dec 14th - 29 commits 2,148 ++ 940 -- - 26 commits 27,065 ++ 252 -- - 22 commits 698 ++ 487 -- - 17 commits 804 ++ 182 -- - 12 commits 257 ++ 24 -- - 10 commits 93 ++ 38 -- - 4 commits 70 ++ 21 -- 2. New committers. After diversity increased, new committer votes shortly followed. Two new committers have been voted in in the last quarter. More have been discussed. We continue to try to be more welcoming and nurturing to new contributors. Potential new contributor Matthew Broadhead has stepped in to try and help provide some patches around JSTL, and we are keen to help him with his contribution. 3. Code donation. Discussion and subsequent vote has taken place to donate two subprojects to TomEE. Both are Java EE Connectors, one adds an SSH shell for logging into the java process and executing commands, the other provides means to integrate with external systems like Gmail, Slack and Twitter. ## Activity: Mark Struberg has started a TomEE 8 branch to support Java EE 8, and progress is being made with this. Master and 1.7.x continue to see maintenance patches, with some key fixes coming in around connector support and application resource classloading. Project dependencies continue to be upgraded to ensure TomEE has the latest fixes in libraries it uses. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 30 committers. - 2 new committers added in the last 3 months - Svetlin Zarev on Tue Oct 24 2017 - Jonathan S Fisher on Wed Nov 1 2017 Thank you to Andy Gumbrecht for co-ordinating these votes. ## Releases: - Last release was 7.0.4 on Sep 26 2017 and 1.7.5 on Oct 24 2017. ## JIRA activity: - 33 JIRA tickets created in the last 3 months - 17 JIRA tickets closed/resolved in the last 3 months [1] http://tomee-openejb.979440.n4.nabble.com/Suffocating-development-environment-td4681969.html
No report was submitted.
No report was submitted.
## Description:
Apache TomEE delivers enterprise application containers and services
based on, but not limited to the Enterprise JavaBeans Specification
and Java Enterprise Edition Specifications.
## Issues:
As reported to the board there was a disagreement between two committers on an
update to the documentation section of the TomEE website late on June 27. The
issue involved a commit which was applied by one person then reverted by the
other within minutes. This happened a total of 3 times in quick succession
over the course of 50 minutes. During this time little discussion reached the
mailing list. Afterwards a "Suffocating development environment" thread [1]
was started on the dev@ mailing list which gave the opinion this was not a
one-time incident, but indicative of the tone of the project as of late.
The discussion of the issue has been very healthy, taking place both on the
public dev list and private list. No parties continued any negative behavior
and discussion did not take the form of stubborn and unyielding debate you
often see in situations like this. While the issues raised in the original
"Suffocating development environment" email are not completely resolved, it is
clear everyone truly wants what is best for the community and open to changes.
This has revived the thread I reported on in January on potentially adopting
review-then-commit (RTC) for a trial period. Discussions continue with regard
to RTC, as yet no vote has taken place or a decision been made.
One challenge the project currently has is contributions coming in via GitHub
pull requests, with the potential for the discussion to happen on the PR as
opposed to on the mailing list. Between Github PR comments and JIRA Issue
comments, there are ample options for draining the dev list of activity. How
the dev list should be used with these systems and how they fit overall is
being discussed as part of RTC, but no changes have been voted on or made.
Though not vote has taken place, some contributors have started using the
discussed RTC format to submit their PRs to the dev list for review. Dev list
discussion overall has shown an increase in the last two weeks.
We will continue to report on the matter and will be carefully tracking any
reverts or other stats we can use to gauge the general tone of the project.
## Activity:
The majority of work on the project is maintenance and bug fixes, although
this is likely to change with Java EE 8 being finalized later in the year. In
addition we have seen a number of fixes being backported to the 1.7.x branch,
supporting Java EE 6.
## Health report:
We have continued to see contributions from Svetlin Zarev, and also
contributions from new contributors Ivan Junckes Filho and Otavio Santana. In
particular we're seeing interest in improving our documentation, which is most
welcome. We are actively trying to be more welcoming and nurturing to these
contributors with a view of growing our community.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015
## Committer base changes:
- Currently 28 committers.
- No new committers added in the last 3 months
- Last committer addition was Mark Struberg at Thu Dec 12 2013
## Releases:
- Last release was 7.0.3 on Mar 07 2017
## Mailing list activity:
There has been a surge in activity on dev@ as a result which is very
encouraging. (July mailing list stats on dev@ are significantly up on the
previous 3 months). In particular we are seeing more discussion around new
functionality and bug fixes on the list as well as more review. This is likely
due to more activity since the "Suffocating development environment" thread
[1].
- users@tomee.apache.org:
- 323 subscribers (up 0 in the last 3 months):
- 331 emails sent to list (488 in previous quarter)
- dev@tomee.apache.org:
- 204 subscribers (up 0 in the last 3 months):
- 399 emails sent to list (171 in previous quarter)
- notifications@tomee.apache.org:
- 7 subscribers (up 0 in the last 3 months):
- 34 emails sent to list (14 in previous quarter)
- tck@tomee.apache.org:
- 15 subscribers (up 0 in the last 3 months)
## JIRA activity:
- 63 JIRA tickets created in the last 3 months
- 40 JIRA tickets closed/resolved in the last 3 months
[1] https://lists.apache.org/thread.html/7ebb2bc5b64115be1ddf35914943cb649378e828594689bfc76b2a71@%3Cdev.tomee.apache.org%3E
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. As commented in the last board report, the project has work to do on attracting new committers. Over the last quarter user and dev emails were roughly 100-180 and 40-60 per month respectively, website traffic ~50k per month, roughly 436 forks on github and 10 pull requests (PRs) from non-committers. There appear to be the right ingredients for healthier committer base. Discussion on potentially using a RTC model on a trial basis to flush out good communication and participation had mixed feedback and was not conclusive. Most achievable contributor discussions appear to be in the area of documentation. Turning this into action and PRs seems to be where things fall short. With the approach to PRs, many being commented as applied but still remaining open in Github, it is difficult to see and track where contributions do go. There is some discussion needed here. If the board is aware of any good role models for ASF projects leveraging Github PRs, I’d like to investigate. Last release was 7.0.3 on 2017-03-13. Last committer was added November 2015. Last PMC addition, 4 new members on 2015-08-11.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. As commented in the last board report, the project has work to do on attracting new committers. In the last year an overwhelming majority of commits have come from one person. That said, since last board report in September we’ve seen at least 7 non-committers submit a total of 21 pull requests through the Github integration. Some of those successfully applied, many not and one deleted by accident. Wearing my PMC Chair hat my concern on adding new committers in the current climate is there is not enough discussion to match the level of commit activity. In particular, only 1 of the 7 faces have posted to the mailing list. Recalling Ken Coar’s decision to go RTC in Geronimo, I’ve put that course of action up for discussion in the PMC. Though Ken did it for entirely different reasons, the benefits it brought the community could be particularly useful here. Work on a new website reached a point where the community was overall happy and voted to go live with it. The new site is largely a new landing page, a few new quick-starts and links to many pages of the old site which has a slightly different look and feel. Contribution to the new site is a definitely opportunity for those looking to get started. Last release was 7.0.2 on 2016-11-11. Last committer was added November 2015. Last PMC addition, 4 new members on 2015-08-11.
The community appears to be stagnant even though there is activity e.g. in conferences.
No report was submitted.
@Jim: pursue a report for TomEE
No report was submitted.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. The project as decided to release Apache TomEE 7 as final despite issues around lack of TCK access. After a series of votes the Apache TomEE 7.0.0 was released at the end of May. Community feedback has been on the whole positive, though some still stay on 1.7.x hoping for some possibility for a certified TomEE 7. There have now been 5 releases in the 7.x stream, the project having released three milestones previously and a patch release 7.0.1 on June 27th one month following the release. Work on a new website has been ongoing passively in the background. This is aimed to replace the perl/svn/markdown system Joe Schaefer wrote and will likely get some attention now that 7.x is out. A new security vulnerability was filed in May following our release of the fix for ZDI-15-638. A supporting video was supplied demonstrating the issue, but did however also show the reporter changed their configuration to explicitly allow the attack — disabling the out-of-box restrictions that prevent ZDI-15-638 from working. The project sees no action is needed and has notified security@. The project still has room for improvement on attracting new committers. Interest people do show up, however general theme is lack of time to properly mentor contributors in what is usually their first open source project. Last release was 7.0.1 on 2016-06-27. 7.0.0 was released on 2016-05-29. Last committer was added November 2015. Last PMC addition, 4 new members on 2015-08-11.
No report was submitted.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Work on addressing ZDI-15-638 completed and fixes released for both the TomEE 1.7.x and 7.0.x code lines. The fix involves a new feature that limits the classes that can be used in a serialization context. Documentation for the fix was contributed by a mix of committers and contributors through the old perl/svn/markdown system Joe Schaefer wrote. Some discussion has started about possibly newer alternatives for accepting documentation contributions, including github pull requests. Major initiatives requiring community attention. Lack of resources remains an issue for the community which needs improvement. Work on TomEE 7 remains in milestone form primarily due to lack of Java EE 7 TCK. Despite the lack of a Java EE 7 TCK, there are users who do not care about certification and simply need a stable release. Some decision will need to be made here as it doesn’t appear likely the community will ever get a TCK. Additionally, OpenJPA’s lack of progress affects TomEE indirectly as it is the default JPA implementation. The user list, however, continues to be active with most queries resolved quickly. User mailing list traffic: - 179 messages / January - 129 messages / February - 174 messages / March Average dev mailing list traffic: - 35 messages / January - 38 messages / February - 52 messages / March Last releases are: - 1.7.4 on March 4th - 7.0.0.M2 on Feb 28th - 7.0.0.M2 on March 6th Last release was 1.7.4 on 2016-03-04 and 7.0.0-M3 on 2016-03-06. Last committer was added November 2015. Last PMC addition, 4 new members on 2015-08-11.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. The user list continues to be active with most queries resolved quickly. Average user mailing list traffic: 230 messages / month Dev mailing list traffic: - 39 messages for October - 138 messages for November - 69 messages for December We seem to continuously see new users reaching out to us. Thanks to a community push and the joined effort, we dedicated the end of November and the beginning of December on the TomEE 1.7.3 release which is Java EE 6 certified. This is a maintenance release with a couple of important fixes the community was looking for. Most of the work has been dedicated to produce the first Java EE 7 TomEE release, namely the 7.0.0-M1. This release has been anticipated for some months and is a big step forward for the community. Lack the Java EE 7 TCK continues to be painful disadvantage, one which will be slightly more highlighted now that we are shipping Java EE 7 targeted releases and questions of compliance increase. Overall the project is lacking in resources and has been highlighted in late board reports, delays in getting security issues resolved and the long lag in the first TomEE 7 milestone release. Action has been taken as previously reported to address issues of late board reports. The PMC is more actively discussing the open security issue, ZDI-15-638. As well serious discussions are underway on how to attract more committers. Expect some resolutions in this area as a deliverable to the board in future reports. The community is aware and desires better. Specifically for ZDI-15-638, the PMC expects resolution in the next two weeks with release in both 1.7.x and 7.x shortly after. Last release was 1.7.3 on 2015-12-09 and 7.0.0-M1 on 2015-12-10. Last committer was added November 2015. Last PMC addition, 4 new members on 2015-08-11.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. The user list continues to be active with most queries resolved quickly. We welcome new contributor Daniel Cuhna who has submitted patches via GitHub pull requests, and hope he will continue to contribute to the the project. We continue to encourage new contributors to join and support them as much as we can. The development pace of the project continues to be slow and focused on maintenance. TomEE 1.7.2 (released in May) continues to be the most popular download. Work has been progressing on TomEE 7 to implement the Java EE 7 web profile, but continues to be hindered by the lack of a Java EE 7 TCK. The community is working towards a maintenance release of the 1.7.x codebase (1.7.3) which provides some key bug fixes and is looking to provide a first milestone release of TomEE 7, which has been eagerly awaited by the community for some time, but delayed due to bugs identified with the integration with upstream libraries. Both are planned for the next few weeks. The PMC has taken action to address repeatedly late board reports. A private SVN repo was requested where board reports can be placed and contributed to by all the PMC. A special thank you to Jonathan Gallimore for being a primary contributor to this report. Last release was 1.7.2 on 2015-05-22. Last committer was added November 2013. Last PMC addition, 4 new members on 2015-08-11.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. A repeat discussion has been around what the next major version number for TomEE should be. After a vote the community has decided to rename TomEE 2.0 to TomEE 7 to more clearly align with the Java EE 7 specification. I have pointed out the many disadvantages of this such as being locked into a major version number that we don’t control, only changes every 4 years and doesn’t reflect our own innovations and major changes. While not my personal preference, the overwhelming majority prefers the 7 version number and I am quite proud to see the community has the health to peacefully disagree and move forward — especially when some of them are disagreeing with their employer. This must be encouraged. The project has voted in 4 new members to the PMC; Andy Gumbrecht, Mark Struberg, Romain Manni-Bucau and Thiago Veronezi. Discussion of this took place openly on the dev list with actual voting on the private@ list. Noted in a previous board report that if the community continued to feel more comfortable voting in private, the PMC numbers would have to be increased. This appears to be the case and so the PMC has been expanded. New faces appeared on the project from Pivotal and SAP, both wishing to contribute a buildpack for TomEE to run in their cloud platforms. Faces from WS02 and ManagedCat have started appearing a little more frequently occasionally joining dev or user list conversations. Contributions are not there yet, but it is promising and the timing is very good. As of September Tomitribe employs the majority of active committers the project has had over the last 5 years. While all members of the community act as individuals, we all know how important it is to have diversity in employers. It would be a milestone to see the project graduate to Tomcat or HTTPd levels of diversity in both individual and employers. This will also be heavily encouraged. While many positive community changes have happened in the previous 5 months since the last board report, the development pace of the project continues to be slow and focused on maintenance. TomEE 1.7.2 was released in May and is now the primary download for most users. Work on TomEE 7 continues to be hindered by the lack of a Java EE 7 TCK. Cameron’s departure from Oracle, could likely be a sign the community will have to stand purely on it’s own innovations. Last release was 1.7.2 on 2015-05-22. Last committer was added November 2013. Last PMC addition, 4 new members on 2015-08-11.
No report was submitted.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Work on TomEE 2.0 remains slow as noted in the February report. Work towards Java EE 7 compliance is understandably difficult and the community is running out of threads to pull on Java EE 7 without a TCK. The TomEE 1.7.x branch remains the center of the day-to-day. Some fixes and minor enhancements are in progress for a future 1.7.2 release likely to come out in this quarter. The stability and gradual movement of the 1.7.x branch seems to be carrying the project forward. Particular new developments in the 1.7.x branch involve the addition of a enhanced command-line library for managing TomEE. It was added externally by some non-committers in a Github project, however discussion has moved to the Apache lists and we'll see if we can get the ideas added and potentially some good new committers as well. There has been some discussion in the community around Apache rules for including snapshot downloads links in the website. There is a page[1] that includes them and features a red disclaimer. Links to this page were recently removed by request. Looking at the Google Analytics project for the last 12 months, exactly 0.09% of the website traffic ever saw the snapshot page. This would seem to me be in an acceptable range. With my VP hat on -- and barring board disapproval -- I'm inclined to rule it responsible use and allow links to be restored as it does appear to enable the right people yet still discourage the general public. Last release was 1.7.1 on 2014-09-15. Last committer was added November 2013. Last PMC addition was 2010-08-26. [1] http://tomee.apache.org/download/tomee-2.0.0-snapshot.html
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Work on TomEE 2.0 has slowed. The 2.x branch now passes the Java EE 6 Web Profile TCK, however work towards Java EE 7 compliance is understandably difficult. The 2.x branch now passes the CDI 1.2 TCK, which is openly available from RedHat. Some work has been done to integrate ActiveMQ 6 into TomEE 2.x. The community is running out of threads to pull on Java EE 7 without a TCK. Meanwhile the TomEE 1.7.x branch remains the center of the day-to-day. A version 1.7.2 is likely to come out in the next quarter. This will be the first release since the project switched from SVN to Git. The change in SCM went fairly smooth despite the kind of "the rails are off" discussions that arise from being now largely unrestricted. The community is trying out various Git flows. This will probably continue for quite a while before the dust truly settles. Website traffic still slowly increasing and at an overall high of around 72k visits/month. User list traffic stable compared to the last 6 months, but down from last year. This would seem to be indicative of a community in stabilizing/maintenance mode, but growing popularity. Last release was 1.7.1 on 2014-09-15. Last committer was added November 2013. Last PMC addition was 2010-08-26.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Major news includes the conversion of the project from svn to git. Motivation includes the number of pull requests has grown and forks of the git mirror in Github are up to nearly 200. Most of the "new blood" showing up on the are more comfortable with git. With new faces arriving more and more frequently, we're hoping this helps them contribute and helps us track and incorporate those contributions. Time to start having some talks about adding contributors. The project was given a Duke's Choice award from Oracle this JavaOne and a Geek Choice award from ZeroTurnaround. The growing popularity is a strong contributing factor for the new faces. Apache TomEE 1.7.1 was released this September and is a maintenance release for the Java EE 6 codebase. Work on Java EE 7 in TomEE 2.0 continues moving forward. Hope of getting a Java EE 7 TCK still remains. Last release was 1.7.1 on 2014-09-15. Last committer was added November 2013. Last PMC addition was 2010-08-26.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Major project news is the release of TomEE 1.7.0, which was a very long release cycle an large community effort. First branch was July 1st. First vote was July 13th. One month late was the final passing vote. Thank you notes have been pouring in from users, which is fantastic to see. As usual releases from some of our sister projects were required, including OpenWebBeans and OpenJPA. Requests for those releases started in April. We were able to get a release from OpenWebBeans, but not OpenJPA. This happens and we dealt with it by creating or own OpenJPA 2.4.0-nonfinal release. With only 70 commits on trunk in the last 12 months it's clear the community needs significant help. I've engaged the private list to see how we can help. I mention to the board for purposes of transparency as most board reports sound "business as usual" even when the community is slowly shrinking. Self awareness can be hard. TomEE trunk is now dedicated to TomEE 2.0 and Java EE 7 efforts, again to much fanfare. Resources for implementing Java EE 7 will be extremely tight. Adding new committers and focusing community on passing the Java EE 7 TCK, assuming we get one, will be key. I couldn't predict when we might reach certification even with a TCK. Both Tomcat and TomEE were jointly awarded a "Geeks Choice" award from ZeroTurnaround in a local developer pool. This is a nice confirmation of interest from outside Apache. The banner is now displayed on our website front-page. Last release was 1.7.0 on 2014-08-15. Last committer was added November 2013. Last PMC addition was 2010-08-26.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Significant work was done by the project around formalizing desired policy and documentation for security vulnerabilities. To date all of these have been in sibling projects and not in TomEE or OpenEJB specifically. Regardless users have come to expect TomEE have the same responsiveness, specifically for Tomcat vulnerabilities. This work was done actually a month or so before the Heartbleed incident fortunately enough and the project was able to turn that around very quickly after it was released by Tomcat. This quarter saw two security vulnerability releases, TomEE 1.6.0.1 and 1.6.0.2, each about a month apart. Note frequent releases have been a concern in several prior board reports. It's very good to see a marked improvement in this area. Primary focus on trunk has revolved around supporting Java 8, which has required patches and releases to a handful projects. Trunk will be released as TomEE 1.7.0, hopefully within a month. After this release the community plans to change trunk to TomEE 2.0 and begin work towards Java EE 7 (with or with out a TCK -- hopefully with). Community activity has increased since last quarter. Patches have been committed from around six new faces hailing from various parts of the world. Most having seen some presentation or been a user for a while and encouraged by seeing others make the jump and start committing. I'll note once again, my personal observations are individual committers tend to come in at least groups of two. Seeing others ask the basic questions on how to contribute often has a way of emboldening others to do the same -- when they do as well, it tends to snowball. Good to see the right "ingredients" in play for some community growth. Conversation about growing the PMC and legal oversight was pushed to the dev list again. Good opportunity to teach how Apache works as a legal entity for the new people getting involved and clarify for existing committers. I'd expect to see some additions there. Last release was 1.6.0.2 on 2014-05-12. Last committer was added November 2013. Last PMC addition was 2010-08-26.
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Apache TomEE 1.6.0 was delivered mid November to a very appreciative community. Major thanks to the cooperation of both OpenWebBeans and OpenJPA for preparing and releasing their cooperation getting their respective 1.2.1 and 2.3.0 releases out the door. The release was an effort spanning multiple communities. Positive note for the release was we had the most votes from non-committers we've ever seen on any TomEE or OpenEJB release. There were several revotes, but it ended up being just under the number of committer votes. Both a sign of the very long delay (the bad) from the previous release and people transitioning involvement from the user list to the dev list (the good). The community remains with the best intentions to release more frequently. Lack of enough activity to split attention between multiple branches is one factor. With this in mind trunk remains at the stable 1.6.x branch with an intent to deliver at least one point release before shifting to another major feature version. Longer term, bringing in more committers will be key. The project voted in Mark Struberg as a committer in November. Mark has been instrumental in all release work in the last year with his involvement as a committer on both OpenWebBeans and OpenJPA which are the most frequently patched and most common SNAPSHOT dependencies of TomEE. Last release was 1.6.0 in November 2013. Last committer was added November 2012. Last PMC addition was 2010-08-26.
AI: Bertrand: inconsistency with last committer.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Demand for the 1.6.0 is quite high with 2 or 3 requests a week. Development of features has slowed, bug fixes still remain quite high and the codebase is nearing release quality. The last remaining details are waiting for the dependencies in snapshot form to be released. Most snapshot dependencies have been resolved to their related released versions in the last two months. The last remaining dependency is OpenJPA 2.3.0 snapshot, which should hopefully be ready for release at some point soon. Work on an administration console has revived, which is a frequently requested feature. The new effort is more or less a "from scratch" effort and shows great promise. Exploratory work has also started in the community on adding support for TomEE in Microsoft Azure. Java EE 7 is still highly demanded. I spoke with a few people at Oracle while at JavaOne and expressed some of the concerns about communities retaining control of projects and more. At individual levels, everyone I spoke with is very open to finding common ground and willing to compromise. My personal take: the will is definitely there. Last release was 1.5.2 in April. Last committer was added 2011-12-14. Last PMC addition was 2010-08-26.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. All development focus is on the coming 1.6.0 codebase and work towards that release will likely start soon. Heavy amounts of user traffic has kept the user list very very active and the dev list somewhat quieter than usual keeping up under the weight of user traffic. Some new faces have started to show up on the dev list and hopefully we can pull some of those people across. Documentation contributions seem to be the largest form of new contributions, though often just one-time tweaks. Demand for Java EE 7, expectation that this will be TomEE 2.x, and requests for a timeline has spread through the user list. We can stave off being specific for a while, but we will need access to a Java EE 7 TCK soon. This is a top priority for our users. Based on several years of Geronimo certification cycles and the TomEE Java EE 6 certification, it will likely take 10 to 15 months post getting access to the Java EE 7 TCK before we can ship a final certified 2.x release. Speculative implementation based only on specification text often proves un-useful as critical details uncovered by the TCK often require reworking implementation work at the core. It is often a matter of doing double work to pull out the previous attempt, then putting in the new attempt. Ideally we'd have the TCK and some progress to show before the end of the year at the latest.
AI: Sam to send message
No report was submitted.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. One of our more quiet periods. Focus continues on more frequent releases and driving stability into the codebase. TomEE 1.5.2 and OpenEJB 4.5.2 were released early April. Work has started on releasing a beta of the current trunk, 1.6.0. The 1.5.2 work has been focused on stability, as mentioned. The coming 1.6.0 has a number of key performance improvements that show big payoff on smaller and slower systems like the Raspberry PI. There is intention of passing the Java EE 6 Web Profile TCK on the Raspberry PI and announcing that in the 1.6.0 release, when that is ready. This may depend on our licensee status. User list traffic spiked up again, March was the second highest month of all time. Contribution to the documentation via the anonymous CMS remains constant. A modest total of 7 contributions came in in the last quarter, which may seem small, but was completely unheard of with Confluence. It's great to see this continue. We've see 2 or 3 "I want to contribute" posts, which is also wonderful and more than normal. The codebase is a big larger now and harder to get into, but fingers crossed we can pull at least one of them into the project.
Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. A rename of the project from OpenEJB to TomEE is mostly complete. The committee-info.txt updated, lists migrated, permission groups renamed, etc. All that remains are minor details. A logo contest was organized and announced late November and has now officially closed as of January 15th. Around 27 logos where submitted. TomEE 1.5.1 and OpenEJB 4.5.1 were released in mid December. The community is very happy to get a stable minor release. This is also a bit of a milestone for the project as the first release of trunk to happen so quickly -- 2 months -- and is a positive trend in the right direction. Most trunk releases have taken 4-6 months. Discussion has started on queuing up another release for the end of January. As can be implied by the stable releases from trunk, the large part of developer activity is focused on digesting and incorporating the overwhelming amount of feedback we're getting which is mostly of the bugfix to improvement variety. As these things go there's a short window till the next major spec round and the community of users and developers is focused on the right thing -- maturing the codebase.
WHEREAS, the Project Management Committee of the Apache OpenEJB Project has chosen by vote to recommend a change of name to Apache TomEE and revision of its charges to include implementation of the Java Enterprise Edition, and WHEREAS, the Board of Directors is receipt of this and deems it to be in the best interests of the Foundation and consistent with the Foundation's purposes; NOW, THEREFORE, BE IT RESOLVED, that the Project Management Committee (PMC), heretofore known as the "Apache OpenEJB Project", shall henceforth be known as the the "Apache TomEE Project", and BE IT FURTHER RESOLVED, that the Apache TomEE Project be and hereby is responsible for enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Special Order 7E, Change the Apache OpenEJB Project Name, was approved by Unanimous Vote of the directors present.
Apache OpenEJB is an enterprise application containers and object distribution services based on, the Enterprise JavaBeans Specification and Java Enterprise Edition Web Profile. A year has passed since "TomEE" was first released last October 2011 at JavaOne. Website traffic is up roughly 150% percent since last September. Mailing list traffic is up 230%. With the clear success of TomEE, the project is currently discussing changing the primary identity from OpenEJB to TomEE. Having them as separate TLPs is a technical impossibility as for all intents and purposes TomEE is OpenEJB. The success has come almost exclusively from certification and rebranding of existing code. The release efforts for TomEE 1.1.0 and OpenEJB 4.5.1 mentioned in last release never resulted in a release due to overwhelming feedback and always having more critical bugs to fix. A release was finalized in October just prior to JavaOne this year in order to keep people off of snapshots. Due to the large volume of fixes, enhancements and features the version was bumped to 1.5.0 and 4.5.0 respectively. A release branch has already been created for 1.5.1 and 4.5.1 with hopes for release candidates in the coming week. Project efforts focus mainly on fixes, documentation, addressing migration issues and keeping up with the high volume of user feedback we are now getting. More frequent releases and documentation have been repeatedly noted by users and developers as major needs of the project. Efforts to further document and create tooling for the release process are starting to show results in the form of greater participation in the release process, which is encouraging. With further efforts, we will hopefully finally realize the desire and demand for more frequent releases.
No report was submitted.
Apache OpenEJB is an enterprise application containers and object distribution services based on, the Enterprise JavaBeans Specification and Java Enterprise Edition Web Profile. Major event for the quarter was the long awaited release of OpenEJB 4.0.0 final and TomEE 1.0.0 final on April 30th. Foundation announcement made with the great might of Sally, as usual. We had the highest website traffic of all time for the following two weeks. Thanks so much to everyone who has helped with that undertaking. Primary activity has been on keeping up with the flood of issues reported and user requests. Feature development around a console for TomEE, ways to improve migration and a new multicast server discovery approach have also been focal points. Effort to release OpenEJB 4.1.0 and TomEE 1.1.0 has just begun and will likely be the focus of the next several weeks. Further effort to "tool" the release process has been undertaken including a tool to create a jira issue with several subtasks. The goal being to better document and spread out release tasks. We might have something to share there at some point. The Infra anonymous edit feature for the CMS has been a boon for the project. The feature coupled with a nice javascript-powered edit button on nearly every page has dramatically improved user contribution to the documentation/website. We've had at least 4 different users contribute to the documentation over the last two weeks or so, which is about 4 times as many as we had with Confluence. One of them as started contributing code. We strongly encourage other projects to add this to their quiver of power tools. Potential concern was raised on running the JavaEE TCK on Amazon-controlled hardware (EC2) [1]. The concern was subsided, but we bring it to the board's attention for maximum transparency as we have done since the start of our EC2 usage. Were we to not use EC2 for TCK testing we would need dedicated hardware for the task. It wouldn't be quite as much as Geronimo, but would be in that ballpark. [1] https://issues.apache.org/jira/browse/INFRA-5044
(OpenEJB)
AI Ross: look into TCK issue with infra.
Apache OpenEJB is an enterprise application containers and object distribution services based on, the Enterprise JavaBeans Specification and Java Enterprise Edition Web Profile. OpenEJB 4.0.0-beta-2 and TomEE 1.0.0-beta-2 were released late January as expected. The releases were well received and a much needed replacement for the "beta-1" set of binaries released and widely announced in October. A typical influx of new faces and questions kept the community busy in the month following beta-2. Primary activity in the last month has been on working towards the long awaited OpenEJB 4.0.0 final and TomEE 1.0.0 final. Updates for the TomEE 1.0.0 include: continued "openejb" -> "tomee" renaming, particularly the console, logging files and config files; more work on the Arquillian Adapters; heavy performance tuning. The release branch has been cut and several preview binaries have been pushed to Nexus in staging. Voting could happen as early as this week. Work on announcements pending (thanks in advance to Sally). Many thanks to OpenJPA, OpenWebBeans, BeanVal, and Geronimo for the releases we needed to prepare for the final OpenEJB/TomEE release. We couldn't have done it without you!
Apache OpenEJB is an enterprise application containers and object distribution services based on, the Enterprise JavaBeans Specification and Java Enterprise Edition Web Profile. Primary activity over the last quarter has been on keeping up with bug fixes and generally supporting the OpenEJB 4.0.0-beta-1 and TomEE 1.0.0-beta-1 release shipped in early. The project switched to the Apache CMS just prior to ApacheCon and developed a new website heavily featuring TomEE. The site itself is still under development and work is still in progress on how to best communicate TomEE and OpenEJB together. The change to the CMS has been incredibly positive and very productive and confluence is no longer in use. Heavy development has been done in the area of OSGi support and integration with Apache Karaf. The effort has been an overlapping with contributions coming from both communities. Contributor, Vishwanath Krishnamurthi, was voted in as a committer and is also a new face at Apache. He's contributed some great things to the infrastructure (twitter bot), documentation and examples. We're very excited to have him in the community and to welcome him into Apache. Work on the OpenEJB 4.0.0-beta-2 and TomEE 1.0.0-beta-2 release has been ongoing for the last two weeks. A second set of binaries are up for a vote currently. Releasing frequently has been a challenge for the project and in efforts to improve that a considerable amount of work has been done to create tooling for automating the release tasks. Hopefully this will bring us closer to the goal of releasing frequently which has been discussed and agreed upon several times, but the weight of the code has thus far kept it from being a reality.
Apache OpenEJB is an enterprise application containers and object distribution services project based on, the Enterprise JavaBeans Specification and Java Enterprise Edition Web Profile. It was a very eventful quarter with the completion of certification work, release, and JavaOne announcement of TomEE, the former "OpenEJB/Tomcat" integration code which has been a major part of OpenEJB for years. Code released October 4th, 2011: - OpenEJB 4.0.0-beta-1 - TomEE 1.0.0-beta-1 - TomEE Plus 1.0.0-beta-1 Certification Steady progress on TCK work was made all through August and September with the hopes of maybe making it in time for a JavaOne certification announcement. First 100% pass completed on the 22nd. Last major bits revolved around @DataSourceDefinition support, CDI integration, global JNDI support and the standard two dozen "picky" things some of which involved patching jars. Release and Announcement Release preparation started shortly after as did work on an announcement. Primary release work involved splitting the TomEE distro into two parts and cleaning up legal files. For certification purposes, any uncertified parts beyond the web profile had to be split into a separate download that could be clearly marked as not certified. Legal work was also quite involved as it had been a year since the trunk code had been released. Typically, releases have taken 2-3 weeks due to discovering issues with LICENSE and NOTICE files of the zips and tar.gz. To aid in the legal screening and speed up release time in a healthy way, a tool was created to make it easier to inspect the zip contents and all NOTICE and LICENSE files in all jars inside said zip. The tool is being moved into the RAT project and will be called "Tentacles." The release announcement was drafted up by Sally with the help of myself and others. The plan was to announce the Thursday of JavaOne, but that date was moved up 2 days when Oracle placed TomEE on the certification page Monday night. By Tuesday morning word had already broken on twitter, some of which had people posting links to snapshots, so the announcement was moved up to Tuesday thanks to some agility on Sally's part and the release binaries were finalized. TomEE was featured prominently at JavaOne in a session on Thursday that week. The session was standing room only and went quite well. I participated in two interviews about TomEE [2][3]. Aside from one of them naming me "project lead", they represent the ASF values nicely. The interviewer's usage of "project lead" usage was an oversight on my part, one which will not slip by uncorrected so easily again. Future public events TomEE will be presented by members of the community in the near future. Jacek Laskowski at Warsjawa 2011, Jonathan Gallimore at JAXLondon in November, and myself at ApacheCon also in November. The community has been sharing all slides from all presentations given this year via the project svn which has been quite nice in helping others reuse the materials for the benefit of the project. Current Activities Immediately post release, work has been focused on completing the Arquillian adapter for TomEE, improving the Embeddable functionality, and refactoring the code to make it clearer what we consider "OpenEJB" and what is "TomEE." The two have been one indistinguishable codebase as the roots of TomEE is simply "the OpenEJB/Tomcat integration" code renamed and certified. Renaming that code TomEE has been a boon in helping people understand what it does in a way they can also communicate to others, but it is a bit of a mess as TomEE is looking like it could easily become the dominant identity. The two, "OpenEJB" and "TomEE", will likely remain as part of the same build and codeline for the foreseeable future, but work as started on giving TomEE more of its own identity in code terms. Much work remains to be done on TomEE Plus, the flavor of TomEE where the uncertified JMS, JAX-RS, JAX-WS and Java EE Connector functionality lives. There is desire to certify this as well, though, that will likely be months off. [1] https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces17 [2] http://www.infoworld.com/d/application-development/apache-tomee-web-stack-gains-approval-175341 [3] http://jaxenter.com/tomee-be-small-be-certified-be-tomcat-38434.html
STABLE 3.2 branch is in the process of being released, currently waiting on the release of snapshots dependencies on other projects. Some users have already started contributing patches to the pre-release 3.2 branch which is a definite sign of pent up demand. With a stronger push hopefully we can see this code released in the next month. TRUNK Push toward Java EE 6 Web Profile certification of the Tomcat integration (TomEE) continues in trunk. Significant progress has been made since last report. Still some heavy lifting yet to be done and that last stretch is usually the hardest. The weakest area was in the CDI integration. That is now in pretty good shape in OpenEJB core and still some work yet to be done in the TomEE side of the CDI integration. JAX-RS support has also been added and is now functional and brought with it an improved CXF integration. The experimental distributed TCK setup on Amazon EC2 with my account seems to have proven useful. While only run occasionally -- couple times a month -- it has been convenient to see overall progress. Though convenient, it still is not getting utilized to any critical capacity. If that changes, we might want to consider a more permanent solution or a setup similar to Geronimo's TCK setup. Regardless of where the TCK is run "all at once", the real bottleneck to forward progress is the number of individuals with the TCK setup on their dev machines. Still only a handful of individuals setup for TCK work. Hopefully we can improve that. COMMUNITY We are pleasantly experiencing a little bubble of new contributor activity with patches coming in from 3 to 4 new faces. Areas range from tooling such as a twitter retweet bot, examples and documentation, to bug fixes. Patches have backlogged as a result. We've re-setup an old script to report unreviewed patches in JIRA, sorted by patch date, and this has helped increase visibility of overlooked/forgotten patches quite a bit. With so many willing contributors, better responsiveness and clearer definition of work to be done will be key ingredients in turning this batch of contributors into committers. There was an OpenEJB/TomEE presence at OSCON this last month. The actual presentation was business as usual, but there was a "Java Standards Annoyances" fishbowl session I participated in just before my session that bore some interesting fruit. Specifically, JCP Chair Patrick Curran attended and was thrown several questions/complaints about TCK transparency from myself, Jeff Genender and others. He detailed several changes in the proposed JSR-38 that would disallow such secrecy and NDAs going forward in the JCP. JavaWorld was there and covered the story[1]. I followed up with him personally after OSCON to ask about immediate relief for the here and now, aka the Java EE 6 TCK NDA requirements, and he implied there might be some willingness to revise that requirement with current licensees. This is something we may want to pursue. Certainly, being able to disclose results would be a big help to OpenEJB, Geronimo and any other projects in the Java EE circle subject to TCK testing. [1] http://www.javaworld.com/community/node/8086
Report missing; will report next month.
STABLE Some branching/version changes were made based on user feedback. Specifically, many users strongly wanted the JPA 2.0 support in the trunk but were getting frustrated with constant trunk change. The 3.1.x codebase is still the primary branch being actively released and supported, yet many users appear to be using trunk primarily for the JPA 2.0 support. To address this demand and get people off of using snapshots, the trunk code was relabeled from 3.2-SNAPSHOT to 4.0.0-SNAPSHOT and a new 3.2 branch was created from the very stable 3.1.x branch. The in-high-demand JPA 2.0 support was then merged from trunk into the new 3.2 branch, is now under test and should be released soon. The 3.2 release will be very popular and treating trunk as a new major version is more "honest" given the changes and goals. TRUNK The trunk code, aimed at Java EE 6 Web Profile certification, has begun to stabilize in many respects. To aid in getting consistent TCK numbers, I've setup a flavor of the Geronimo distributed TCK setup on my Amazon EC2 account as an experiment. Not strictly required as it just runs the TCK using the same commands an individual would use, but given the small size of the community and the fact that most active committers have day jobs, it has potential as a time-saver that could be really cheap for a run or two a week. A significant push was made to round out some sharp corners. The code seems to be in decent enough shape for its first release, likely an alpha or beta. Significant changes have been made recently with regard to OpenEJB-created features that were added to the Java EE 6 set of specifications, but in a way that was slightly different than the way OpenEJB had been doing it. Specifically processing EJBs inside of .war files and processing ejb modules in a plain Java SE vm with an embedded EJB container. Significant other changes and additions include slight overhaul of the Tomcat integration code (TomEE) and experimental Meta Annotation support. COMMUNITY With regards to community activity, Jonathan Gallimore and myself spoke in two sessions at JAX London 2011, last week. The first on EJB in general and the second on the TomEE server (formerly called just "OpenEJB/Tomcat"). Both session were well attended and met with a good deal of excitement. The "EJB" talk crowed stayed a full twenty minutes after into the lunch hour before we finally said "ok, enough, go eat lunch!" and cut the session "short." The second annual OpenEJB Get-Together is currently underway in Tours, France. A big push to encourage people to show up and hack was made on the mailing list, blog and twitter over the last couple months. Decent group of three committers and two contributors showed up with potentially another one or two later in the week. First day hacking, today, has pretty much been of the "how things work" variety and some notes on "needs" and "wants" that shook out of that has been posted to the list. As usual the "no offline decisions" rule applies, but further the goal is to post as much as possible for the benefit of those that really wanted to attend but were unable. Maybe at some future year we can grow it to barcamp status.
Jim and Greg appreciate the nice writeup.
OpenEJB 3.1.3 was released in late October and contained a decent amount of improvements and new features. Perhaps too much. This was largely due to the gap between the previous release and overall the project decided more diligence in releasing more often was a priority. OpenEJB 3.1.4 was released in late November. Discussions on a 3.1.5 have started. Things look much improved in release frequency for 3.1.x. The 3.2.x codebase has yet to be released in any form. There is still some active and unstable development on that branch with regards to Tomcat 7 support and OpenWebBeans integration, both required for Web Profile certification. Good progress has been made in those two areas particularly in the last month. Hopefully release work will start over the next quarter. There are many anxious users. Community remains active. Many of the committers added last quarter still actively participate which is good as sometimes people become demotivated once they cross that "finish line". We've been lucky enough to have two different people file CLAs for access to contribute to the docs. Both random users with no prior interest shown in contribution. No docs have been produced yet, but we read the interest as a good sign. A sign we need more docs, but that there's too much value for users to switch to another solution and the project is perceived as open enough that contribution is possible. The Nabble issues reported last quarter have been largely resolved. What was previously an OpenEJB "category" that held two forums, dev and user, was automatically converted on one of their many internal upgrades to a full forum that simply didn't point anywhere so posted questions stayed on Nabble and were perceived as ignored. We responded to all posts that were in this forum explaining the issue and were able to switch the forum back to a category. Other projects who are setup in Nabble, either by themselves or by Nabble, should review their setup as this likely happened across the board.
A few releases are in the works. A 3.0.3 release is pending. This branch is fixes only. The anticipated 3.1.3 release is up for a vote now and includes new features and fixes. After the 3.1.3 release, the 3.1.x branch will likely go to minor fixes and enhancements as 3.1.x development has slowed since the 3.2.x branch started. A 3.2 beta release is hopefully not too far off. Java EE 6 certification efforts continue in the 3.2 branch and in concert with Geronimo and OpenWebBeans. Things are largely feature complete with regards to EJB 3.1. Work on CDI integration with OpenWebBeans is progressing. The project welcomes Andy Gumbrecht, Ivan Xu, and Thiago Veronezi who have been voted in as committers. As well Jean-Louis Monteiro and Kevan Miller have been voted into the PMC. Dev list traffic is up and user list traffic is down over the last quarter. User list traffic, which had been steadily increasing over the last two years, dropped to half in May and has stayed there over the last quarter. It's our guess that this is in reference to Nabble. A significant percentage of the user list traffic has come from Nabble over the last two years or so. It has recently come to our attention that Nabble often does not deliver messages to the lists, yet still shows them in their website as part of their "OpenEJB" forum. The result has lead some users to think they were being ignored. I find Nabble's misrepresentation of their service and the impact on users perception of the project to unacceptable. Either they are an archive with posting capability or they are separate forum with its own separate support community. I have done an audit of the months missing threads that only show up in their false representation of our archives and sent them a message asking for the corresponding Message-IDs. No response so far. I will continue pushing the issue with them.
Work on the 3.1.next development has slowed and a release of that codebase (3.1.3) is likely to come out soon. Activity on the 3.2 codebase is going strong with significant progress on EJB 3.1 features, specifically; @AccessTimeout, @AfterBegin, @BeforeCompletion, @AfterCompletion and some support for the @Asynchronous method invocations. Most of this work is being done by contributors. New committers are sure to be right around the corner. Work has started on JCDI integration aided by the OpenWebBeans community. That work is somewhat revolutionary and a separate branch has been created temporarily to workout the overall architecture and design of the integration. Significant work is also being done to overhaul and test the application validation code and related i18n message keys. Dev list participation has increased due to greater contributor activity. User list traffic has slowed somewhat which is welcome as it provides a little breathing room for development.
OpenEJB 3.0.2 was released in early April, primarily focused on supporting the Geronimo 2.1.5 release. Major development activity has been around new support for JAX-RS and JPA 2.0, upgrading ActiveMQ versions, EJB 3.1 @LocalBean support, major overhaul of Stateless pooling code and JMX monitoring. Trunk moved from 3.1.next (java ee 5 and java 5) and mostly stable to 3.next (java ee 6 and java 6). A branch has been spun off for 3.1.next development and so far remains quite close to trunk minus some java ee 6 features. User list traffic now getting heavy enough that there are more questions than answers. Something to keep a close eye on as the community continues to grow. The developer side of the project shows signs of growth as well with a few new promising contributors who are themselves users. These things tend to fluctuate, hopefully we can pull in some new active committers while we are trending upward.
OpenEJB 3.0.2 was released in early April, primarily focused on supporting the Geronimo 2.1.5 release. Major development activity has been around new support for JAX-RS and JPA 2.0, upgrading ActiveMQ versions, and major overhaul of Stateless pooling code. List user list traffic now getting heavy enough that there are more questions than answers. Something to keep a close eye on as the community continues to grow. The developer side of the project shows signs of growth as well with a few new promising contributors who are themselves users. These things tend to fluctuate, hopefully we can pull in some new active committers while we are trending upward.
Shane to request that the report be resubmitted.
Main areas of development activity include OSGi support, upgrading JAX-WS and support for JAX-RS, and Java EE 6 @ManagedBean support. More detailed planning has also begun for the remaining EJB 3.1 work. Overall user list activity continues to increase with October and November both being record months in terms of volume. Diversity in developers responding to user requests has also been greatly improved, quite stellar in fact, with more committers pitching in and resolving user issues. A wonderful trend. Holidays had their usual impact on December activity. OpenEJB Eclipse Plugin 1.0.0.alpha was released in late October and a screencast created which shows how to get started with it was put up in the project blog and website. An informal get together is planned in Milan, Italy for the last weekend of January. Information has been sent to the user list and anyone is welcome to come. Primary goal is just to meet each other and have a few beers, but there's certainly room for tech talk and some will likely occur. Anything substantial will reach the dev list as with any offline communication.
Get together is noted.
OpenEJB 3.1.2 was released over this last week. Vote concluded last Thursday, binaries pushed Friday, announcements went out on Monday. Overall it is a release focused on bug fixes and improvements. This is the first release from the 3.1.x branch to be included in a Geronimo release. Significant time/effort was given to address related TCK issues and get everything closed up in time for the Geronimo 2.2 release which should roll very soon. User list traffic continues to increase with a considerable spike over the last two months. Active new faces have popped up on the user and dev list over the last quarter. A clear standout is Quintin Beukes who has been passionate about helping other users and giving back to the project. We've asked him for a CLA and are excited to see what he contributes. The blogs.a.o service has been used quite actively with good success. Thank you again to all who helped set that up. It has proven to be an invaluable tool. The blog preview support we created for RTC-ing blog posts has been tweaked and installed right on blogs.a.o with the help of Gavin and other members of infra. A big thanks to them and we hope that other projects find it as useful as we do. Jonathan Gallimore was voted in as a PMC member shortly after the previous board report. An initial alpha release of the OpenEJB Eclipse plugin was put up for a vote in September, with Jonathan as release manager. The vote was eventually cancelled to address some missing license headers and NOTICE file formatting, but after a small hiatus the plugin is back up for a vote this week and looking good. With fingers crossed we can soon celebrate the first release of the OpenEJB Eclipse plugin and as well as congratulate Jonathan on surviving his first Apache release.
OpenEJB 3.1.1 was released in June. The release contained a mix of improvements and fixes. Overall it was very well received and very anticipated as the last trunk release was in October 2008. More frequent dot releases are planned and a 3.1.2 will hopefully be not too far behind. Project participation in blogs.apache.org started up in April and has been fairly successful with about seven posts so far. Some effort has gone into creating a convenient way that blog posts can be staged for community review before being posted. The result has proven to be very easy and not cumbersome which directly contributes to the number of posts in the last two months or so. Two screencasts, the first of many hopefully, were also added and published through the blog. Jean-Louis Monteiro was voted in as a committer in June. The project is extremely happy to have him as a committer and very much enjoys his work and overall contributions in the community. Congratulations, Jean-Louis! Preparation has been underway to do a first release of the OpenEJB Eclipse Plugin. As part of the work in preparing the release files, discussion started at the beginning of the month on adding the release manager and majority contributor to the plugin, Jonathan Gallimore, to the project PMC for better oversight. The discussion was started on the dev list carefully and deliberately with so far very healthy and positive results. A vote for his addition to the PMC is now underway on the dev list, the first of hopefully many open PMC votes. A big compliment to the community to whose amazing openness, mutual respect, and overall friendliness makes this kind of thing possible.
Greg: imo, PMC membership votes should be private. it is *very* hard for a fellow committer to -1 somebody in public. thus, you do not get truly unfettered voting by doing so on the dev@ list.
Justin: Well, I know many PMCs cast their votes in public. Does it merit a broader announcement/reminder?
Doug: David is aware of the issue, and feels that in this case this process is a better fit for this project.
Sam: I suggest a guideline, not a rule
Brian: I prefer flexibility
Shane: committer votes private be strong guideline, but not rule
Jim: concern is the public minutes, I agree to guideline not a rule
Doug: I'll work to get something on the dev site that is advisory
A patch release of OpenEJB 3.0 (3.0.1) was released with fixes aimed to support the Geronimo 2.1.4 release. Talk has started on a release of the current 3.1 branch (to be OpenEJB 3.1.1), which already contains several fixes and improvements over the 3.1 version released in November. List traffic has continued to increase. In Q1 2008 traffic averaged 63 messages per month. In Q1 2009 the average is 133 per month. This resulted in occasional delays in response times due to bursts of requests. At a particularly heavier burst one user complained in an email titled, "Thank you for not supporting me in any way." This proved to be an overall positive event as it provided an opportunity to reset expectations, get everyone behind the project, and resulted in a generous increase of participation from users and committers alike[1]. Ultimately it was just what we needed. Jean-Louis Monteiro has been contributing some good patches and time on the user list and proving to be a good potential committer. His activity is primarily around web services which is one area where can certainly use the expertise. His participation is greatly appreciated and we look forward to continued contribution. Discussions have opened up with OpenWebBeans on providing them with the tools they need to support their own OpenEJB integration in efforts to complete the JSR-299 specification. The JSR-299 itself is currently very unstable and major changes to the core of the specification, requested by the Java EE 6 (JSR-316) EG, are planned to address overlap with other specifications like JSF and EJB. These will certainly provide some challenges as the specification is rebalanced. Several users have recently pointed out a possible incompatibly in regards to the handling of business remote interfaces also marked as a web service interface. The issue has been raised on the EJB 3.1 (JSR-318) EG. Regardless of the outcome, support for that feature is planned. [1] http://mail-archives.apache.org/mod_mbox/openejb-users/200902.mbox/ -> %3c98A91BE3-4ACC-4D86-AE19-4CD4A202E1CD@visi.com%3e
The OpenEJB 3.1 release vote passed and binaries were shipped in late October. It was a long anticipated release as OpenEJB 3.0 was released seven months prior. An 3.1.1 patch release is in the works with the goal of getting more frequent, smaller, releases out there for people to use. Work on the Eclipse plugin continues and discussion of moving out of the sandbox and preparing a first release has begun. Development slowed over the holidays. No new features have been added with most work relating to TCK and other bug fixes required for the upcoming 3.1.1 release. Despite the holidays, user list traffic was up for both November and December and appears strong in January as well. The requested Privacy Policy for projects using Google Analytics has been added to the website, copied from the Jackrabbit Privacy Policy.
The privacy policy is much appreciated, though it should have been mentioned in the report.
The user base has grown significantly. The primary areas seem to be people replacing the JBoss Embedded platform with OpenEJB as an embedded container for either testing or Swing/GUI work and people using OpenEJB in Tomcat for web work. There have also been some reports of very large applications getting ported to OpenEJB. External signs of adoption have increased as well with some OpenEJB users popping up in other communities such as Maven asking for OpenEJB focused improvements in their tools, a half dozen or so very favorable blog entries from people outside the project and a recent thread on TheServerSide where many users expressed they were considering leaving Spring for OpenEJB/Tomcat or Glassfish. Development on the OpenEJB Eclipse Plugin continues strong. The still-in-development Eclipse plugin is attracting some interest and has already received some contributions from at least two different individuals. Thanks goes out to Jonathan Gallimore for not succumbing to post-commit-status burnout as so many people do when first getting commit. The dedication is noted. Other larger areas of development have been a total overhaul of the client/server aspect of OpenEJB, first in the request speed and throughput and secondly in request failover and retry. This had been a weak area for the project and these improvements will likely increase the number of people using the standalone version of OpenEJB (current major areas of use are embedded and Tomcat). Some experimental work on integrating OpenEJB with Spring has been done which when completed should prove to be a compelling feature. Support for EJB 3.1 is underway. Full support for the proposed Singleton bean type has been added, which to our knowledge is the only implementation in the market currently. This should drive some EJB 3.1 early adopters to the project and serve as a good tool for getting feedback for the EJB 3.1 spec. The OpenEJB 3.1 release is up for a vote and if all goes well will be final in a few days. It's been a bit too long since our last release in April. Hopefully after 3.1 is released we can get back into the frequent release rhythm we had throughout the betas and up until 3.0 final.
Greg to follow up with Henning to understand his concerns about OpenEJB transition paths
The OpenEJB 3.0 Final release in mid April brought some good attention to the project and more new users. User list traffic showed a small increase in April and May and a sharp spike in June. July looks to be a slow month so far. Many users are content and anxiously awaiting the next release. Planning for the next release has begun. The list of fixes and improvements is growing very large. If all goes well it won't be too much longer before we start spinning binaries for OpenEJB 3.1. Major new features will include more EJB 3.1 support, jaxb performance increases through the SXC project, network performance increases in client/server communication, cmp and jpa conversion improvements, tomcat console improvements, and fixes in the jdbc connection pooling. Jonathan Gallimore was voted in as a committer with great support. Jonathan is not just a new committer to OpenEJB but to the ASF. A very warm welcome to Jonathan!
The highlight of early February was the release of OpenEJB 3.0 beta 2 which was very well received and triggered another small increase in overall users@openejb.a.o traffic. We've also seen some encouraging growth signs we haven't seen for quite a while: users answering each other's questions; first time posters saying "we've added this feature, do you want it?"; more questions answerable with documentation links; random new faces on IRC. Work on OpenEJB 3.0 final began towards the end of February with the first binaries up for vote on March 11th. Some wonderful feedback on both the dev and users list revealed some critical technical issues with those binaries and the vote was cancelled so that the issues could be fixed. Several members of the community went the extra mile to help get issues fixed and the release out the door. After steady stream of bug fixes, legal file maintenance, and a few more aborted votes, the long anticipated OpenEJB 3.0 Final was released April 12th. The binaries proposed a month prior pale in comparison to the binaries eventually released and we are all very pleased with the quality of the 3.0 final. We are very excited to see what kind of a splash 3.0 will make and expect a 3.0.1 will be required soon. The work contributor Jonathan Gallimore has been doing with an OpenEJB Eclipse plugin has taken root with other developers in the community and development naturally changed from code drops to frequent patches and discussion. A big thank you to committer Daniel Haischt for contributing to the Eclipse plugin and giving Jonathan someone to work with and the opportunity to demonstrate his collaborative skills. A bigger thank you to Jonathan for his patience.
The release of OpenEJB 3.0 beta 1 at the end of September showed an mild but noticeable increase in user traffic which has continued since. Several usability improvements and related new features have been added, particularly around a returning user from years ago Alex St. Croix. Alex has already written some blog entries, created a couple video tutorials, and has a downloadable PDF of using OpenEJB embedded in Tomcat which is a dozen pages and growing. This is all very good for OpenEJB and we are very excited to see user activity of this nature again. Web Services support has been added to OpenEJB in both standalone and Tomcat embedded modes, and significant work as been contributed to the CXF project as a result to add new features required by OpenEJB but not already present, such as rpc/encoded web services. The ability to embed OpenEJB into Tomcat has been re-expanded from temporarily just supporting Tomcat 6.0 to now version 5.5 as well including annotation processing support which is usually a v6.0.x and higher feature. Support for older versions was lost when the integration was reworked and improved over the OpenEJB 1.0 approach, however post OpenEJB 3.0 beta 1 release, requests from users of older Tomcat versions began coming in showing that the ability to support pre Tomcat 6 users is still very important. The documentation has been reorganized significantly. A new confluence space as been created dedicated entirely to the OpenEJB 3.0.x codebase and reintegrated back into the main website. Several new examples have been created as well. A major issue with the documentation was that most of the new documents weren't linked into the main site, were just loose pages, and had no "center" to bind them all together. The creation of dedicated 3.0.x space with it's own index and new left navigation section has dramatically improved this. Jonathan Gallimore, a newer contributor, recently contributed another large patch to the Eclipse plugin he's been working on that takes an EJB 2.x application and adds the annotations to the source code required to turn it into an EJB 3.0 application, removing the equivalent xml as it goes. Jonathan has done great work, but we could be doing better as he is largely working alone and isn't getting the benefit of working closely with existing committers. It's always difficult to pull people in when there isn't a strong intersection with existing code/people. Release work on OpenEJB 3.0 beta 2 has begun. There was a perpetual state of "going to release" through late November and all December, however all the open issues have been cleared and the general mood is "it's over-ready." We've branched and have begun helping other projects to release some of the things we have dependencies on such as the Geronimo Transaction Manager/Connector and the XBean libraries. All is going well and we should see OpenEJB 3.0 beta 2 put up for vote this month. On a general note, OpenEJB celebrated it's eighth year of existence in December. As a personal comment from someone who's been on the project the entire time, I [David Blevins] have never seen the project in such good shape. A major challenge going forward will be releasing the 3.0 final and getting OpenEJB back on people's radar.
Approved by General Consent.
OpenEJB 3.0 beta 1 released Completed Export Control (Cryptography) process Completed integration with Tomcat 6 Expanded documentation and examples Activity on the user list has increased slightly since the release
Brief discussion on the terseness of the report. Decision was that it was sufficient.
Approved by General Consent.
Work on the OpenEJB 3.0 release is coming to a close. Documentation remains the largest outstanding item. A complete audit of all documentation was completed and concrete steps to improve it were detailed. Progress on updating the out-of-date documentation has already been made. The usability of the codebase has matured significantly through many contributions from the community and very little remains to be completed in that regard. Developer activity is up. We are delighted to have voted in a dedicated contributor, Karan Malhi, as a new committer and he has proudly excepted. No CLA is on file yet. User list activity overall remains low, though some new faces have started to pop up whom we are hoping can provide us with some good pre-release feedback. We hoping to see a measurable increase in user list activity post release.
Approved by General Consent.
CURRENT FOCUS Primary activities in the project are around polishing up features, user-facing code, reducing dependencies, documentation, and taking care of legal in preparation for the coming 3.0 release. No real issues stand in the way at this point, builds and voting should start soon. CONTRIBUTIONS More wonderful documentation contributions have been made by contributor Karan Malhi who is actively scraping our list archives and creating documentation from old emails. EXTERNAL INVOLVEMENT Contributed managed connection support to commons-dbcp. This will eliminate our custom database pooling code, and adds an important new feature to DBCP. This feature should be useful to anyone using DBCP in a managed environment such at Tomcat. Also, OpenEJB has a large set of data base test case, and we have already found a few bugs to fix in DBCP for which we are working on fixes.
Approved by General Consent.
All Incubator Infrastructure has been migrated over to TLP as well as removal of any miscellaneous Incubator related disclaimers in code and the website. The project is excited to have implementation of EJB 3.0 complete and to see our sister project, Geronimo, announced JavaEE 5 Certification. Community short term goals are a release of OpenEJB 3.0 along with regular published snapshots. Early development discussions are underway on clustering, application validation as well as general items for code clean up. List activity post JavaEE 5 Certification is back up to normal. We still gain more contribution interests from new people like Karan Malhi who is interested in fixing some issues with OpenEJB 3.0 assembly build process.
Approved by General Consent.
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 enterprise application containers and object distribution services based on, but not limited to the Enterprise JavaBeans Specification. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache OpenEJB Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache OpenEJB Project be and hereby is responsible for enterprise application containers and object distribution services based on, but not limited to the Enterprise JavaBeans Specification; and be it further RESOLVED, that the office of "Vice President, Apache OpenEJB" 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 OpenEJB Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache OpenEJB Project; 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 OpenEJB Project: * David Blevins (dblevins@apache.org) * Alan Cabrera (adc@apache.org) * David Jencks (djencks@apache.org) * Jacek Laskowski (jlaskowski@apache.org) * Brett Porter (brett@apache.org) * Dain Sundstrom (dain@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Blevins be appointed to the office of Vice President, Apache OpenEJB Project, 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 initial Apache OpenEJB Project be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenEJB podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator OpenEJB podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 6C, Establish Apache OpenEJB Project, was approved by Unanimous Vote.
iPMC Reviewers: jukka, yoavs, jim, noel OpenEJB is an open source, modular, configurable, and extendable EJB Container System and EJB Server. Incubating since: 2006-07-10 We received some very excellent feedback we are all really proud of from a new face in the community. OpenEJB has always prided itself for being the kinder, gentler side of open source and it's really good to know this is coming through. http://mail-archives.apache.org/mod_mbox/incubator-openejb-dev/200701.mbox/% 3cac85de250701201929x2de78662r57de9d62fa30642f@mail.gmail.com%3e Recent New Contributors: Karan Malhi and Raj Saini contributed their first patches. New Committers: Manu George was voted in as an OpenEJB committer. Mohammad Nour (voted in last reporting cycle) finally got his iCLA approved and will be getting his well-earned commit. Work on an OpenEJB Eclipse plugin was launched and is generated lot's of excitement in the community. iPMC questions / comments: * jukka: Things to do before graduation? ---- This is the OpenJPA status report for the board for the three month period ending Mar 2007.
OpenEJB is an open source, modular, configurable, and extendable EJB Container System and EJB Server. Incubating since: 2006-07-10 Additions to the PPMC: David Blevins, David Jencks Additions to the committer roster: Rick McGuire, Mohammed Nour (not yet processed) All remaining infra has been migrated to ASF hardware: * JIRA * Confluence * Website As hoped the JIRA migration tool we created has helped other Incubator projects migrate as well, most recently Ivy. All IP was cleared. Recent new contributors: Manu George and Filippo Diotalevi contributed their first patches. Recent activity has centered around producing a 2.2-incubating release. The spread of workload and commitment to getting all of the process right (including updates to the source headers) was very encouraging. A vote was held, and recently passed, including the 3 binding votes from the incubator PMC (by the mentors of the podling).
OpenEJB discussion is happening on the Incubator mailing list, but the resources from codehaus have not yet been moved over, as they wait for some committers to still file CLAs. The latest ETA was to move everything over this week.
The OpenEJB project has begun it's migration into the Incubator. Primary activities are setting up infrastructure and establishing a list of active committers. Items completed so far: * Status page created and published to Incubator website * Lists established and in active use * Most CLAs are in, more coming * Account created for Daniel Haischt