[armedbear-devel] Moving toward a release
Just writing a note that it's time to move toward a release. Over the past days a number of fixes have been committed, especially with respect to pathname code, but in other areas as well. If you have time to excersize some testing, please do and report any failure (or succes!). Before branching the 0.20.x branch, I hope to be able to see 2 additional changes: * finishing METACLASS tests - this is my action item, but is more or less blocked by the next item * ABCL being able to run its own tests - on Windows, this is currently broken by one of the Pathname changes; if you have time to contribute (and hence take some weight off Mark's shoulders) please do! Once again, any feedback appreciated. Bye, Erik.
On 5/2/10 10:18 PM, Erik Huelsmann wrote: […]
* ABCL being able to run its own tests - on Windows, this is currently broken by one of the Pathname changes; if you have time to contribute (and hence take some weight off Mark's shoulders) please do!
This issue has been partially addressed in [r12562][1]. "partially" because while the immediate problem was fixed (the need to always use '/' as the directory path separator in URLs), the tests still don't run due to the incorrect introduction of the Windows drive letter in URLs. Probably an equally trivial change in Pathname.getNamestring(), but I'm out of time for right now to address this, so I'm still open for help here. [1]: http://trac.common-lisp.net/armedbear/changeset/12652 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On 5/3/10 3:49 PM, Mark Evenson wrote:
[…] "partially" because while the immediate problem was fixed (the need to always use '/' as the directory path separator in URLs), the tests still don't run due to the incorrect introduction of the Windows drive letter in URLs. Probably an equally trivial change in Pathname.getNamestring(), but I'm out of time for right now to address this, so I'm still open for help here.
The incorrect inclusion of the default device for URL-PATHNAME [has been fixed][1], but the network loading tests still fail until I update the remote resource on Googlecode to update to the new FASL. Since Google Code requires that uploaded files cannot be changed (a pretty reasonable constraint in order to have distributed caching), I will have to include the date in the URL or something. [1]: http://trac.common-lisp.net/armedbear/changeset/12653 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On 5/5/10 7:37 AM, Mark Evenson wrote:
[…] but the network loading tests still fail until I update the remote resource on Googlecode to update to the new FASL. Since Google Code requires that uploaded files cannot be changed (a pretty reasonable constraint in order to have distributed caching), I will have to include the date in the URL or something.
This change has [been made as part of r12654][1], which also addresses other outstanding problems in the JAR-PATHNAME tests. As far as I know, this issue has been resolved. Please provide further feedback if someone finds this not to be the case. [1]: http://trac.common-lisp.net/armedbear/changeset/12654 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
Any chance of including support for ABCL in the OSGI environment in this release? -Alan On Thu, May 6, 2010 at 3:15 AM, Mark Evenson <evenson@panix.com> wrote:
On 5/5/10 7:37 AM, Mark Evenson wrote:
[…] but the network loading tests still fail until I update the remote resource on Googlecode to update to the new FASL. Since Google Code requires that uploaded files cannot be changed (a pretty reasonable constraint in order to have distributed caching), I will have to include the date in the URL or something.
This change has [been made as part of r12654][1], which also addresses other outstanding problems in the JAR-PATHNAME tests.
As far as I know, this issue has been resolved. Please provide further feedback if someone finds this not to be the case.
[1]: http://trac.common-lisp.net/armedbear/changeset/12654
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
_______________________________________________ armedbear-devel mailing list armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
On 5/6/10 3:39 PM, Alan Ruttenberg wrote:
Any chance of including support for ABCL in the OSGI environment in this release?
Unfortunately not, unless someone steps up with eworking code. I'm still working on the problems with the Protege environment you have delineated, but OSGi is a weird beast, so I'm moving rather slowly. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
participants (3)
-
Alan Ruttenberg -
Erik Huelsmann -
Mark Evenson