Release Plans

[Karsten Thoms]

Hi all,

Jos and I had yesterday organized a BoF session at CodeGeneration 2013 and talked about Spray. We both were very busy in the past with other things, but want to push Spray again a bit further. Therefore we think it is especially important to come along with a new release soon, and regular releases afterwards. We will take the current state, maybe fixing some urgent issues. For the next release, 0.5.0, we should pay special attention to the documentation, making sure that it is updated and that what is decribed there actually works.

I will start soon working on some build issues. Especially I find it important that we will provide pre-built IDEs for Spray Developers and Spray Users, with different set of features bundled. I received a nice build package from the Xtext guys today that I will add to Spray.

We think that we should release 0.5.0 in May, and then come up with a 0.6.0 when Eclipse Kepler was released, so release date mid of July for Spray.

BTW: We again got some attention on Spray at the conference.

Best wishes,
~Karsten

[Jörg Reichert]

Hi Karsten,

glad to read that. There is already a ticket for making the 0.5 release,
http://code.google.com/a/eclipselabs.org/p/spray/issues/detail?id=155,
also mentioning the notion of product builds. I got stucked a bit with
fixing the tests.

For documentation we can have a look at Xdoc
(https://github.com/RvonMassow/xDoc) (again) and/or Mylyn Intent
(http://wiki.eclipse.org/Intent) for avoiding outdated documentation
(see also
http://www.eclipse.org/intent/pages/transcripts/2012_AgileALMConnect/img0.html,
http://jaxenter.com/eclipse-intent-being-agile-does-not-mean-being-short-sighted-45856.html).

For Kepler/Xtext/Xtend 2.4 version of Spray there is a branch "kepler".
Currently the issues with the builder in the IDE (remove Guava 11 from
target platform) and the changed Xbase Linking behavior (if this is the
cause for the failing example project builds) should be fixed.

When all infrastructure related stuff is fixed, we should come up with a
road map for choosing and prioritising the next features (use cases) to
implement (filed once a issue for that:
http://code.google.com/a/eclipselabs.org/p/spray/issues/detail?id=165).
To support this a started with Yakindu Requirements project on a branch
("yakindu_requirements") (see generated spec so far:
http://spray.eclipselabs.org.codespot.com/git-history/yakindu_requirements/docs/org.eclipselabs.spray.doc.requirements/output/specconfig/SprayReport/SprayReport.pdf).
To learn more about Yakindu Requirements:
http://www.yakindu.com/requirements/

Joerg

[Karsten Thoms]

Hi Jörg!

Thanks for the detailed update. I will start getting on overview tomorrow, and then do from time to time something besides my project work.

~Karsten

> --
> You received this message because you are subscribed to the Google Groups "spray-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to spray-dev+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>