Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-spec.committee] Approval of the past meeting minutes - June 28th meeting
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

Back to the top