We have been going through a recent project to identify and address any
issues left in epic4-1.1.*, with a mind towards a feature freeze and
then a stabilization and then a certification and production release.
ftp://ftp.epicsol.org/pub/epic/EPIC4-ALPHA/epic4-1.1.15.tar.gz
ftp://ftp.epicsol.org/pub/epic/EPIC4-ALPHA/epic4-1.1.15.tar.bz2
It has been suggested I should announce epic4-1.1.15, which is going to
be the basis for the FreeBSD port now. This is the first of hopefully
several "beta-quality" epic4-1.1.* releases. Note that this is not a
formal beta release, but rather is an alpha release that is stable, and
free of any real meaningful problems.
You are therefore invited to try this out if you want to be an early
adopter and see what epic4-2.0 is going to look like. If you find any
problems, now would be an excellent time to bring them up because I would
like to have a formal release candidate by December 1, and then we'll go
through the voting process and all that.
Obviously if you're using epic4-1.0.1 you should not be hasty to upgrade
because all epic4-1.1.* clients will break scripts written for epic4-1.0.1
for various reasons that all have to do with progress. You should as
always stick with the version of epic your script was targeted for. It is
always best to upgrade epic only when your scripts needs you to.
Jeremy
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list
