Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2017-05-22 18: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.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

TomEE

19 Apr 2017 [David Blevins / Bertrand]

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.

18 Jan 2017 [David Blevins / Jim]

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.

21 Dec 2016 [David Blevins / Jim]

No report was submitted.

@Jim: pursue a report for TomEE

16 Nov 2016 [David Blevins / Bertrand]

No report was submitted.

19 Oct 2016 [David Blevins / Sam]

No report was submitted.

21 Sep 2016 [David Blevins / Marvin]

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.

17 Aug 2016 [David Blevins / Marvin]

No report was submitted.

20 Jul 2016 [David Blevins / Shane]

No report was submitted.

20 Apr 2016 [David Blevins / Bertrand]

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.

20 Jan 2016 [David Blevins / Greg]

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.

18 Nov 2015 [David Blevins / Jim]

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.

21 Oct 2015 [David Blevins / Sam]

No report was submitted.

16 Sep 2015 [David Blevins / Bertrand]

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.

19 Aug 2015 [David Blevins / Greg]

No report was submitted.

15 Jul 2015 [David Blevins / Greg]

No report was submitted.

22 Apr 2015 [David Blevins / David]

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

18 Feb 2015 [David Blevins / Doug]

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.

21 Jan 2015 [David Blevins / Ross]

No report was submitted.

19 Nov 2014 [David Blevins / Jim]

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.

15 Oct 2014 [David Blevins / Ross]

No report was submitted.

20 Aug 2014 [David Blevins / Doug]

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.

16 Jul 2014 [David Blevins / Chris]

No report was submitted.

21 May 2014 [David Blevins / Roy]

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.

16 Apr 2014 [David Blevins / Chris]

No report was submitted.

15 Jan 2014 [David Blevins / Bertrand]

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.

16 Oct 2013 [David Blevins / Brett]

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.

21 Aug 2013 [David Blevins / Shane]

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

17 Jul 2013 [David Blevins / Brett]

No report was submitted.

17 Apr 2013 [David Blevins / Greg]

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.

16 Jan 2013 [David Blevins / Jim]

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.

19 Dec 2012

Change the Apache OpenEJB Project Name

 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.

21 Nov 2012 [David Blevins / Doug]

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.

17 Oct 2012 [David Blevins / Ross]

No report was submitted.

25 Jul 2012 [David Blevins / Rich]

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.

18 Apr 2012 [David Blevins / Sam]

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!

24 Jan 2012 [David Blevins / Larry]

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.

26 Oct 2011 [David Blevins / Brett]

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

17 Aug 2011 [David Blevins / Sam]

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

20 Jul 2011 [David Blevins / Jim]

Report missing; will report next month.

20 Apr 2011 [David Blevins / Shane]

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.

19 Jan 2011 [David Blevins / Bertrand]

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.

20 Oct 2010 [David Blevins / Shane]

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.

21 Jul 2010 [David Blevins / Shane]

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.

19 May 2010 [David Blevins / Geir]

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.

21 Apr 2010 [David Blevins / Shane]

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.

20 Jan 2010 [David Blevins / Brian]

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.

21 Oct 2009 [David Blevins / Doug]

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.

15 Jul 2009 [David Blevins / Doug]

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

15 Apr 2009 [David Blevins / Bertrand]

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

21 Jan 2009 [David Blevins / Bertrand]

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.

15 Oct 2008 [David Blevins / Greg]

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

16 Jul 2008

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!

16 Apr 2008 [David Blevins / Geir]

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.

16 Jan 2008 [David Blevins / Jim]

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.

17 Oct 2007 [David Blevins / Sam]

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.

29 Aug 2007 [David Blevins / Geir]

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.

18 Jul 2007 [David Blevins / Jim]

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.

20 Jun 2007 [David Blevins / Justin]

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.

16 May 2007

Establish Apache OpenEJB Project

 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.

28 Mar 2007

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.

20 Dec 2006

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).

16 Aug 2006

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.

19 Jul 2006

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