-
Notifications
You must be signed in to change notification settings - Fork 10
Release project #41
Comments
@donovanmuller What do you think? Just give me a green light and we can enjoy brand new release of the project soon ;) . |
Hi Henryk, just travelling at the moment. Will get to this as soon as I can 👍 |
Awesome, thanks!
On Wed, Jun 7, 2017, 08:48 Donovan Muller ***@***.***> wrote:
Hi Henryk, just travelling at the moment. Will get to this as soon as I
can 👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAyOd-9LQ8PxQqzZ_xhmskz79gFjRc7Kks5sBkfSgaJpZM4Nxa6J>
.
--
Henryk Konsek
https://linkedin.com/in/hekonsek
|
All releases are pushed to this Bintray repo: https://bintray.com/donovanmuller/switchbit-public/spring-cloud-deployer-openshift Would that be sufficient, or is Maven Central something you must have? |
Would it be a problem to enable sync with Maven Central in Bintray? :)
pt., 9 cze 2017 o 07:41 użytkownik Donovan Muller <[email protected]>
napisał:
All releases are pushed to this Bintray repo:
https://bintray.com/donovanmuller/switchbit-public/spring-cloud-deployer-openshift
Would that be sufficient, or is Maven Central something you must have?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAyOd6cjk3Uec1tEbxaI--nB7KzIG1Etks5sCNr9gaJpZM4Nxa6J>
.
--
Henryk Konsek
https://linkedin.com/in/hekonsek
|
I could look at that yes :) |
That would be great! Also another question related to release - do you plan to release OpenShift deployer whenever Spring Deployer is released and keep versions in sync with a Spring Deployer project? |
I have sent the request to add to Maven Central... The release of this project is targeted to track the Spring Cloud Data Flow releases. I'm planning to hopefully get to them soon and release 1.2.0 to track Spring Cloud Data Flow 1.2.x release. |
Many thanks for the Central request! Is there anything in particular what prevents you from releasing 1.2.0 version of the project? IMHO OpenShift deployer should catch up to the Spring's releases as soon as possible. BTW It seems that deployer has similar [1], but not identical release cycle to SCDF. The former is 1.2.0 right now, while the latter is 1.2.1. [1] https://github.com/spring-cloud/spring-cloud-deployer-kubernetes/releases |
See the 1.2.0 milestone for issues I'd like to close before releasing. |
Unfortunately, I realised later that releasing this project to Maven Central would not be possible in it's current form. Specifically due to the package name of I'll have to either change the package to |
Also keep in mind that you can release under your GitHub name, like
"com.github.donovanmuller" . Just saying :) .
pon., 19 cze 2017 o 07:54 użytkownik Donovan Muller <
[email protected]> napisał:
Unfortunately, I realised later that releasing this project to Maven
Central would not be possible in it's current form. Specifically due to the
package name of org.springframework.cloud, which I obviously will not
have permission to publish under.
I'll have to either change the package to io.switchbit or ask if this
project can somehow be adopted as an official Spring project. I'll respond
with a decision shortly...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAyOd8OFuwMR8UAauhp9I1OPeaxzxinnks5sFg0sgaJpZM4Nxa6J>
.
--
Henryk Konsek
https://linkedin.com/in/hekonsek
|
Hi Donovan,
What do you think about releasing the project to Maven Central? I'd like to use deployer in some of our projects here at Red Hat and I'd love to rely on the stable version of OpenShift Deployer.
Maybe I will create a PR with release configuration for Sonatype OSS, so you can just hit
mvn release:perform
to start syncing with Maven Central?The text was updated successfully, but these errors were encountered: