You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Samuel Andrew McIntyre <fu...@nonintuitive.com> on 2004/10/15 03:31:14 UTC

proposed binaries for 10.0.2.1 posted

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

Sam Ruby has graciously offered to host a proposed set of binaries for 
the 10.0.2.1 release here:

http://www.apache.org/~rubys/derby10021/

The bin package includes the HTML documentation (basically a copy of 
the website, since we need the CSS and images and dir structure), the 
'publishedapi' javadoc, and the jar files.

The lib package includes just the jars, and looks like the previously 
posted snapshot release.

The src package is the source as of the last changed revision, 54760, 
which was used to build the binaries included here.

Give them the once over, feedback is greatly appreciated, of course. I 
will be forwarding this to the Incubator PMC shortly to ask for 
permission to post as a release. Here are the changes included since 
10.0.2.0, the initial code drop:

Release: 10.0.2.1

bugs fixed for the current release:

showstoppers:
DERBY-24 Client should not be able to raise an event on a 
PooledConnection it no longer owns.
DERBY-32 Logic to prevent mutiple jvms booting the same database in 
parallel to avoid accidental corruptions on Unix environment is not 
working.

non-showstoppers:
DERBY-6 Trigger of the form: create trigger ... values myFunction(); 
has no effect.
DERBY-30 Connection.close() method inconsistently throws exception on 
closed connection
DERBY-38 Make LOCKS as non-reserved keyword in Derby since it is not a 
reserved keyword in the SQL standards

patches applied in this release:
[PATCH] Optimization of 
org.apache.derby.impl.services.uuid.BasicUUID.toByteArray()
[PATCH] Set Derby's build number to be the subversion revision number
[PATCH] derby.war file build
[PATCH] derby.log file error message
[PATCH] Network servlet display only message key
[PATCH] added 3 more parser generated files to the clobber target in 
main build.xml
[PATCH] Various fixes to javadoc generation
[PATCH] Trigger Bug Fix
[PATCH] Fix to prevent empty log file switches that could cause 
recovery failures
[PATCH] ExternalSortFactory Bug Fix
[PATCH] Modify dblook messages to enable localization ...
[PATCH] minor bugs in dblook
[PATCH] Extension Packaging

andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBbyhpDfB0XauCH7wRAniqAJ98f9J60TPfELxVhWjxwclPaM3jYgCeKOdK
e2w/ZAIYb7Kjs3m6MbCALwM=
=8ttv
-----END PGP SIGNATURE-----


Re: proposed binaries for 10.0.2.1 posted

Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Samuel Andrew McIntyre wrote:

> Hello all,
>
> Sam Ruby has graciously offered to host a proposed set of binaries for
> the 10.0.2.1 release here:
>
> http://www.apache.org/~rubys/derby10021/
>
> The bin package includes the HTML documentation (basically a copy of the
> website, since we need the CSS and images and dir structure), the
> 'publishedapi' javadoc, and the jar files.

While it's ok for this release, I think the complete copy of the
web-site is not a valid option for the future. As more information goes
onto the site the releases will increase in size, in fact this release
has the original snapshot jars, and so the next release will have those
and this release, and any other intermediate snapshot jars, etc.

I assume an essential step to fixing this, is to get the docs into XML
source form, from which separate packaged docs can be created.

Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBdtruIv0S4qsbfuQRAi4KAJ9wdKe2LIntz25Kt5Sr9BoNboZ2qwCfSKyS
OuvFK7/fdIrUrItQPg2hSnA=
=uKEb
-----END PGP SIGNATURE-----


Re: proposed binaries for 10.0.2.1 posted

Posted by Jonas S Karlsson <js...@yesco.org>.
Samuel Andrew McIntyre wrote:
> Give them the once over, feedback is greatly appreciated, of course. I
> will be forwarding this to the Incubator PMC shortly to ask for
> permission to post as a release. Here are the changes included since
> 10.0.2.0, the initial code drop:

The file CHANGES is missing.

See http://mirrors.qualsec.net/apache/httpd/CHANGES_2.0 for a textual
variant and http://cocoon.apache.org/2.1/changes.html for a HTML
variant (they are not related, just examples), I think both variants
should be included.

I think both are good, but I especially like how the HTML one also
for each fix points to the relevant bug description. The text for
these should possibly come from the "svn log" command, which may make
people considering writing good explanations. I'm not sure what is the
ASF practice here.

/Jonas