Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] 2.4.1 patch release next week

Hi Jeen, Håvard,


so I'll guess I'll merge GH-1056  into master (leaving further improvements for a next release),
and start the process of creating the 2.4.1 release ?

Best regards

Bart

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Håvard Ottestad <hmottestad@xxxxxxxxx>
Sent: Monday, October 29, 2018 7:51
To: rdf4j developer discussions
Subject: Re: [rdf4j-dev] 2.4.1 patch release next week
 
I had a consultant do some automation for me with jgit earlier this year. That might give the flexibility required.

Håvard

On 29 Oct 2018, at 06:21, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:

No prob Havard.

Automating the release would be good. There's too many manual steps involved at the moment. It's tricky though, as we need multiple repos in the right state, and e.g. SDK/onejar assembly can't start until all versioned maven artifacts are available.

Back in the dark ages we used the maven release plugin to automate things, but we dropped it because it didn't fit with the git workflow/branching model. It might be interesting to revisit it though.

Cheers,

Jeen

On Sat, Oct 27, 2018 at 9:00 PM "Håvard M. Ottestad" <hmottestad@xxxxxxxxx> wrote:
Just thought I would let you know that I think right now I want to focus on the shacl stuff and helping out with a review every once in a while. 

I would also be up for helping automate the release. Would be nice with a single push-button solution.

Håvard

On 27 Oct 2018, at 03:44, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:



On Fri, Oct 26, 2018 at 7:17 PM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:


If needed, I can spare a few hours on Monday (the rest of the week is somewhat more difficult) to give it a try,

unless you or Havard want to do the honors 😊


By all means, go for it. 

ProTip: don't put anything on the site or the mailing list until you're sure the release artifacts are available and all has gone well. If in doubt, just wait with putting out an announcement until you've had a chance to verify.

I'll doublecheck the developer docs this weekend to make sure it documents all the steps correctly. Have a glance beforehand if you can and let me know if anything is unclear to you.


I guess it would be a good time to create a PR to merge the fixes from the master branch into the develop branch ?


We can do that any time it's convenient, but definitely a good idea to do directly after a release.

 

(and bump the version in the docker image https://github.com/eclipse/rdf4j-tools/tree/master/assembly/src/main/dist/docker

FWIW, I’m in touch with the Eclipse team to get access to the Eclipse part of hub.docker.com)

 

I’m mainly working on a library upgrades for 2.5 and fixing a console bug, but it needs some more testing,

so that would rather be candidate for 2.4.2 or 2.5.0  (https://github.com/eclipse/rdf4j/issues/1105)


Good to hear. I'm fine with doing more patch releases later, they're cheap and easy so even if there's only one or two bug fixes we can do that.
 

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

Back to the top