Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] rdf4j 2.5 release planning
No worries Bart, I'm happy you lodged the CQ in the first place because I had completely overlooked it.

Most of our CQs have now been certified, we have one pending Lucene-related CQ. I've pushed back the release date to Feb 21. Who knows, if we get that last CQ approved before then we can even consider adding the lucene/Solr/ES upgrade to the release after all.

Jeen

On Wed, Jan 30, 2019 at 9:39 AM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

My bad really, I should have paid more attention to the status of this CQ

 

Best regards

 

Bart

 

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> On Behalf Of Jeen Broekstra
Sent: dinsdag 29 januari 2019 22:37
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] rdf4j 2.5 release planning

 

Status update: our IP log has not yet been approved, and we still have one pending CQ that needs to be approved before we can proceed with release (the ziplet one). This is my mistake for leaving filing the IP log late and getting caught out by this CQ that wasn't on my radar. I've withdrawn the original CQ and re-filed as a type A in the hope that that gets things moving again.

 

If these things are not fixed by end of today we may need to postpone release for a few weeks. To be fair I don't mind a whole lot, gives us more time to finalize features. If required we can do a second milestone build when we feel enough updates have been put into master.

 

Jeen

 

On Sat, Jan 19, 2019 at 11:14 AM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Hi,

 

+1 on releasing even without Lucene upgrades, 25th seems a bit optimistic to get the remaining CQs approved and somewhat tested.

And 2.5-dev does indeed contain plenty of goodies...

 

Just my 2 cents,

 

Bart

 

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> On Behalf Of Jeen Broekstra
Sent: vrijdag 18 januari 2019 23:50
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] rdf4j 2.5 release planning

 

Just a heads up on timelines: if we want to stick to February 7 as our release date for 2.5, we need our IP log approved by January 30 so we can start a release review on that date. Give or take a few days to get the nod on the IP log itself, and I'd say we have a deadline for CQ approval by January 25 at the latest.

 

In the event that we don't get all our CQs for ElasticSearch/Solr/Lucene updates approved by Jan 25, we have 2 options:

 

1. we postpone release;

2. we release without the Lucene/ES/Solr upgrades.

 

Given the large number of other fixes and improvements, my personal preference is option 2, but I'd like to hear your thoughts. If we postpone, the next possible release date is March 7 (normally it would be Feb 21 but I'm unavailable for release prep in the week before, so unless someone else feels confident enough to handle this and steps up, we'll have to skip a slot). We can of course postpone to March but then do one or more milestone builds in Feb - they don't require any review.

 

Related: I want to do a 2.4.3 patch release this weekend, couple of useful bug fixes are in place. Then I suggest we do a first milestone build for 2.5 (_without_ lucene/ES updates) on Thursday Jan 24.

 

Jeen

 

On Wed, Dec 26, 2018 at 10:51 PM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Sounds good.

 

Still no news about a few ES/Solr/Lucene CQ's, even after a gentle hint in one of the tickets

But it's the holiday season of course..., so I'll try again early January

 

Bart

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Jeen Broekstra <jeen.broekstra@xxxxxxxxx>
Sent: Wednesday, December 26, 2018 2:12:48 AM
To: rdf4j developer discussions
Subject: [rdf4j-dev] rdf4j 2.5 release planning

 

 

I suggest that for RDF4J 2.5.0, we aim for a release on Thursday, February 7. Working backwards, this means we need to be ready for starting a release review on Wednesday, January 27. Planning conservatively, I'd like our open CQs resolved a week before that, on January 20, so that we have enough time to get our IP log approved.

 

I'd like to get a Milestone build for 2.5 out the door around January 20 as well, so  we can get some early-adopter feedback.

 

We can continue adding features and fixes right up to the start of release review, when ideally I'd like to feature-freeze and only accept fixes to existing features. Please keep an eye on your issue tickets in Github, and make sure they have the correct version milestone set.

 

I'll start prepping release documentation ASAP so that we're good to go. Of course, if something comes up we can always push back by two weeks. But I believe we have enough new stuff to make this useful.

 

After 2.5 is out the door, my current plan is start development of a new major release, 3.0. This means that 2.5 is intended to be the last of the 2.x rang (patch releases excepted of course).

 

Thoughts?

 

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

Back to the top