Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Community help request
The table is comment-only but I made comments where I work on or can help especially JMS or Soteria/ES.

Werner 



On Mon, Aug 20, 2018 at 7:11 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

If some project needs particular advice or helping hands with Jenkins / Maven / Nexus / OSSRH / POM changes etc. just let me know. I am not a contributor to other projects besides JAX-RS / Jersey but I can help with the pipeline. I am sure Christian could help too, but he's currently on hollidays.

-Markus

 

From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Kornilov
Sent: Montag, 20. August 2018 17:02
To: Reza Rahman
Cc: Jakarta EE community discussions
Subject: Re: [jakarta.ee-community] Community help request

 

Thanks, Reza. I really appreciate your willingness to help. 

 

Unfortunately, there is not much progress. See the summary here:

 

  • JAX-RS created the release job. Thanks, Markus!
  • Elder Moraes volunteered to create release pipelines for Servlet API. No progress reported so far.
  • I talked with Werner Keil. He is willing to help, but he didn’t put an assignment to the spreadsheet above. Werner, if you are in, please do it.



That’s it. Help is still needed.

 

Thanks,

Dmitry

 



On 17 Aug 2018, at 00:46, Reza Rahman <reza_rahman@xxxxxxxxx> wrote:

 

Have you found any meaningful community help on this? If that's the case, I'll leave this here. If not, I'm going to try to find someone that can help. It can't be right that no one is willing to help accelerate this given how important this work is. This is not my specialty, but I will do it if no one else is willing.

On 8/8/2018 5:36 AM, Dmitry Kornilov wrote:

Hi,

 

I took the initiative and created a list of tasks we need help with. All these task are related to projects CI/CD pipelines and releasing the first Eclipse versions of projects. I created two tasks in projects issues trackers:

 

1. Build CI/CD pipeline. 

 

This is about creating a basic pipeline which build the project and runs tests on Eclipse provided infra.

 

2. Release pipeline and first release

 

This is about creating a release pipeline which releases a Maven artefact to OSSRH *staging* repository. Staging is a keyword, we don’t want public releases before projects pass the release review.

 

Here is a summary spreadsheet with links to all issues created for progress tracking:

 

Please self assign to tasks ion GitHub and and add a comment to the corresponding "Responsible Person” cell in the spreadsheet above, I’ll check it periodically and update it based on your comments.

 

There are also two wiki pages which you can use as a reference:

 

1. How to release the first Eclipse version of projects. 

It contains general flow and HOWTOs.

 

2. JSONP release job. 

It describes JSONP release pipeline which is the only one which works for now. You can use it as a reference for your project release job or you can come out with something else. 

 

Don’t hesitate to ask questions if you have any.

 

Thanks,

Dmitry




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

 

 

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

Back to the top