> On Apr 21, 2015, at 8:31 PM, Emmanuel Lécharny <[email protected]> wrote: > > now that Apache CON US is over, you probably have a bit less stressed > and loaded... >
Indeed > > On Apr 21, 2015, at 8:31 PM, Emmanuel Lécharny <[email protected]> wrote: > > Can you tell us what's the current status of the project, especially > regarding the tests and the packaging ? 1. core - released v1.0-RC40 on April 15th 2. realm - ready to go 3. web - ready 4. rest - ready 2 - 4 are now using the org.apache.directory as parent pom 3 & 4 problem with genesis license file check has been fixed I am able to build, compile and pass all of the tests in my dev vms. There were some new bugs reported recently, but no showstoppers. > > On Apr 21, 2015, at 8:31 PM, Emmanuel Lécharny <[email protected]> wrote: > > We have a release done for core, we still have some release to provide > for the 3 other modules, and it will require a bit of work and probably > some rethink of the existing Fortress-core release (all in all, this > first release was a way to kickstart the release process). May be moving > to a top-level module for the 4 Fortress projects is a think to have... > > What's your take on all this ? Agree on the rethink. Right now there are too many projects with too many manual steps. One of the more interesting things is Stefan's introduction of a docker image running openldap and testing on jenkins build server. It runs quite well though there is a bug in the audit log test case pulling back failed authZ records. I would like to see more of docker and more automation within the fortress dev/test/release cycles. So yes, there is much work to be done before the build and release is right. But since the core has already been released we should do same for the others. We'll need someone's eyes looking at the other 3 to make sure the notice and license files are compliant. I *think* it good but could have missed something. Thanks Shawn [email protected]
