Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Approval of the past meeting minutes - June 28th meeting
Thanks for pointing out Bill! I made the correction, meaning the same text is in the email is now in the google doc also. 

Here is what I believe we should aim for, similar to what we are doing for Steering Committee calls - 
https://jakarta.ee/meeting_minutes/
each call has its own, pdf file.

So for the moment instead of having separate files to review, can we please provide feedback, comments in the existing file with intention of having 3 separate pdfs (for June 28th, July 12, July 18) published on the web.

Please let me know if you see an issue with this approach.

Thanks,
Tanja




On Wed, Jul 18, 2018 at 5:43 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
There seems to be some text missing after the last sub-sub-bullet under TCK releases.  And there's a bunch of other minor wording problems or typos.  And the text below is different than the text in the Google document; which are we approving?  Hopefully there won't be one ever-growing document that contains all the meeting minutes; the minutes for each meeting should be in a separate document, frozen after approval.

Tanja Obradovic wrote on 07/18/18 07:30 AM:
Hi All,

Can we please approve below meeting minutes from June 28th? The same is also available at the bottom of this Google document that we use for the meeting agenda and past meeting minutes. 

Spec Committee meeting minutes June 28th


Actions:

  • Tanja to set up doodle for a new time slot

    • Weekly meetings are a must

  • Requirements and Goals document is done, feedback is still being collected, please provide feedback


Next steps:


Need to define the TCK challenge process

  • defining TCKs is a must but the process needs to be defined first


Meeting Notes:


Now that RI (Reference Implementation) is gone - what does it mean passing a TCK? What happens in the case there is a conflict between implementations (eg different interpretation of the spec, and therefore different outcome when implemented)


Dealing with specifications is a problem - huge documents, not realistic to rewrite all for the goal to have Jakarta EE 8 released this year

Specs to be compliant with - 7000 pages of specs of 33 JSR - how will this happen quickly??

  • what does it take reference specs instead of redefining / rewriting them

  • What is IP flow structure?? will this allow specs to co-exist

  • Can we have new spec -> to reference old spec + addition on top of the old


Defining a process needs to be a priority

  • process should not care how spec gets done

  • we should plan in next 2-3 weeks spec and process to be defined


Eclipse GlassFish supporting Jakarta EE is not enough. We need others on Jakarta EE 8


TCK releases

  • version management process

  • What should be our approach? stability vs aggressive releases

  • Who calls for a new version?

    • Spec committee needs to approve a new version; a new version would be suggested /recommend it by spec project

    • recommendation from the project and PMC to be used as escalation path (PMC,


TCK maintenance release and then point releases on quarterly releases will show platform making progress freq releases

  • but this can end up with vendors being on too many versions in practice
Regards,
Tanja

--

Tanja Obradovic

Jakarta EE Program Manager | Eclipse Foundation, Inc.

+1.613.295.0105 | eclipse.org | Twitter | LinkedIn | YouTube

Eclipse Foundation: The Platform for Open Innovation and Collaboration


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




--

Tanja Obradovic

Jakarta EE Program Manager | Eclipse Foundation, Inc.

+1.613.295.0105 | eclipse.org | Twitter | LinkedIn | YouTube

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Back to the top