Was an issue with testsuite, fixed that.
Started the jenkins build that broke.
Will get the onejar out of the way while I wait.
Håvard
I’ve merged master —> develop where needed and created a release branch, mvn version and git tag.
Running the release deploy pipeline in jenkins now.
Will see how that goes.
Håvard
Hi Bart,
I realised last night that I forgotten. I’ll take a little look now before lunch and get back to you on email.
Håvard
Hi Håvard,
have you looked at the (milestone) release yesterday ? If not, we could start a M2 in a few hours if you want.
Best regards
Bart
Tuesday will probably be best. That will give me some time on Monday to try it out for myself.
We had some kind of “not slack” chat I remember. Maybe we can use that.
It’s very kind of you to help :) We can’t have time to code all the time. And we’re all doing this for fun. So important that it stays fun ;) Håvard Hi, Well, if needed I can do or help you with the release on Monday or Tuesday. I’ve been quite busy in the last weeks, sorry about that, still haven’t found the time to finish the RDFa parser (but as far as I’m concerned that could also be a 3.1 feature…) Best regards Bart I still haven’t done a release on my own since that video chat we had 2-3 years ago. So I think I can be up for trying for a milestone release, but I’ll leave a full release to you.
I’ll just keep plodding along with more SHACL stuff, so don’t worry about RDF4J while on your skiing holiday. I’ll try to keep it in mind so I don’t tag you for a review on GitHub ;) Fair point Havard. I've also realized that to do an official release on August 1 we'd have to kick off the review (and have the IP log approved and all that) by July 25 - which is in the middle of my skiing holiday. How about you (or perhaps Bart if he's available) put out another milestone build next week, and then official release can happen halfway August? Sorry to have to keep pushing back, but I'd rather do it right than having to rush things. As said though if you prefer to just do a milestone build and let me handle the final release, that's fine too :) We have sh:not support. This required a lot of changes to the ShaclSail. We’ve also merged master into develop. But I guess that this shouldn’t mean anything since I presume the M1 release is a new branch based on both master and develop. Due to the problems I had with building the first milestone, and the resulting delay, I think we will need to push back the entire release schedule by 2 weeks (also factoring in that I am on holiday for one week in late July). What this comes down to is that we aim to have a final release on August 1. We were also supposed to have a second milestone release right about now but I don't think we have much new things since the first milestone, so I suggest we keep that in reserve. Same here :-/ Currently looking into JDK 11, inching towards something that builds, also thanks to Håvard’s PR on japicmp Best regards Bart That’s very fine with me. I have conferences this week and I realized last night how tired that made me. I have been a bit swamped with other things lately and have not had as much time as I wanted to prep for the first milestone build. There's numerous pull requests still open that I think we may want to include in this first milestone, and I need to write some preliminary release notes as well. Ok with you if we postpone the milestone build to this weekend? That should give us a bit more time to get it in shape. Hi Jeen,
This looks great.
There are a lot of improvements that I’m eager to get out.
- SHACL supports updating shapes - SHACL single run validation is faster - more SHACL features - faster SPIN (~2x for most things, 1000x for initialization)
- SPIN works with the schema caching RDFS reasoner - SHACL in the server/workbench
Should we have code-freeze on develop on the 18th of June in preparation for M1?
Sounds sensible, let's do our best to make it stable. I'll also do my best to get all the backward-incompatible changes in there, so that we can give early adopters the best possible chance to anticipate changes they'll need to make. Håvard > On 6 Jun 2019, at 08:03, Jeen Broekstra < jeen.broekstra@xxxxxxxxx> wrote: > > hi all, > > here's my tentative schedule for the 3.0 release. Working backwards: > > - release: July 18 > - review complete: July 17 > - start of release review: July 10 > - get PMC approval: July 9 > - finalise release documentation: July 8 > - submit IP log: July 1 > - Milestone 2: July 4 > - Milestone 1: June 20 > > How does this look? Doable? I know we have a large list of Todo's still open but most of these are not backward-incompatible, so they don't have to block release. > > Cheers, > > Jeen > > > > > _______________________________________________ > rdf4j-dev mailing list > rdf4j-dev@xxxxxxxxxxx> To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/rdf4j-dev_______________________________________________ rdf4j-dev mailing list rdf4j-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________rdf4j-dev mailing listrdf4j-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/rdf4j-dev
|