First of all, I noticed two threads on this subject. One is following David's email while the other one is from Dmitry. Can we join the two threads into one?
I think we are in debate on whether to update the namespace or not when moving specs from MP to Jakarta. There are cons/pros for either option. How about the following suggestions?
As Jakarta core profile is a brand new profile, could it source specs from both MicroProfile and Jakarta to demonstrate the great ecosystem? Can we label Core Profile as a hybrid profile? If it takes in MP config, MP Config will obey the rules from Core Profile - retaining backward compatibility. In this way, there is no move - no more debate on whether changing namespace or not, no impact for end users.
For MP standalone specs such as Context Propagation, I think it is ok to join Jakarta Concurrency. I think when joining the Context Propagation, due to jpms issues, the namespace would have to be updated. For moving other specs under MP platform release, we really need to weigh out the cons/pros.
At the end of day, we really need to ensure both communities keep moving on and be innovative instead of competing/fighting with each other.
Thanks
Emily