mid march sounds good to me, in fact would prefer to have it then rather
than pushing and risk final release anytime in summer when people will
start being unavailable to test. I plan on working on bug fixes for
that release but no need to hold up for any specific one.
/mikem
Rick Hillegas wrote:
Thanks to everyone who has been updating the 10.5 release page. So far I
don't have a sense of whether the community would be comfortable with
producing a release candidate in mid-March.
Are there any other major features which we should add? For instance, I
see that there's been a lot of progress on DERBY-3788 (Provide a
zero-admin way of updating the statisitcs of an index). Do we want to
include that feature in 10.5--if so, is mid-March reasonable?
Thanks,
-Rick
Rick Hillegas wrote:
To track the upcoming 10.5 release, I have hung the following status
roundup off our top wiki page:
http://wiki.apache.org/db-derby/DerbyTenFiveOneRelease I would
appreciate it if everyone could take a moment to update this page with
the work you are doing which you want to expose in 10.5.
If we stick to our traditional release cadence, I expect that we will
want to produce a 10.5 release this spring. Is anyone planning or in
the middle of work which won't be done by mid-March? Does anyone want
us to push the release back till later in the year--and if so, what
would be a better release date?
Thanks,
-Rick
