Re: [mylyn-docs-dev] Releases to Maven Central

[David Green <david.green@xxxxxxxxxxx>]

Jeremie,

The goal is to release all of Mylyn Docs together all the time, but separately from Mylyn.  This will enable us to release more frequently and remove artificial coupling between the projects.

As a step to getting there, I've suggested that we release the Maven artifacts of Mylyn WikiText (i.e. just the core pieces) as a 3.0 release.  The intention is to immediately follow up with another 3.x release of Mylyn Docs that has all of the components in it, UI included.  This will enable us to take an iterative approach to working out the kinks of releasing to Mylyn Central without also having to work out how to release the p2 artifacts of Mylyn Docs at the same time.

As far as versioning, there are still some decisions to be made, but I agree that we should keep it simple.

On release frequency, I don't think that we have an idea yet as to how often we'll release.  I like to think that we can keep Mylyn Docs in a releasable state at all times, and release whenever we need or want to.  This could result in more frequent releases than we've had previously, which would have the benefit of a more continuous value stream to consumers.

David

On Wed, Mar 1, 2017 at 9:30 PM Jeremie Bresson <dev@xxxxxxxx> wrote:

Hi David,

Having the possibility to release wikitext-core to maven central is really great news!

Most of my developments are in wikitext-core, and I appreciate to have an easy way to run the maven build locally.

If we split release process for wikitext-core and wikitext-ui we need to reflect this change in Bugzilla. Otherwise we cannot extract the list of bugs fixed with each wikitext-core release.

Have already an idea of the version scheme? We are now working on "3.0.x" (I have seen, you have built version 3.0.0, 3.0.1 and 3.0.2 to test your setup). In Bugzilla I track the bugs with "Target Milestone = 3.0". When you do a release of wikitext-core on maven central, will the development continue with 3.0.y-SNAPSHOT or with 3.z.0-SNAPSHOT?

If wikitext-core and wikitext-ui are split, have you already a vision for the release train? Sam Davis has mentioned on the cross-project-issues-dev mailing list [1] that there is one downstream project: Jubula. We need to continue to take care of this.

Is the idea to publish a wikitext-core version before each mylyn-docs release?

For the release train, we have main releases but also intermediary builds (milestones and rc). This needs also to be considered.

If we split the release, have you an idea of the release frequency for wikitext-core?

Regards,

Jeremie

[1] http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14164.html

Le 24.02.2017 21:11, David Green a écrit :

Steffen,

 

Thanks for your feedback.  I agree, releasing all of Mylyn Docs would be a good thing.  By doing that we'd produce a separate p2 site as you suggest, which would hopefully make it easier across the board.  I will need some help in making that happen since I'm not familiar with the release process for the p2 components.

 

David

On Thu, Feb 23, 2017 at 4:47 AM Steffen Pingel <steffen.pingel@xxxxxxxxxxx> wrote:

Doing a separate Docs release sounds very good to me! It's great to see that we can finally publish WikiText as proper Maven artifacts that can easily be consumed as a dependency in any Java project.

However, I would prefer to release all of Docs along with the core. I don't see any good reason to delay releases of WikiText UI bits. It would also potentially complicate the Mylyn release process to pull in relevant parts of the WikiText build only and it's not clear to me where the WikiText core p2 repository would be consumed from.

What if we kept both release processes entirely decoupled and simply consumed the latest WikiText release on the Mylyn composite sites? That way consumers wouldn't notice a difference and Mylyn and Docs could release on their own cadence.

Steffen

 

 

On Thu, Feb 23, 2017 at 1:57 AM, David Green <david.green@xxxxxxxxxxx> wrote:

Devs,

 

I'd like to release Mylyn WikiText to Maven Central as part of bug 511120 https://bugs.eclipse.org/bugs/show_bug.cgi?id=511120

We now have a build[1] that can do that for the "core" bits of WikiText using the maven-release-plugin.

 

My current plan is to do a Mylyn Docs release per the EDP[2], but only release the Mylyn WikiText "core" bits.  The rest of Mylyn Docs including the WikiText UI bits would release in conjunction with all of Mylyn per our existing process.

 

This change in process will enable consumers outside of the Eclipse ecosystem to consume WikiText, and will also enable us to release more frequently.

 

Let me know if you have any feedback, positive or otherwise!

 

David

 

1. https://hudson.eclipse.org/mylyn/job/mylyn-wikitext-release

2. https://www.eclipse.org/projects/dev_process/development_process.php

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx

_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev

--

Steffen Pingel
Staff Software Engineer
http://tasktop.com

_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx

_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev

_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx