[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be "jakarta-ized"
|
TBH, in my personal
experience, I have found that many people will create PRs and then (maybe)
associate it with an Issue as an afterthought. But, if any of the
other committers on the Platform project wish to track the effort on a
more granular basis, you are welcome to create and track the progress via
individual issues. I'm just trying to kickstart the activity before
the long weekend in the US. Thanks!We already have
two PRs submitted. Thanks, Steve, for your great reviews! Keep
them coming!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
Emily
Jiang <emijiang6@xxxxxxxxxxxxxx>To:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>Date:
07/04/2019
08:32 AMSubject:
[EXTERNAL]
Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be
"jakarta-ized"Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
I like the idea of 1PR = 1 issue from
Steve. In order not to duplicate effort, can we comment on the issue to
say which ascii are you working on? I plan to help out. By the time, I
can start working, it will be good to see what left to be done. I hate
to see some of us head down to edit. By the time he/she finishes, someone
has done the PR. Avoid wasting time. Thoughts?EmilyOn Thu, Jul 4, 2019 at 2:27 PM Steve
Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:Personally I like 1 PR = 1 issue as GH
will autoclose the issue when the PR is merged but not too bothered in
this case. Steve From: jakartaee-platform-dev-bounces@xxxxxxxxxxx<jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 04 July 2019 14:22
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Platform and WebProfile specs
ready to be "jakarta-ized" Steve,
Decided not to do an Issue per chapter. Reference my previous reply
and the one Issue I did create:
https://github.com/eclipse-ee4j/jakartaee-platform/issues/38
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: "Steve
Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To: jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 07/04/2019
05:12 AM
Subject: [EXTERNAL]
Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be
"jakarta-ized"
Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
Or
an issue per chapter then the PR will correspond
From:jakartaee-platform-dev-bounces@xxxxxxxxxxx<jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Guillermo González de Agüero
Sent: 04 July 2019 11:11
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Platform and WebProfile specs
ready to be "jakarta-ized"
Thanks
for the heads-up Kevin. I'll try to help there on the weekend.
I
can't do it right now, but I propose we create an issue with a checklist
of all chapters, so people can comment and assign specific chapters themselves.
Otherwise
we are at risk of duplicating efforts.
El
jue., 4 jul. 2019 5:19, Kevin Sutter <sutter@xxxxxxxxxx>
escribió:
Hi,
Most of you know that the Java EE Platform and WebProfile specs have now
been contributed to Eclipse and ready to go through the transformation
to Jakarta Platform and WebProfile specs:
https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification
I have broken up the individual specs into slightly more manageable pieces
of asciidoc (each spec used to be one giant asciidoc file). I broke
them up by chapters. Of course, some are larger than others, but
at least we can now divide and conquer the effort in front of us.
Many of you have been asking "how can I help?". Now's your
chance. If you are interested and available, we would appreciate
PRs with cleaning up the various sections of these two spec documents.
The cleanup required is mostly tedious work.
- The main thing is changing
"Java EE" to "Jakarta EE".
- Modifying references
to the JCP with corresponding Eclipse processes.
- References to existing
Java EE technologies, acronyms, and JSRs are okay as long as they are properly
attributed.
- Be careful not to modify
the semantics or behavior -- we need Jakarta EE 8 to be functionally equivalent
to Java EE 8.
-
We
are looking for the minimal work required. At this point, do not
further subdivide the asciidoc files. I would suggest keeping the
PRs short and simple. Don't try to do "everything" in one
PR. You don't even have to complete a whole chapter in a single PR.
Maybe identify the subsections covered in the title of your PR. Shorter
PRs will be easier for the committers to evaluate and merge into master.
Reference the list of existing PRs before starting on a chapter to avoid
duplication of effort.
I am sending out this request now since many of us in the US will be out
for the extended weekend. There are a few committers in other parts
of the world, so hopefully we'll make some progress over the weekend.
I didn't want to wait until Monday to start this effort since we need to
have these spec docs ready by July 15.
Thanks for your help!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx
Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev _______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
-- Thanks
Emily
=================
Emily Jiang
ejiang@xxxxxxxxxx_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev