Great work from Lasse so far, lots of code review, issue tracker action and
pull requests starting to get pulled in quite quick. All of them were
addressed, now we sent a couple of more from the Adminotech/Meshmoon team
your way so you don't get bored :)

I'd like to mention that we tried to contact you when we were thinking what
version should our next release be. We decided to jump to 2.5.0.0 just on
the fact that the wire protocol had this quite major change, not code wise,
but its impact is big at least for us. We were trying to consult so we
could sync up the Meshmoon release with the next realXtend release version
numbering. Hopefully you feel there is a justification to call the next one
2.5.0.0, ofc it can include lots of other things still before that is done,
but that would keep it about in sync with us.

All the latest Tundra code and our bugfixes pull request is in todays
released Meshmoon Rocket 2.5 (hit check for updates on your client). I will
send a separate post telling people a bit more about it later.

Keep up the good work Lasse, all hail the new king :)

Best regards,
Jonne Nauha
Meshmoon developer at Adminotech Ltd.
www.meshmoon.com


On Tue, Mar 26, 2013 at 4:35 PM, "Lasse Öörni" <lasse.oo...@ludocraft.com>wrote:

> Hi all,
> this post is kind of overdue, but better late than never. I'm Lasse Öörni
> from LudoCraft, and for roughly a month I've been continuing Jukka's work
> as the lead architect and mergemaster for realXtend Tundra, taking care of
> merging pull requests to the codebase and coordinating the core
> development.
>
> In addition to the several bugfixes and improvements contributed by
> Stinkfist, cvetan, th3flyboy et al., some of the work already done this
> winter/spring has to do with the Tundra network protocol: from the next
> release onward (release date not set yet) it will be possible to add
> attributes to the Entity-Components without breaking wire protocol
> compatibility. Unfortunately Tundra 2.4.x and earlier will not understand
> this and need to be upgraded to be compatible.
>
> My personal plan is to continue to tackle the bug, performance and
> scalability issues in Tundra where possible, as well as to continue the
> experimental AngelScript integration work started by Jukka. The Tundra
> Android port also needs further attention to become truly usable (for
> reference, see issues labeled "Android" at
> https://github.com/realXtend/naali/issues)
>
> Whenever I'm working on Tundra, I'll also be hanging out at #realxtend-dev
> on freenode (look for nick "cadaver").
>
> Regards,
>
> Lasse
>
>
> --
> --
> http://groups.google.com/group/realxtend-dev
> http://wiki.realxtend.org
> http://dev.realxtend.org
> ---
> You received this message because you are subscribed to the Google Groups
> "realXtend-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to realxtend-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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


Reply via email to