Which reminds me, I have a pull request ready to go. It fixes a couple dependencies. david.
-----Original Message----- From: Puja Valiyil <puja...@gmail.com> Sent: Tuesday, January 7, 2020 8:06 PM To: dev@rya.apache.org Subject: [EXTERNAL] Re: Rya release as TLP I think this is a great idea! I think removing incubating and upgrading versions is a good target. It would also be good to start another discussion to rank features people would like to see implemented and make more progress on a project road map. On Tue, Jan 7, 2020 at 7:54 PM Adina Crainiceanu <ad...@usna.edu> wrote: > Hi all, > > It would be good to have a release of Rya as TLP soon. We usually had > releases around March. Last year was a little later, in the summer. > > I think we have a few options: > 1) We could just update all references to the project to remove > i"incubating" and have a 4.0.1 release very soon. > 2) We could do the updates in 1 and also try to update the > dependencies, in particular Accumulo. We would need more testing for this one. > > Anyone volunteering as release manager? > Thoughts on what should be in next release and when? > > Thanks, > Adina > > -- > Dr. Adina Crainiceanu > Associate Professor > Computer Science Department > United States Naval Academy > 410-293-6822 > ad...@usna.edu > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.usna.edu_Users > _cs_adina_&d=DwIBaQ&c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10&r=ru > y1rriFBFoeOJvvQWwN1h8AcdSNT3EVLrdVl7pr-iA&m=Lpbt9vh57-RxuAuWyumzQbGYnv > hIE0d3XwIKnT3mnqg&s=BM4_gqUFQgjLssWy23rJemIY5rb1gqchA3lp1KrxJ2w&e= > 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.
