Thank you for volunteering Adina! As far as Davids questions below, I do not feel there are any breaking changes thus far. However, we do have a breaking change in the pipeline with the upgrade to the latest version of rdf4j. I was thinking that any releases after that pr is merged be on a 4.0.0 series.
Since I know many users may not be able to immediately upgrade, does it also make sense to maintain a 3.2.x branch? I know a few users of rya that will for not be able to update deployed instances of rya to a 4.0.0 version anytime soon but may need to submit bug fixes/security patches/minor features against the current 3.2.x baseline. How do other projects handle this? I think maintaining two branches makes sense but I would really like to hear everyone's thoughts on this. Sent from my iPhone > On Nov 14, 2017, at 9:59 PM, Adina Crainiceanu <[email protected]> wrote: > > I volunteered some time ago for the 3rd release. It is that time, so I > guess I'll be the next Release Manager unless someone else really wants the > role. > > Adina > > >> On Tue, Nov 14, 2017 at 1:23 PM, David Lotts <[email protected]> wrote: >> >> We soon will have plenty of new features and fixes for another release, if >> we don't already. So I'd like to kick off some discussion. Requesting >> comments for any of these: >> >> 1- When shall we target the next release? Start now? >> >> 2- Can we get a volunteer to be the next Release Manager? >> There are a couple of us now listening to this list that can help you reify >> the instructions[1], which are looking pretty good these days. I'd be glad >> to walk you through it. >> >> 3- Our current release is 3.2.11, shall we call this one 3.2.12 ? >> Any breaking changes? v3.3.0 or v4.0.0 ? >> >> david. >> >> [1] https://cwiki.apache.org/confluence/display/RYA/How+To+Release+Rya >> > > > > -- > Dr. Adina Crainiceanu > Associate Professor > Computer Science Department > United States Naval Academy > 410-293-6822 > [email protected] > http://www.usna.edu/Users/cs/adina/
