Sometime later today, I intend to make [the current snapshots abcl-1.1.0-rc-2][rc-2] the functional base for [ABCL-1.1.0][].
Please speak up loud if we shouldn't do this.
We will have a maintenance release within 30 days.
[rc-2]: https://code.google.com/p/abcl-dynamic-install/downloads/list [ABCL-1.1.0]: http://trac.common-lisp.net/armedbear/milestone/1.1.0
For the Mgmt., Mark evenson@panix.com
P.S. Multiple cryptographic signatures when tag is created would be a nice thing.
07.12.2012, 13:31, "Mark Evenson" evenson@panix.com:
Sometime later today, I intend to make [the current snapshots abcl-1.1.0-rc-2][rc-2] the functional base for [ABCL-1.1.0][].
Please speak up loud if we shouldn't do this.
We will have a maintenance release within 30 days.
For the Mgmt., Mark evenson@panix.com
P.S. Multiple cryptographic signatures when tag is created would be a nice thing.
IMHO #274 deserves to be considered. It's a hungup during compilation.
On 12/7/12 2:18 PM, Anton Vodonosov wrote:
07.12.2012, 13:31, "Mark Evenson" evenson@panix.com:
Sometime later today, I intend to make [the current snapshots abcl-1.1.0-rc-2][rc-2] the functional base for [ABCL-1.1.0][].
Please speak up loud if we shouldn't do this.
We will have a maintenance release within 30 days.
For the Mgmt., Mark evenson@panix.com
P.S. Multiple cryptographic signatures when tag is created would be a nice thing.
IMHO #274 deserves to be considered. It's a hungup during compilation.
It is not the only Quicklisp distributed properties.
We're at a chicken and egg type impasse with Quicklisp distributed implementors: they wish to test against a known, securely versioned released; we need them to add #+abcl conditionals.
As soon as [#274][] gets addressed--maybe a hook on a watcher that catches hung ASDF operations?--on abcl-1.2.0-dev aka. [trunk][], we'
[#274]: http://trac.common-lisp.net/armedbear/ticket/274 [trunk]: http://svn.common-lisp.net/armedbear/trunk/abcl/
Mark evenson@panix.com for urn:abcl.org .
07.12.2012, 20:30, "Mark Evenson" evenson@panix.com:
On 12/7/12 2:18 PM, Anton Vodonosov wrote:
07.12.2012, 13:31, "Mark Evenson" evenson@panix.com:
Sometime later today, I intend to make [the current snapshots abcl-1.1.0-rc-2][rc-2] the functional base for [ABCL-1.1.0][].
Please speak up loud if we shouldn't do this.
We will have a maintenance release within 30 days.
[rc-2]: https://code.google.com/p/abcl-dynamic-install/downloads/list [ABCL-1.1.0]: http://trac.common-lisp.net/armedbear/milestone/1.1.0
For the Mgmt., Mark evenson@panix.com
P.S. Multiple cryptographic signatures when tag is created would be a nice thing.
IMHO #274 deserves to be considered. It's a hungup during compilation.
It is not the only Quicklisp distributed properties.
We're at a chicken and egg type impasse with Quicklisp distributed implementors: they wish to test against a known, securely versioned released; we need them to add #+abcl conditionals.
As soon as [#274][] gets addressed--maybe a hook on a watcher that catches hung ASDF operations?--on abcl-1.2.0-dev aka. [trunk][], we'
Mark evenson@panix.com for urn:abcl.org .
Is this unfinished message?
On 12/8/12 12:38 AM, Anton Vodonosov wrote:
07.12.2012, 20:30, "Mark Evenson" evenson@panix.com:
On 12/7/12 2:18 PM, Anton Vodonosov wrote:
07.12.2012, 13:31, "Mark Evenson" evenson@panix.com:
Sometime later today, I intend to make [the current snapshots abcl-1.1.0-rc-2][rc-2] the functional base for [ABCL-1.1.0][].
Please speak up loud if we shouldn't do this.
We will have a maintenance release within 30 days.
For the Mgmt., Mark evenson@panix.com
P.S. Multiple cryptographic signatures when tag is created would be a nice thing.
IMHO #274 deserves to be considered. It's a hungup during compilation.
It is not the only Quicklisp distributed properties.
We're at a chicken and egg type impasse with Quicklisp distributed implementors: they wish to test against a known, securely versioned released; we need them to add #+abcl conditionals.
As soon as [#274][] gets addressed--maybe a hook on a watcher that catches hung ASDF operations?--on abcl-1.2.0-dev aka. [trunk][], we'
Mark evenson@panix.com for urn:abcl.org .
Is this unfinished message?
It certainly got garbled somehow!
What I meant to point out is that one of the goals of abcl-1.1.0 was to get it released so that Quicklisp 2012-12 can hopefully release versions of CLOSER-MOP, CFFI, and Hunchentoot with the necessary patches.
As such, that has a higher priority than fixing the compiler for com.informatimago.common-lisp.cesarum. Unless there is a patch.
ABCL 1.1.0 is "released" in that binary and source artifacts are available.
TODO: add multiple cryptographic signatures in [releases/1.1.0][], write up the release notes, update the canonical site with download links.
When signing the release, committers can verify the chain with [my md5sums][1].
[releases/1.1.0]: http://svn.common-lisp.net/armedbear/public_html/releases/1.1.0/ [1]: http://abcl-dynamic-install.googlecode.com/files/abcl.org-20121207a.urn.md5
Now if I can just figure out how to help guess my PGP passphrase…
Mark Evenson evenson@panix.com writes:
What I meant to point out is that one of the goals of abcl-1.1.0 was to get it released so that Quicklisp 2012-12 can hopefully release versions of CLOSER-MOP, CFFI, and Hunchentoot with the necessary patches.
I was kind of hoping to do that tomorrow. My preference is to release on the first weekend of each month. November was an exception.
Zach
On 12/9/12 3:57 AM, Zach Beane wrote:
Mark Evenson evenson@panix.com writes:
What I meant to point out is that one of the goals of abcl-1.1.0 was to get it released so that Quicklisp 2012-12 can hopefully release versions of CLOSER-MOP, CFFI, and Hunchentoot with the necessary patches.
I was kind of hoping to do that tomorrow. My preference is to release on the first weekend of each month. November was an exception.
For ABCL, you should be update to working CFFI and Hunchentoot for December 2012 Quicklisp fairly easily, the necessary patches for abcl-1.1.0 have already been commited to the respective repositories.
[cffi]: https://github.com/easye/cffi/commits/master [hunchentoot]: https://github.com/easye/hunchentoot/commits/master
For CLOSER-MOP, everything reported has been fixed so that abcl-1.1.0 works well, but the maintainer has expressed the desire for a released version of ABCL before the source is patched. That condition was met on December 7. 2012 but the maintainer has been busy with moving homes, and then catching up from moving. So, unless there is some fancy footwork between you and Pascal, and/or you patch CLOSER-MOP further than its repository (probably a bad idea in general), this will have to wait until 2013, or a supplemental December 2012 Quicklisp.
Note that the [bug affecting com.informatimago.common-lisp.cesarum][#274] has not (unfortunately) been addressed in ABCL-1.1.0.
[#274]: http://trac.common-lisp.net/armedbear/ticket/274
We'll be around in email and IRC today to provide any assistance that we can.
Mark Evenson evenson@panix.com writes:
On 12/9/12 3:57 AM, Zach Beane wrote:
Mark Evenson evenson@panix.com writes:
What I meant to point out is that one of the goals of abcl-1.1.0 was to get it released so that Quicklisp 2012-12 can hopefully release versions of CLOSER-MOP, CFFI, and Hunchentoot with the necessary patches.
I was kind of hoping to do that tomorrow. My preference is to release on the first weekend of each month. November was an exception.
For ABCL, you should be update to working CFFI and Hunchentoot for December 2012 Quicklisp fairly easily, the necessary patches for abcl-1.1.0 have already been commited to the respective repositories.
I usually pull those projects from releases, and it doesn't look like releases with ABCL updates are available yet.
Zach
All the [steps involved in releasing ABCL 1.1.0][1] have been completed.
A [provisional draft of release notes has been published][2]. At this point, I find looking at the [abcl 1.1.0 Milestone in Trac][1.1.1] and especially the [closed tickets for 1.1.0][3] to give the best overview of what we have accomplished in the past year.
[1]: http://trac.common-lisp.net/armedbear/wiki/ReleaseSteps [2]: http://common-lisp.net/project/armedbear/release-notes-1.1.0.shtml
[1.1.0]: http://trac.common-lisp.net/armedbear/milestone/1.1.0 [3]: http://trac.common-lisp.net/armedbear/query?status=closed&group=resoluti...
The three major drivers in ABCL 1.1.0 for running Quicklisp systems were CLOSER-MOP, [cffi][], and [Huchentoot][]. for which patches are needed to actually run, so we haven't currently met this criteria. We will try our hardest for this to be the case in [1.1.1][], provisionally due for New Year's Eve.
[cffi]: https://github.com/easye/cffi/commits/master [hunchentoot]: https://github.com/easye/hunchentoot/commits/master
I am current awaiting the 2012-12 Quicklisp--take your time, Zach. I've got lots of other stuff to do--elease to actually write up an email/comp.lang.lisp posting announcing the release while updating the provisional release notes, but I don't think such a step should detract from anyone wishing to use the implementation at this point.
Depending on what happens in 2012-12 Quicklisp, I am possibly thinking of extending the QUICKLISP-ABCL contrib to somehow "overlay" the corrected versions of CLOSER-MOP, CFFI, Hunchentoot, and other ASDF systems that need patches to work, by creating a "QUICKLISP-ABCL" distribution, so that the necessary coordination with Quicklisp packaged systems can occur in a much more centralized and prompt manner.
For abcl-1.1.1 the procedure is pretty simple: commit/submit patches to [trunk][], and I'll make sure to backport them. We will then release abcl-1.1.1 at the end of December, and hopefully all the Quicklisp drivers can patch for Quicklisp 2013-01. Now that I have [most of the basics in RDF][abcl.rdf], automating the procedure should start to be feasible.
[1.1.1]: http://trac.common-lisp.net/armedbear/milestone/1.1.1 [abcl.rdf]: http://svn.common-lisp.net/armedbear/trunk/abcl/abcl.rdf
Thanks, Mark evenson@panix.com
armedbear-devel@common-lisp.net
-
Anton Vodonosov -
Mark Evenson -
Zach Beane