I would like to go on and to develop my extensions on GitHub as separate
project. Later, if they is an existing user community, I can contribute
them. So for me it would be fine if the builder and JSON module would be
removed from the tree.
Oliver
Am 12.02.15 um 18:21 schrieb Anatole Tresch:
I also wanted to raise that question (I was some days sick, so you were
faster ;-D )...
If extensions must be moved out to a separate tree. I think some extensions
already work qute well (resolver( and just need some tests and docs,
whereas many others definitively require more time.
So if we can separate extensions somehow (even perhaps manage in a seperate
source tree), I would agree that API and core are rather stable.
Things to be done:
- Checking for accurate Javadocs
- Checking improving API/Core Documentation
- Ensure we have a release build, which also updates our web page on
successful build with Javadocs, asciidocs (may be coping the generated
html...? )
Ensuring the delivery tool chain works ;)
Best
Anatole
2015-02-12 18:06 GMT+01:00 Romain Manni-Bucau <[email protected]>:
IMO for core we can release (I'd like to release a 0.1-alpha but with
our incubating it makes too long ;))
for extensions I think it is too early so maybe we should remove them
from main tree and release them separately when someone need it in
alpha or experimental until we manage to discuss them and integrate
them back in main tree
wdyt?
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-02-12 18:03 GMT+01:00 Oliver B. Fischer <[email protected]>:
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E [email protected]
S oliver.b.fischer
J [email protected]
X http://xing.to/obf
