Hi Jeen,
I’ve created the releases notes on github, and closed the github milestone.
Kudos for the deployment documentation by the way, the procedures were easy to follow.
Still no mail from Wordpress though…
Best regards
Bart
From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx>
On Behalf Of Jeen Broekstra
Sent: dinsdag 30 oktober 2018 8:25
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] 2.4.1 patch release next week
Thanks again Bart. I haven't seen an email yet either. Also don't see the release notes up yet at GitHub. But we'll pick it up tomorrow. Let me know if you need a hand with anything
Hi,
Meanwhile the 2.4.1 SDK and onejar are available on the Eclipse SFTP.
I’ll take a look at the WordPress tomorrow. I haven’t received the mail, but maybe it ended up in the spam folder(s).
Best regards
Bart
From:
rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx>
On Behalf Of Jeen Broekstra
Sent: maandag 29 oktober 2018 22:24
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: Re: [rdf4j-dev] 2.4.1 patch release next week
I did notice that for some artifacts, the latest releases are missing (e.g. most of the compliance modules). The latest version there is 2.2.4. So this is probably not a problem
with this particular release, and perhaps even intentional (arguably the compliance tests don't need to be on Central). I'll take a closer look later.
Oh btw Bart I realized you didn't have an editor account yet for our Wordpess site, which you'll need for a release announcement. I created one for you, you should have received
an e-mail. Shout out if you have trouble getting in.
PS it's on my radar to look at our website and documentation setup, and if possible simplify things. We're currently relying on a lot of "bespoke" setup (our own Wordpress site,
our own box to compile and run AsciiDoc doco), I want to see if Eclipse has options to standardize this a bit more.
From: Bart Hanssens (BOSA)
Sent: Monday, October 29, 2018 3:09:51 PM
To: rdf4j developer discussions
Subject: Re: [rdf4j-dev] 2.4.1 patch release next week
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
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 :)
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 ?
I had a consultant do some automation for me with jgit earlier this year. That might give the flexibility required.
Håvard
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.
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.
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
😊
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.
_______________________________________________
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
|