oh, by virtue of the evil plan powers vested in me, i've got a virtual
lock on the trunk while
i change the package names. (click, thunk)
http://www.cksinfo.com/clipart/construction/tools/locks/lock.png
scott out
scott comer (sccomer) wrote:
i've created a branch for etch release 1.0.2.
https://svn.apache.org/repos/asf/incubator/etch/releases/release-1.0.2/
trunk is now open for 1.1 activities, the first of which will be the
resolution of:
ETCH-22: Change Java (other?) package names to org.apache.etch
https://issues.apache.org/jira/browse/ETCH-22
the package name change will break code compatibility, but a recompile
with the 1.1 compiler should be sufficient to resolve most issues.
wire compatibility will not be compromised (except where any etch
services' module name changes). so be it.
no other planning for 1.1 has occurred yet. to kick the ball, ideas
for 1.1:
c binding (nearly done)
python binding (in progress)
reference etch services (naming, configuration, authentication,
logging, router)
high performance transport using selectors (ETCH-10, ETCH-20)
interoptester (ETCH-15)
ideas? thoughts?
scott out
