Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] 3.0 release schedule
Thank you both for taking care of the milestone build!

I am back on deck after my skiing trip, and have put things in motion for us to do a final release on August 15. Tech PMC has been asked to approve our review documentation and release notes (I've added a new section for release/upgrade notes on the website btw: https://rdf4j.eclipse.org/release-notes/ ), and our IP log has been approved. 

As an aside: due to the differences in testsuite setup (and the related changes in how Jenkins is set up for master and for develop), we won't merge develop into master until after we have tagged and deployed the 3.0.0 release. That way I don't have to do a lot of changes in the Jenkins master branch setup prior to release, which is especially nice since that entire setup is going to change again anyway once we go back to a monorepo (I want to do that change as soon as possible after the 3.0 release btw). 

Cheers,

Jeen

PS I just tried that slack clone again that we experimented with (mattermost) but it appears eclipse has taken that server down (to be fair, it was a bit of a graveyard). If there's still a need for this kind of thing, we could always go old-skool and give IRC another go (#rdf4j on freenode)

On Wed, Jul 24, 2019 at 4:21 AM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Excellent, thanks


Bart

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Håvard Ottestad <hmottestad@xxxxxxxxx>
Sent: Tuesday, July 23, 2019 2:29:11 PM
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] 3.0 release schedule
 
PS. Looks like there is some automatic publishing to the rdf4j site :)

On 23 Jul 2019, at 14:27, Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:

Thanks Bart.

I’ve added a new post and updated the downloads page.

Håvard


On 23 Jul 2019, at 14:01, Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Nice work !

About the new website, but you can upload new markdown files to github, though I'm not sure the site gets updated automatically after git commits
(perhaps Jeen still has to press the magic button)


I'll add new docker images for good measure (another thing that doesn't work automagically just yet)

Bart

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Håvard Ottestad <hmottestad@xxxxxxxxx>
Sent: Tuesday, July 23, 2019 1:46:33 PM
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] 3.0 release schedule
 
Everything should be done now except for posting on the new webpage. I don’t know where/how to log in to edit those.

The guide was quite comprehensive :)

I think we could easily make a script for making a release branch, the mvn version stuff and the git tagging and pushing.

Same should be possible for the onejar stuff, and maybe even the sftp upload.

I’ve scripted stuff with git before and usually run into issues 6-12 months later when a new git version breaks something. Might be better to use jgit and write a small java program that fixes everything.

Håvard


On 23 Jul 2019, at 13:29, Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:

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

On 23 Jul 2019, at 12:27, Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:

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

On 23 Jul 2019, at 10:46, Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:

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

On 23 Jul 2019, at 10:12, Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

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
From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Håvard Ottestad <hmottestad@xxxxxxxxx>
Sent: Thursday, July 18, 2019 5:49:45 PM
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] 3.0 release schedule
 
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

On 17 Jul 2019, at 21:52, Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

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

 

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> On Behalf Of Håvard Ottestad
Sent: woensdag 17 juli 2019 14:39
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] 3.0 release schedule

 

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 ;)

 

Håvard


On 17 Jul 2019, at 12:30, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:

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.

 

Of course I'm also fine with one of you handling the official release, but since it's a major release, there will be some additional paperwork (requests for additional documentation, etc) involved in the review. In case one of you does feel up to it, see the rdf4j project management docs on minor/major releases for more info on what's involved. FYI the IP log has already been generated (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20337) but it needs to be approved before July 25 to be able to start the review in time, so keep an eye on it. I've also already done a draft of the review documentation (it's available at https://projects.eclipse.org/projects/technology.rdf4j/releases/3.0 ) but it could probably do with some additional details.

 

As said though if you prefer to just do a milestone build and let me handle the final release, that's fine too :)

 

Cheers,

 

Jeen

 

 

On Sun, Jul 7, 2019 at 5:15 PM Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:
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. 

Håvard


On 7 Jul 2019, at 01:53, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:

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.

 

Jeen

 

On Thu, Jun 20, 2019 at 8:07 PM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:
Same here :-/
Currently looking into JDK 11, inching towards something that builds, also thanks to Håvard’s PR on japicmp

 

Best regards

 

Bart

 

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> On Behalf Of Håvard Ottestad
Sent: donderdag 20 juni 2019 11:57
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] 3.0 release schedule

 

That’s very fine with me. 

 

I have conferences this week and I realized last night how tired that made me. 

 

Håvard


On 20 Jun 2019, at 11:33, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:

Havard, others,

 

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.

 

On Fri, Jun 7, 2019 at 7:28 PM Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:

 

 

On Fri, Jun 7, 2019 at 4:46 PM Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:
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)

 

That's... :)

 

 - 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.

 

Jeen

 

 

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@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@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@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@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@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@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@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@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@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@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev

Back to the top