Works for me too. Thanks Richard
Am 4. Dezember 2024 08:41:54 MEZ schrieb Romain Manni-Bucau <rmannibu...@gmail.com>: >Don't think we'll migrate specs to git, ultimately we'd migrate 1 spec per >repo but since we made them in maintenance mode to prefer jakarta bundles >I'd just move the needed ones, no? > >Yep PMC must do, if there is no objection I or François can do that without >any issue I think. > >Romain Manni-Bucau >@rmannibucau <https://x.com/rmannibucau> | Blog ><https://rmannibucau.metawerx.net/> | Old Blog ><http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | >LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book ><https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> > > >Le mer. 4 déc. 2024 à 08:20, Richard Zowalla <rich...@zowalla.com> a écrit : > >> Yep. We are waiting for CXF (expected next week) and OWB (no response yet) >> ;-) >> >> Don't know how fast INFRA is today for a SVN to Git Migration but would be >> good to just fully migrate the SVN Specs to Git. >> >> I cannot open the Jira though because Infra insists on a PMC member to do >> that (discussed it for another TLP). >> >> So can anyone do that? >> >> Gruß >> Richard >> >> >> Am 4. Dezember 2024 08:08:01 MEZ schrieb Romain Manni-Bucau < >> rmannibu...@gmail.com>: >> >>> Yes release plugin hides all the details but guess we should ensure we do >>> it from git and have svn read-only since there is no urgence (tomee awaits >>> for other releases AFAIK) >>> >>> Romain Manni-Bucau >>> @rmannibucau <https://x.com/rmannibucau> | Blog >>> <https://rmannibucau.metawerx.net/> | Old Blog >>> <http://rmannibucau.wordpress.com> | Github >>> <https://github.com/rmannibucau> | LinkedIn >>> <https://www.linkedin.com/in/rmannibucau> | Book >>> <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> >>> >>> >>> Le mar. 3 déc. 2024 à 22:21, Richard Zowalla <rich...@zowalla.com> a >>> écrit : >>> >>>> @Francois: I think the process is similar. Tagging and commit is done by >>>> the release plugin, so should not be different aside from having SVN >>>> Tooling available. Maybe give it a try? (i am sure the Geronimo Slack is >>>> able to assist in case of issues). >>>> >>>> Gruß >>>> Richard >>>> >>>> >>>> Am 2. Dezember 2024 15:45:10 MEZ schrieb Francois Papon < >>>> francois.pa...@openobject.fr>: >>>> >>>>> Ok :) >>>>> >>>>> It's hard for me to sync that on Monday after 6 hours of meeting :( >>>>> >>>>> Let me cancel this vote. >>>>> >>>>> However about the release of the spec on SVN, I'm not sure I can do >>>>> that, I never done any release on SVN...I don't want to create a >>>>> blackhole :D >>>>> >>>>> NB: should I revert the github repository from the release? I think so >>>>> because it's about the impl, right? >>>>> >>>>> regards, >>>>> >>>>> François >>>>> fpa...@apache.org >>>>> francois.pa...@openobject.fr >>>>> >>>>> Le 01/12/2024 à 11:14, Richard Zowalla a écrit : >>>>> >>>>>> Ok, I just re-checked ;-) >>>>>> >>>>>> What we actually need is a release of the Geronimo Java Mail 2.1 >>>>>> ___Spec___, which is still in SVN: >>>>>> https://svn.apache.org/viewvc/geronimo/specs/trunk/geronimo-mail_2.1_spec/?pathrev=1922110 >>>>>> >>>>>> On GitHub, we have the implementation part, which is not that >>>>>> important. Of course, we should do a release of it once we have the >>>>>> fixed spec available. >>>>>> >>>>>> Sowe don't need an INFRA ticket here as all the specs are still on SVN >>>>>> and everything is actually fine. It is just confusing that there is >>>>>> some part on SVN an some part on GitHub :) >>>>>> >>>>>> @Francois: Sorry, I didn't specified it correctly in my first mail >>>>>> asking for a release :) - I should have written "spec" but the EE mail >>>>>> world is actually hardly tied to impls... >>>>>> >>>>>> Gruß >>>>>> Richard >>>>>> >>>>>> >>>>>> Am Sonntag, dem 01.12.2024 um 11:05 +0100 schrieb Richard Zowalla: >>>>>> >>>>>>> Yep, can create an INFRA Ticket with reference to this thread, so we >>>>>>> can get it fixed up. >>>>>>> >>>>>>> Gruß >>>>>>> Richard >>>>>>> >>>>>>> >>>>>>> Am 1. Dezember 2024 10:33:54 MEZ schrieb Romain Manni-Bucau >>>>>>> <rmannibu...@gmail.com>: >>>>>>> >>>>>>>> I'd say open a ticket to infra to make svn read only, ensure git is >>>>>>>> sync-ed to not loose anything from anywhere. >>>>>>>> Generally truth is git (history direction) but we are human beings >>>>>>>> ;) >>>>>>>> >>>>>>>> Le dim. 1 déc. 2024 à 06:47, Richard Zowalla <rich...@zowalla.com> >>>>>>>> a écrit : >>>>>>>> >>>>>>>>> I am always confused where to find the truth in Geronimo, so all >>>>>>>>> fine :-) >>>>>>>>> >>>>>>>>> I guess, the actual issue is, that the SVN repo is/was not read >>>>>>>>> only. >>>>>>>>> >>>>>>>>> So how to proceed? >>>>>>>>> >>>>>>>>> I would suggest that we use SVN for this release and migrate to >>>>>>>>> git afterwards (dropping what is there). We released a version >>>>>>>>> from SVN and made changes, so the tag is also in SVN. >>>>>>>>> >>>>>>>>> WDYT? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Am 1. Dezember 2024 00:19:47 MEZ schrieb Jean-Louis MONTEIRO >>>>>>>>> <jeano...@gmail.com>: >>>>>>>>> >>>>>>>>>> I thought this one was still on SVN. Sorry if I messed up >>>>>>>>>> >>>>>>>>>> Le sam. 30 nov. 2024 à 20:20, Richard Zowalla >>>>>>>>>> <rich...@zowalla.com> a écrit : >>>>>>>>>> >>>>>>>>>>> Actually, the last release (1.0.0.made by JL) was made from >>>>>>>>>>> SVN and the commits, which broke the milestone, were also >>>>>>>>>>> done on SVN. >>>>>>>>>>> >>>>>>>>>>> So there is an inconsistency for the source of truth here and >>>>>>>>>>> GitHub is already missing changes... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Am 30. November 2024 17:53:16 MEZ schrieb Romain Manni-Bucau >>>>>>>>>>> <rmannibu...@gmail.com>: >>>>>>>>>>> >>>>>>>>>>>> We migrated to gitbox but thought we made svn dir readonly. >>>>>>>>>>>> >>>>>>>>>>>> Le sam. 30 nov. 2024 à 16:18, Richard Zowalla >>>>>>>>>>>> <rich...@zowalla.com> a écrit : >>>>>>>>>>>> >>>>>>>>>>>>> Good question. Didn't know it is on GitHub, so the patch >>>>>>>>>>>>> was in SVN: >>>>>>>>>>>>> https://svn.apache.org/viewvc/geronimo/specs/trunk/geronimo-mail_2.1_spec/?pathrev=1922110 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Am 30. November 2024 15:31:31 MEZ schrieb Romain Manni- >>>>>>>>>>>>> Bucau <rmannibu...@gmail.com>: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hello François, >>>>>>>>>>>>>> >>>>>>>>>>>>>> What is the difference with last release >>>>>>>>>>>>>> (https://github.com/apache/geronimo-javamail/commits/tr >>>>>>>>>>>>>> unk/)? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Romain Manni-Bucau >>>>>>>>>>>>>> @rmannibucau | Blog | Old Blog | Github | LinkedIn | >>>>>>>>>>>>>> Book >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Le ven. 29 nov. 2024 à 21:41, Francois Papon >>>>>>>>>>>>>> <fpa...@apache.org> a écrit : >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi everyone, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I submit Apache Geronimo Java Mail 2.1_1.0.1 release >>>>>>>>>>>>>>> to your vote. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> This release mainly includes (other issue description >>>>>>>>>>>>>>> is available on >>>>>>>>>>>>>>> the release note): >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ** Bug >>>>>>>>>>>>>>> * [GERONIMO-6871] - InternetHeaders to rejects >>>>>>>>>>>>>>> well-formed headers >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Staging Maven repository: >>>>>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapachegeronimo-1174/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Staging dist repository: >>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/geronimo/javamail >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Please vote to approve this release: >>>>>>>>>>>>>>> [ ] +1 Approve the release >>>>>>>>>>>>>>> [ ] -1 Don't approve the release (please provide >>>>>>>>>>>>>>> specific comments) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> This vote will be open for at least 72 hours. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>
