OpenSSO: Nightly and Stable Builds
By justme on Nov 22, 2006
There are some answers.
It took us about 9 months to open source the Access Manager code base, We did code clean up; move to an open source test framework; add more comments to our code (so that external parties can understand the logic better); etc. During this 9 months, we are also committed to ship Sun Java Enterprise System's Access Manager 7.1. So, we have two CVSes, one for Access Manager 7.1 (which is private to our team) and other for OpenSSO (which is public to all). We are constantly sync-ing up these CVSes. i.e. whatever got fix in private CVS goes to OpenSSO CVS.
Much of our QA effort are spent on Access Manager 7.1. Theoretically, OpenSSO code base is stable because it is based on Access Manager 7.1. However, we cannot be certain because we did code clean and minor refactoring on OpenSSO code base.
Now, we are almost done with Access Manager 7.1, and soon we will have a QA certified nightly build and we will tag it as "stable".