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

Great stuff Bart, I see it's all done and dusted, thanks for taking care of this!

Cheers,

Jeen

On Thu, Nov 1, 2018 at 12:08 AM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Hi Jeen,


no problem, meanwhile I've received your mail about the Wordpress credentials, so I'll update the website accordingly.

When that's done, I'll send the mail to the rdf4j-users lists to announce the release (+ some twittering ;-)


Best regards


Bart


From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Jeen Broekstra <jeen.broekstra@xxxxxxxxx>
Sent: Wednesday, October 31, 2018 3:05:10 AM
To: rdf4j developer discussions
Subject: Re: [rdf4j-dev] 2.4.1 patch release next week
Â
Ah sorry, when you said "mail missing" I thought you were talking about your announcement message to the mailing list. Sorry about that. I'll doublecheck Wordpress, I'll just mail you your details privately if necessary.

Jeen

On Tue, Oct 30, 2018 at 8:40 PM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

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Â

Â

Cheers,

Â

Jeen

Â

On Tue, 30 Oct. 2018, 10:40 Bart Hanssens (BOSA), <bart.hanssens@xxxxxxxxxxxx> wrote:

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

Â

Looks good!

Â

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.

Â

Cheers,

Â

Jeen

Â

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.

Â

On Tue, Oct 30, 2018 at 7:49 AM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Seems like the rdf4j 2.4.1 artifacts made their way to the maven repository eventually https://search.maven.org/search?q=rdf4j

So I'll start building the SDK and onejar.

Â

Best regards

Â

Bart


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


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

Â

On Mon, 29 Oct. 2018, 21:26 Bart Hanssens (BOSA), <bart.hanssens@xxxxxxxxxxxx> wrote:

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

Â

_______________________________________________
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