I've created the 0.26 release branch after updating CHANGES.
If there are no further objections, I'll continue the release process by signing the release.
It'd be very helpful if one of the other committers can update the webpages, as I won't have time to do that today or tomorrow.
Bye,
Erik.
On Sun, Jul 10, 2011 at 12:49 AM, ehuelsmann@common-lisp.net wrote:
Author: ehuelsmann Date: Sat Jul 9 15:49:04 2011 New Revision: 13381
Log: Update CHANGES with 0.26.0 items.
Modified: trunk/abcl/CHANGES
Modified: trunk/abcl/CHANGES
============================================================================== --- trunk/abcl/CHANGES Fri Jul 8 01:40:37 2011 (r13380) +++ trunk/abcl/CHANGES Sat Jul 9 15:49:04 2011 (r13381) @@ -1,3 +1,91 @@ +Version 0.26.0 +============== +svn://common-lisp.net/project/armedbear/svn/tags/0.26.0/abcl +(?? ???? 2011)
+Features +--------
- Add support for weak reference objects
- Add support for finalizers on LispObject derived classes
- Upgrade ASDF to 2.0.16.1
- #\ reader macro now understands #\uNNNN as unicode codepoints
- JAVA:JRESOLVE-METHOD returns same method as would have been
- called by JAVA:JCALL with the same arguments
- Ant 'update' target to upload application to Google App Engine
- Simple RUN-PROGRAM implementation
- Support for custom slot definitions according to AMOP
- New JAVA:*JAVA-OBJECT-TO-STRING-LENGTH* variable to control pretty
- printing of Java objects
- JSS - more dynamic Lisp/Java FFI - (
http://lsw2.googlecode.com/svn/trunk)
- imported
- (REQUIRE :ABCL-CONTRIB) adds 'abcl-contrib.jar' to the ASDF search path
- Support for weak references in hash tables through a :WEAKNESS keyword
- argument to MAKE-HASH-TABLE; with SYS:HASH-TABLE-WEAKNESS for
inspection
- Support for loading ASDF systems from JAR archives
- Fast SHA1, SHA256 and SHA512 cryptographic hashes for files
- Beginnings of a manual
- ABCL/ASDF integration with Maven provided systems
- ASDF-JAR:PACKAGE function to package ASDF systems into JARs
+Changes +=======
- Reduced code size in the compiler by changing COMPILE-TEST-FORM
- Enhanced SLIME inspector for JAVA:JAVA-OBJECT
- Reimplemented MERGE-PATHNAMES
- TRANSLATE-PATHNAME aligned with SBCL's behaviour if version is wild
- Removed PRINT-OBJECT methods duplicating Java side code
- Refactored code in SYSTEM:ZIP function
- Allow JCOERCE to convert any number to java.lang.Byte (using
- its two's complement)
- Replace MAKE-IMMEDIATE-OBJECT with +NULL+, +TRUE+ and +FALSE+ constants
- (the only supported ones)
- Better separation between java-collections package and Java FFI
- JAVA:ADD-TO-CLASSPATH is now a generic function
+Fixes +=====
- Google App Engine example fixed
- MAKE-PATHNAME erroneously merges directories as in MERGE-PATHNAME
- Pretty printer routines using SYS:OUTPUT-OBJECT with GRAY-STREAM
- Value of *PRINT-CASE* affects file (to FASL) compilation
- MAKE-PATHNAME ignores version in :DEFAULTS
- URI decoding algorithm in Pathname.java
- JNEW-ARRAY-FROM-ARRAY should create byte[] arrays
Version 0.25.0
svn://common-lisp.net/project/armedbear/svn/tags/0.25.0/abcl
armedbear-cvs mailing list armedbear-cvs@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-cvs
On 10 July 2011 01:53, Erik Huelsmann ehuels@gmail.com wrote:
I've created the 0.26 release branch after updating CHANGES. If there are no further objections, I'll continue the release process by signing the release. It'd be very helpful if one of the other committers can update the webpages, as I won't have time to do that today or tomorrow.
I ran ansi-test baselines on 0.25, which went ok, but running interpreted tests on 0.26 bombed with a stack overflow. I'm running compiled tests now, then I can see more closely what's going on...
On 11 July 2011 18:58, Ville Voutilainen ville.voutilainen@gmail.com wrote:
I ran ansi-test baselines on 0.25, which went ok, but running interpreted tests on 0.26 bombed with a stack overflow. I'm running compiled tests now, then I can see more closely what's going on...
Same result with compiled, which is not surprising. Some sort of a print-recursion-loop.
On 7/10/11 12:53 AM, Erik Huelsmann wrote:
I've created the 0.26 release branch after updating CHANGES.
If there are no further objections, I'll continue the release process by signing the release.
It'd be very helpful if one of the other committers can update the webpages, as I won't have time to do that today or tomorrow.
Unfortunately, the abcl-0.26.0-src release won't build because that archive is missing the newly added org.armedbear.lisp.protocol package.
[Fixed and backported to the abcl-0.26.x branch][1].
[1]: http://trac.common-lisp.net/armedbear/changeset/13391
My vote would be to figure out the stack overflow reported in [ticket #154][2] as well as whatever is causing the ansi-interpreted errors that Ville is noticing, and move to releasing an abcl-0.26.1.
[2]: http://trac.common-lisp.net/armedbear/ticket/154
Erik is on his first day of vacation, and probably has limited upload bandwidth, so we may be a bit constrained here.
On 11 July 2011 20:51, Mark Evenson evenson@panix.com wrote:
My vote would be to figure out the stack overflow reported in [ticket #154][2] as well as whatever is causing the ansi-interpreted errors that Ville is noticing, and move to releasing an abcl-0.26.1.
ansi-interpreted and ansi-compiled, and I agree, let's not push regressions out, we can afford waiting for a while, even two weeks if need be.
Hi,
On Mon, Jul 11, 2011 at 7:51 PM, Mark Evenson evenson@panix.com wrote:
On 7/10/11 12:53 AM, Erik Huelsmann wrote:
I've created the 0.26 release branch after updating CHANGES.
If there are no further objections, I'll continue the release process by signing the release.
It'd be very helpful if one of the other committers can update the webpages, as I won't have time to do that today or tomorrow.
Unfortunately, the abcl-0.26.0-src release won't build because that archive is missing the newly added org.armedbear.lisp.protocol package.
[Fixed and backported to the abcl-0.26.x branch][1].
My vote would be to figure out the stack overflow reported in [ticket #154][2] as well as whatever is causing the ansi-interpreted errors that Ville is noticing, and move to releasing an abcl-0.26.1.
Erik is on his first day of vacation, and probably has limited upload bandwidth, so we may be a bit constrained here.
Yea, it'd be very convenient for me to fix any remaining issues and go for a 0.26.1 in 2 weeks. Also because my signing key is most easily operated at home.
Let's take some time to solve these regressions and scrap the brown paper bag release :-)
Bye,
Erik.
armedbear-devel@common-lisp.net