I haven't received any feedback about the build yet so I'm assuming it's
worked for everyone, right? ;)
Erik Huelsmann wrote:
> There's a lot of code in the repository which hasn't been released yet
> - some of which is sitting there for years now - so, it would be great
> to make that code part of an official release.
Does anyone want to write up a changelog of the most important changes
for the upcoming release? Nothing fancy, but it will take a little
spelunking of the svn log. See:
> I'd also like to stress that separating the trees as we have done now,
> doesn't need to mean that ABCL can't be integrated or even intergrated
> *more* into J; it just means it lives in its own library and we'll
> need to start documenting what APIs can be depended upon and which
> ones can't.
Indeed, having a stable abcl API will be a good thing!
> Also: the purpose of ABCL is much broader than just being a scripting
> language to J. Being a separate tree makes that fact very explicit and
> works better as a marketing tool than being hidden in the tree of a
> different goal (project?) entirely.
Hopefully making a new release as it's own project will encourage others
to start hacking on J again. Peter has done an excellent job with J!
> Thanks for stepping up!
> If you need anything, please speak up, maybe we can be of service. I
> sure hope others speak up like you did and give J the bright future it
> so deserves.
Erik, can you do a build and post a release candidate of the source and
binaries for folks to download? If there are no complaints after a week
or so, we can tag it as 0.22.0, put a new build up, and update the
various version strings on the website.
How exciting to have a new J release after 4+ years!