Re: [Bigdata-developers] 2.2 Release date?

[Kevin F. <kf...@ar...>]

Hi Brad,

Thanks for the info. I'll certainly take the RC out for a spin.

All the best,
Kevin


On 1/3/17 15:41, Brad Bebee wrote:
> Kevin,
>
> Thank you. Yes, we are working towards having a release in Q1 for 2.2,
> which will include some fixes made for the Wikidata query service. The
> move to RDF 1.1 also has some potential data migration.
>
> If you haven't already, we'd encourage you to try the 2.2.0 RC and let
> us know if you have any issues:
>  https://github.com/blazegraph/database/releases/tag/BLAZEGRAPH_RELEASE_CANDIDATE_2_2_0.
>
> Thanks, --Brad
>
> On Tue, Jan 3, 2017 at 12:05 PM, Kevin Ford <kf...@ar...
> <mailto:kf...@ar...>> wrote:
>
>     Dear All,
>
>     I might be looking in all the wrong places, but is there any information
>     about when Blazegraph 2.2 will be released? We're excited to see the
>     sesame upgrade that will bring RDF 1.1 support.
>
>     I've found the 2.2 RC but nothing else.
>
>     All the best,
>     Kevin
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     _______________________________________________
>     Bigdata-developers mailing list
>     Big...@li...
>     <mailto:Big...@li...>
>     https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>     <https://lists.sourceforge.net/lists/listinfo/bigdata-developers>
>
>
>
>
> --
> _______________
> Brad Bebee
> CEO, Managing Partner
> SYSTAP, LLC
> e:  be...@sy... <mailto:be...@sy...>
> m: 202.642.7961
> f:  571.367.5000
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP, LLC.  Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please
> notify the sender by reply email and permanently delete all copies of
> the email and its contents and attachments.