Hello, Well said Harald !
In addition, I think TomEE will be taken even more seriously if it was written somewhere on its Internet site that for security alerts (CVE...) a new release would be provided in at most xx weeks. I know many potential users who wouldn't consider using TomEE if a Tomcat CVE is publicized and the only way to fix is to use a "Snapshot", which may not be stable. The question is : "TomEE is currently a super choice of developers, how can it be also a super choice for IT people, at least as much as Tomcat is ?". Fixed number of releases per year would be a good start (IT people won't care about Milestones, but I like this idea for developers, if "Snapshot" could be replaced by "Nightly build" - okay I confess : I like Eclipse way :) Alex On Sat, Dec 8, 2012 at 5:09 PM, Harald Wellmann <hwellmann...@gmail.com>wrote: > To sum up my experience with TomEE: 1.0.0.beta was completely > unusable, the 1.5.0 release has made a giant leap towards production > quality but still has blocker bugs, which are getting fixed very > quickly, and this list is extremely helpful. > > The problem with snapshots is that they disappear. If you work with > Maven, you can't even release a product of your own with a snapshot > dependency (and for a very good reason too). I've often cherrypicked > fixes from unreleased versions of third-party dependencies, but that > always involves the hassle of checking in a local copy, building a > private release and deploying it to a local Nexus. > > At the current rate of bugs appearing and getting fixed in TomEE, it > would be very helpful to have frequent releases. You may want to > differentiate between milestone releases or stable builds and GA > releases. It's ok to have only two or three GA releases per year as > long as there are frequent (e.g. monthly) milestone releases, > published to Maven Central, but without all the QA and ASF procedural > overhead. > > IMHO, you cannot overestimate the negative effect of people taking a > quick look at a project, running into problems, finding not enough > documentation and then turning away and spreading bad news. So in > addition to coming up with the next release, IMHO this project would > greatly benefit from usable entry-level documentation and from sorting > out the TomEE/OpenEJB confusion. > > Best regards, > Harald >
