> On May 18, 2021, at 12:22 PM, David Blevins <david.blev...@gmail.com> wrote:
> 
> As long as I was doing the tomee-release-tools converstion from svn to git, I 
> went ahead and did this one too:
> 
> - https://github.com/apache/tomee-jakartaee-api
> 
> We did end up creating a module for an updated jakartaee-api jar in the 
> `tomee-jakarta` repo:
> 
> - https://github.com/apache/tomee-jakarta/tree/master/jakartaee-api
> 
> Next steps for anyone who has the energy is to move that setup into the 
> `tomee-jakartaee-api` repo then remove it from `tomee-jakarta`

Jean-Louis,

Here's the last status on jakartaee-api I remember.


-David


> 
>> On May 19, 2020, at 7:18 PM, Cesar Hernandez <cesargu...@gmail.com> wrote:
>> 
>> Hi,
>> 
>> I need help from a PMC member in order to create the repo.
>> 
>> In the INFRA ticket [1] we obtained the link for the self-service creation
>> of a new git repository but it most be performed by a PMC member.
>> This is the link for the request:
>> https://gitbox.apache.org/setup/newrepo.html
>> 
>> As peer the data requested by the form, this is the information required.
>> Notice that I left the repo name with tomee as the prefix because all the
>> other gitbox repositories related with Tomee has it.
>> 
>> Repository name: tomee-jakartaee-api
>> Repository description: Apache TomEE jakartaee-api
>> Commit notification list: dev@tomee.apache.org
>> GitHub notification list: dev@tomee.apache.org
>> 
>> 
>> [1]
>> https://issues.apache.org/jira/browse/INFRA-20280?focusedCommentId=17111651&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17111651
>> 
>> 
>> El lun., 18 may. 2020 a las 16:07, Daniel Dias Dos Santos (<
>> daniel.dias.analist...@gmail.com>) escribió:
>> 
>>> great :  )
>>> --
>>> 
>>> *Daniel Dias dos Santos*
>>> Java Developer
>>> SouJava & JCP Member
>>> GitHub: https://github.com/Daniel-Dos
>>> Linkedin: www.linkedin.com/in/danieldiasjava
>>> Twitter: http://twitter.com/danieldiasjava
>>> 
>>> 
>>> Em seg., 18 de mai. de 2020 às 19:04, Cesar Hernandez <
>>> cesargu...@gmail.com>
>>> escreveu:
>>> 
>>>> My own +1
>>>> Here are the results from the vote.
>>>> 
>>>> 
>>>> +1s
>>>> 
>>>> Jonathan Gallimore (binding)
>>>> 
>>>> David JencksDaniel "soro" Cunha
>>>> 
>>>> Daniel Dias Dos Santos
>>>> 
>>>> Thiago Henrique Hupner
>>>> 
>>>> Nishant Raut
>>>> Mark Struberg (binding)
>>>> 
>>>> Carlos Chacín
>>>> 
>>>> Cesar Hernandez
>>>> 
>>>> 
>>>> There are no other votes, so this vote passes. I'll open the infra ticket
>>>> for this task.
>>>> 
>>>> El jue., 30 abr. 2020 a las 9:39, Carlos Chacín (<ccha...@gmail.com>)
>>>> escribió:
>>>> 
>>>>> +1
>>>>> 
>>>>> On Thu, Apr 30, 2020 at 6:04 AM Mark Struberg
>>> <strub...@yahoo.de.invalid
>>>>> 
>>>>> wrote:
>>>>> 
>>>>>> +1 (binding)
>>>>>> 
>>>>>> LieGrue,
>>>>>> strub
>>>>>> 
>>>>>> 
>>>>>>> Am 29.04.2020 um 23:39 schrieb Cesar Hernandez <
>>> cesargu...@gmail.com
>>>>> :
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> As a follow up from the `Javax -> Jakarta rename` thread [1]
>>>>>>> I would like to propose moving the existing SVN javaee-api repo [2]
>>>> to
>>>>>>> Git[3] to enable wider visibility and collaboration either via
>>> GitHub
>>>>> or
>>>>>>> gitbox.apache.org.
>>>>>>> 
>>>>>>> I will create the Apache JIRA Infra migration ticket after the vote
>>>> has
>>>>>>> passed.
>>>>>>> 
>>>>>>> [ ] +1 approve the release move javaee-api repo to Git
>>>>>>> [ ] +0 no opinion
>>>>>>> [ ] -1 disapprove (and reason why)
>>>>>>> 
>>>>>>> [1]
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> https://lists.apache.org/thread.html/refb945e599cad66d8508a540fa5801fd2b04682424e9e29b4e6dd7b4%40%3Cdev.tomee.apache.org%3E
>>>>>>> [2] https://svn.apache.org/repos/asf/tomee/javaee-api/
>>>>>>> [3] https://gitbox.apache.org/
>>>>>>> --
>>>>>>> Atentamente:
>>>>>>> César Hernández.
>>>>>> 
>>>>>> 
>>>>> 
>>>>> --
>>>>> *Carlos Chacin*
>>>>> Senior SDE
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> Atentamente:
>>>> César Hernández.
>>>> 
>>> 
>> 
>> 
>> -- 
>> Atentamente:
>> César Hernández.
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to