Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Spec doc conversion: heads-up
Tom,
I should have read the passage before responding...  The doc already states that only "checkin" is required before starting work on the doc.  The "Approval" is required before the doc can be included in a public release (or service release).  Any Milestone or Release Candidate drivers are okay to include the doc before these CQs are approved.  If you look at the complete list of CQs, you'll see about half of them are in the Approved state.  This is a state at the IP team moves the CQ to -- after the development team has updated the CQ with the information that the source has been merged and any requested actions have been taken care of.

Full list:  https://dev.eclipse.org/ipzilla/buglist.cgi?https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=specification+document&product=ee4j

Hope this helps!
-- Kevin

On Wed, Feb 12, 2020 at 7:57 AM Kevin Sutter <kwsutter@xxxxxxxxx> wrote:
That is not correct, Tom.  The CQ gets marked Approved after each component does the required work to incorporate the source into their repo.  The keyword "checkin" is required as well as PMC approval.  I'll update those instructions.  Thanks!

-- Kevin

On Wed, Feb 12, 2020 at 5:06 AM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
Hi,

https://github.com/jakartaee/specification-committee/blob/master/steps_javaee_to_jakartaee.adoc says "CQ must be marked approved before the document may be included in any release". I tried to find something on https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21456 to confirm it but don't have an exact match. Is the thing to look for a positive PMC_Approved flag?

Also I see a keyword "checkin" but how do I the person that set it is part of the "EMO IP Team"? https://dev.eclipse.org/ipzilla/show_activity.cgi?id=21456

Thanks,
Tom

On Wed, 22 Jan 2020 at 14:43, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
Just to ensure that everyone knows about this...  Based on our efforts for the Platform and Web Profile Specs, we compiled some helpful hints.  I just referenced these when I did the Jakarta-izing of the Managed Beans Spec and it helped jog my memory.  Good luck!

https://github.com/jakartaee/specification-committee/blob/master/steps_javaee_to_jakartaee.adoc

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        Mark Thomas <markt@xxxxxxxxxx>
To:        jakartaee-platform-dev@xxxxxxxxxxx
Date:        01/22/2020 08:29
Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] Spec doc conversion: heads-up
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx



On 22/01/2020 11:54, Dmitry Kornilov wrote:
> I am currently working on JPA spec and facing the same issues. It’s not difficult, but time consuming because there is no other way than doing it manually section by section.

+1

Also, from experience of doing the EL and WebSocket specs watch for
escaping issues around code snippets.

I found there was a reasonable amount that could be done via search and
replace on the source but you have to review each one. You can't just do
a global search and replace.

And there was no getting away from the repeated cycles of generate PDF,
proof-read, correct, repeat.

Mark


>
> - Dmitry
>
>> On 22 Jan 2020, at 12:42, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
>>
>> Hi,
>>
>> I just started with the JASPIC to Jakarta Authentication spec document conversion, and just a heads-up for anyone who hasn't started yet: it's quite labour intensive.
>>
>> Tables are completely missing, image captions are mistaken for headings meaning section numbering and hierarchies are all wrong, even chapter numbering can become all wrong, footnotes are missing, etc etc.
>>
>> This is far more than just a semi-automated search & replace for terms as with the Javadocs adjustments for Jakarta EE 8.
>>
>> Basically it boils down to reading the entire document, adjusting errors wherever you see them, compiling the PDF, checking it's correct now and repeat that.
>>
>> Absolutely doable of course, but just taking a fair amount of time.
>>
>> Kind regards,
>> Arjan
>>
>> _______________________________________________
>> 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



_______________________________________________
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

Back to the top