DKPro Lab Release 0.13.0

[Tobias Horsmann]

Hi,

I think I am satisfied with the last changes. I would want to prepare the release of 0.13.0 

Any objections :o?

Are there any noteworthy differences of releasing Lab compared to releasing TC regarding the steps for preparing the release? 

It is just merging from the branch from "develop" to "master" and then follow the guide? i.e. looking for dead depenencies and so on. 

I think there is barely anything left to do since almost no changes have been made since 0.12.0 so this should be rather quick and easy to do.

Can someone grant me the rights to request a sonatype repository for DKPro Lab ? 

Best,

Tobias

[Richard Eckart de Castilho]

Hi,

> On 19.10.2016, at 15:25, Tobias Horsmann <tobias....@gmail.com> wrote:
>
> I think I am satisfied with the last changes. I would want to prepare the release of 0.13.0
> Any objections :o?
>
> Are there any noteworthy differences of releasing Lab compared to releasing TC regarding the steps for preparing the release?

I don't think there is anything extra to observe.

> It is just merging from the branch from "develop" to "master" and then follow the guide? i.e. looking for dead depenencies and so on.
> I think there is barely anything left to do since almost no changes have been made since 0.12.0 so this should be rather quick and easy to do.

Yup.

> Can someone grant me the rights to request a sonatype repository for DKPro Lab ?

As far as I can tell, you can release any project under the "org.dkpro" groupId:

https://issues.sonatype.org/browse/OSSRH-14519

If you run into permission problems, we should follow up on that, but I think it
should "just work".

Best,

-- Richard

[Tobias Horsmann]

Ok thanks.

What do you request @sonatype for a new release? The last time we requested a new project - is each release a project or how does the workflow looks like?

[Richard Eckart de Castilho]

On 19.10.2016, at 15:45, Tobias Horsmann <tobias....@gmail.com> wrote:
>
> Ok thanks.
>
> What do you request @sonatype for a new release? The last time we requested a new project - is each release a project or how does the workflow looks like?

DKPro Lab is already synced to Maven Central. There is nothing to request. The only thing we would have to request would be for you to get permission to do the release. But as I said: I believe you already have permissions @sonatype to release any project under org.dkpro.

So do your sanity checks on the code, and then "release:prepare"/"release:perform", etc.

Best,

-- Richard

[Tobias Horsmann]

I thought the staging repositories are only valid for one release run? Thus, for a new release I would have to request a new staging repository which requires creating a new issue?

[Richard Eckart de Castilho]

On 19.10.2016, at 15:54, Tobias Horsmann <tobias....@gmail.com> wrote:
>
> I thought the staging repositories are only valid for one release run? Thus, for a new release I would have to request a new staging repository which requires creating a new issue?

The staging repo is created automatically when you run the release as long as you have permissions to use the staging profile associated with the groupId. This is nothing you have to request. Last time, we had to request that you get access to the staging profile so that you can run the release.

The second thing one needs to request is that syncing to Maven Central is enabled for the staging profile. That is done when the first release from the profile is done. This is already done for org.dkpro and as have already been various releases from the this profile.

So I don't see anything we should have to request.

Best,

-- Richard