hrm. Ok. I do not think the code is quite ready to be tagged just yet. I am going to move "release-1.0.2" to "branches" and check it out. We should not create tags under "releases" until we have a thumbs-up consensus.
-- james On Tue, Jan 27, 2009 at 3:44 PM, scott comer (sccomer) <[email protected]> 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 > >
