Hic sunt liones
This is development version of midPoint. Although we try to keep midPoint in a good working shape through the entire development cycle, there are some fluctuations and unforeseen circumstances. This is development after all. Therefore proceed with care. Here be lions.
midPoint Development Snapshot is the latest build from the latest source code. It is the "HEAD" of the development. The bleeding edge.
Installing the Snapshot
There are two ways how to install the snapshot:
Quality of the Snapshot
Quality of the snapshot varies depending on the development phase:
|Phase / milestone||Time period||Activities||Expected code quality||Recommended community participation|
|Feature development||start - feature freeze|
(usually 4-5 months)
|Development of new features.|
Restructuring, cleanup, architectural changes.
Fixing of important (subscriber, security) issues.
There are usually three internal milestones (M1-M3, M3 usually being feature freeze)
|No assurance about quality. Quality varies depending of specific feature. Nothing should be broken too badly - maybe except quite rare and usually very short intervals. |
Old features may be broken occasionally.
New features may not work at all.
|It may be worthwhile to check the stat of new features - especially for subscribers that are endorsing particular features. Look at the functionality, provide feedback, but please do not bee to pedantic yet. This is still work in progress.|
It is not recommended to systematically test all midPoint functionality yet. The bugs and unfinished part are perfectly normal at this point. Reporting them makes no very little sense.
However, it makes sense to test the functionality of new features, especially at the milestones (M1,M2,M3).
This is ideal phase to contribute new features to midPoint.
You can also help improve the documentation of old features.
|Feature freeze||milestore|| milestone|
(M3 or M4)
|Old features mostly stable, but some bugs may be present.|
New features working at least for common positive cases. Bugs are still quite likely, but they should not be too bad.
|Start systematic testing of all midPoint features.|
|Testing and bugfixing||feature freeze - release|
(usually 1-2 months)
|Quality assurance (testing) and bugfixing.||Quality should be improving every day.||Participate in midPoint testing. Make sure midPoint works for your usecases. File bug reports and contribute fixes. Help improve the documentation of new features as the configuration schema should be perfectly stable now. Test upgrade and data migration.|
(Please see the explanation of bugfixing expectations below.)
|Production-ready||Use midPoint in production.|