[Fennel-developers] 0.9.4 release prep

[Nicholas G. <ngo...@dy...>]

Once we get a fully integrated, tested, and spot checked //open/dev we will work through the release procedure here:
http://pub.eigenbase.org/wiki/ReleaseProcedure

We will start our integration from dy/dev up to open/dev this Friday.  It would be helpful if dt/dev integration up could be complete by then, but it's not a prerequisite but it would be much easier to have a clean, 100% passing open/dev prior to us integrating up.

We're still trying to get our windows build machines re-imaged, but will do that prior to release.

Our branch contains a few modifications to release packaging scripts that will be in our integration up.  In particular, we modified the scripts to allow for:
 - Releases can be built from any branch, not just //open/dev.  This is helpful when we're doing milestone releases directly from the dy/dev branch of LucidDB (or patches for customers).
 - Release point releases are now a string (RC1 or M1 or GA or ... whatever).  I'm not sure how dependent Aspen is on FarragoReleaseProperties class, but we've changed the datatype of point release to StringProperty instead of IntegerProperty.  Comments/concerns/flames welcomed.

We had to revert (on our branch) JVS's generated transient JMI implementation because of issues with packaging for a release (Enki + transient classes).  We intend to do release with the memory only implementation (same one present in 0.9.3) and work on re-enabling post 0.9.4.  However, if anyone has time to sort out the release packaging of this change prior to a 0.9.4 release we'd welcome the help.

Nick