I agree that it is time to upgrade to the latest version of RDF4J and that this 
should involve a major version increment.

To provide time for Rya users to upgrade, I think that we should support a 3.x 
branch and a 4.x branch for the near future (minimally the end of the calendar 
year) and then reevaluate continuing to maintain 3.x.

Best Regards,

Jen

Jennifer Brown
Project Manager, Semantic Technologies
PARSONS
1911 N. Fort Myer Dr. Ste 800
Arlington, VA 22209
Phone: (703) 797-3136
Fax: (703) 522-6310
jennifer.br...@parsons.com<mailto:jennifer.br...@parsons.com>
www.parsons.com

On Apr 9, 2018, at 12:30 PM, Chilton, Kevin 
<kevin.chil...@parsons.com<mailto:kevin.chil...@parsons.com>> wrote:

Hey Rya devs,

I'd like to get PR #245 (RYA-405) pulled in.  This is a pretty big dependency 
change, and should probably involve a major version increment to 4.0.0.  Could 
we get a discussion going on the devlist about if we want to support a 3.x 
branch and a 4.x branch going forward, or just update master to 4.x.

Thanks,
Kevin

NOTICE: This email message and all attachments transmitted with it may contain 
privileged and confidential information, and information that is protected by, 
and proprietary to, Parsons Corporation, and is intended solely for the use of 
the addressee for the specific purpose set forth in this communication. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any reading, dissemination, distribution, copying, or other use of this 
message or its attachments is strictly prohibited, and you should delete this 
message and all copies and backups thereof. The recipient may not further 
distribute or use any of the information contained herein without the express 
written authorization of the sender. If you have received this message in 
error, or if you have any questions regarding the use of the proprietary 
information contained therein, please contact the sender of this message 
immediately, and the sender will provide you with further instructions.

Reply via email to