Yes, we spoke about putting back some kind of roadmap page that was in the old website (and I have an action to make some progress in that regard). But we didn't want to make the roadmap unrealistic either, so we want to get the wording right.

Cheers, Paul.

On Fri, Jan 29, 2016 at 5:59 AM, Clark Richey <clark@factgem.com> wrote:
Thanks. I just haven't been able to find much information in development status since the website changes occurred and I was vaguely concerned. 

Sent from my iPhone

Clark Richey

CHIEF TECHNOLOGY OFFICER

  240.252.7507
  CLARK@FACTGEM.COM
  WWW.FACTGEM.COM






This message and any included attachments are property of FactGem and its affiliates, and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail. Thank you.


On Jan 28, 2016, at 14:56, Paul King <paulk@asert.com.au> wrote:

We are still working on getting 2.5 out the door. Only a little bit of experimental/spike work has gone in regards to 3.0 .

Cheers, Paul.

On Fri, Jan 29, 2016 at 5:22 AM, Clark Richey <clark@factgem.com> wrote:

Hi! Does anyone have any information on the status of Groovy 3.0? Thanks!

Sent from my iPhone


Clark Richey

CHIEF TECHNOLOGY OFFICER

  240.252.7507
  CLARK@FACTGEM.COM
  WWW.FACTGEM.COM






This message and any included attachments are property of FactGem and its affiliates, and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail. Thank you.