Merge already done, and tags created as per docu;-)
Currently restarting the Jenkins job
rdf4j-client-deploy-release-ossrh-central
(first job went well, but according to the console log there were connection errors for the second job)
"Remote staging failed: java.net.SocketException: Connection reset"
Probably temporarily, I'll give it another try in an hour or so)
Best regards
Bart
From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Jeen Broekstra <jeen.broekstra@xxxxxxxxx>
Sent: Monday, October 29, 2018 2:55:51 PM
To: rdf4j developer discussions
Subject: Re: [rdf4j-dev] 2.4.1 patch release next week
Sorry, you caught me after hours (it's past midnight here), didn't see this earlier. If you're still up for it, then yes, merge that pr and try doing the release. If it's too late now for you, no worries, we'll sort it tomorrow.
Right, going back to bed,ttyl :)
Jeen
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
I had a consultant do some automation for me with jgit earlier this year. That might give the flexibility required.
Håvard
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
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
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.
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
|