The roadmap sketches out, in broad terms, what is on the horizon for beet development. If you want to suggest additions or indicate priorities, come visit the mailing lists or development forums.
Q2 2009
beet 1.4.0 final: Mid-July
With the exception of a few minor configuration enhancements, beet 1.4.0 is code complete and a final release should be announced by mid-June mid-July. Between now and then we'll be working on some performance benchmarks, improving the documentation, and planning for the next release.
Q3 2009
beet 2.0 alpha
Features requested on the development forum are tending toward the high end -- support for tracking transactions across multiple applications, support for EJB3, non-Spring apps, and so on. So we'll branch for 2.0 development soon.
The following features are under consideration for 2.0. Eventually each of these should have an Issue Tracking number where we can find more detailed discussion:
Major Enhancements
- Support for tracing distributed call chains across multiple applications, multiple threads in the same application
- EJB3 monitor
- Web Service monitor
- Non-Spring / legacy app monitor
- Runtime configuration changes
- Persistent config changes across system restarts
Minor Enhancements
- Improved configuration schema
- keiker integration
- customizable event storage schema
- configurable event data for method calls (store some parameters but not others, etc)
- migrate to EasyAnt-based build
- Multi-language support (esp. Scala, C#)
- Integrated system resource monitors
- Integrated database traces
A key litmus test for any candidate feature design is whether it meets the ergonomic standards for beet. Specifically, all features should be enabled at runtime (not compile-time). We should only need the addition of jars and minimal configuration to enable monitoring. Additionally, configuration should be centralized as much as possible (e.g. appear alongside other beet config in our Spring config file). Obviously these standards are subject to periodic reevaluation, but deployment simplicity is why beet exists.
2.0 should be in beta well before the end of Q3.
Q4 2009
beet 2.0 final
There's plenty on the roadmap to keep us busy, but we should constrain the scope to allow for a major release in Q4, hopefully early in the quarter. At this point we can evaluate branching for 3.0 or focusing more on minor releases for the 2.0 / 1.0 series.