Hi list,

I have a couple of quick questions. Is there a planned Wonder release that includes the fix to issue #615 (https://github.com/wocommunity/wonder/issues/615)? And is the master branch generally considered stable?

Thanks in advance.

Regards,
Bogdan Zlatanov

If not, we'll help ourse

On 10/02/2014 16:24, Johann Werner wrote:
Hi list,

it has been a long time but finally Wonder 6.1.1 is officially out. Point your 
browser to the release page on github 
https://github.com/wocommunity/wonder/releases to get everything you need: a 
changelog and all artifacts you would get from the wocommunity jenkins server.

Beginning with this version of the frameworks Wonder applications will log out 
that version number on startup. This is amongst others to make it easier for 
getting help from the mailing list as to provide more information on your WO 
setup. The version number reported on the Wonder Javadoc documentation will 
reflect that version number too so you can be sure looking at the documentation 
matching your version.

Thanks for all those who contributed!


For those using their own jenkins servers:
Building the documentation put the Javadocs into a directory "dist/wonder-6.0/Documentation". That 
path changed to "dist/wonder/Documentation" without the "-6.0" part. You should check the 
settings of the Javadoc publisher plugin if that path is still matched or update it accordingly.


  _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/bogdan.zlatanov%40gmail.com

This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to