Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

> I guess as there were no objections, I’ll go forward with this. > +1

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

Well, I guess as there were no objections, I’ll go forward with this. Chris Von: Christofer Dutz Datum: Dienstag, 30. Januar 2024 um 10:41 An: dev@cocoon.apache.org Betreff: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x I’d be happy to take care of that. Chris Von: Gabriel Gruber Datum

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

I’d be happy to take care of that. Chris Von: Gabriel Gruber Datum: Sonntag, 28. Januar 2024 um 16:50 An: dev@cocoon.apache.org Betreff: Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x Going to github would make things a lot easier. Who could do that? Gabriel Gesendet von Outlook für Android

Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

Going to github would make things a lot easier. Who could do that? Gabriel Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> From: Jörg Heinicke Sent: Sunday, January 28, 2024 4:37:25 PM To: dev@cocoon.apache.org Subject: Re: [RESULT][VOTE] Retire 2

Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

that then … or if better done in SVN … I guess the final discussion Git vs. SVN still needs to formally be done, right? Chris *Von: *Cédric Damioli *Datum: *Dienstag, 23. Januar 2024 um 17:30 *An: *dev@cocoon.apache.org *Betreff: *Re: AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x +1 Cédric Le 23

AW: AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x +1 Cédric Le 23/01/2024 à 17:25, Christofer Dutz a écrit : Yeah … I also think that possibly making them read-only (and additionally prefixing them with a “retired/” prefix should be enough. Chris Von: Cédric Damioli <mailto:cdami...@apache.

Re: AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

@cocoon.apache.org *Betreff: *Re: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x Why should retired branches be deleted ? Shouldn't they instead be somehow put in read-only state but kept available for anyone needing them ? My 2 cents, Cédric Le 09/01/2024 à 14:40, Christofer Dutz a écrit : So, I guess

AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

Yeah … I also think that possibly making them read-only (and additionally prefixing them with a “retired/” prefix should be enough. Chris Von: Cédric Damioli Datum: Freitag, 12. Januar 2024 um 20:48 An: dev@cocoon.apache.org Betreff: Re: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x Why

Re: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

by a PMC member. I’m happy to help with migrating 2.3.x to git as soon as the old stuff is buried, if the project wants this to happen. Chris *Von: *Christofer Dutz *Datum: *Montag, 18. Dezember 2023 um 20:25 *An: *dev@cocoon.apache.org *Betreff: *AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

@cocoon.apache.org Betreff: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x How about a Mexican style funeral party at Community Over Code? ;-) Cocoon 2.1 was such a big part of my early IT carreer … Chris Von: Cédric Damioli Datum: Montag, 18. Dezember 2023 um 19:40 An: dev@cocoon.apache.org

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

How about a Mexican style funeral party at Community Over Code? ;-) Cocoon 2.1 was such a big part of my early IT carreer … Chris Von: Cédric Damioli Datum: Montag, 18. Dezember 2023 um 19:40 An: dev@cocoon.apache.org Betreff: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x The vote is now over

[RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

The vote is now over and successful with 4 binding +1 and no -1 : * Francesco Chicchiriccò * Peter Hunsberger * Jörg Heinicke * Cédric Damioli The PMC is now tasked to do what is needed to effectively retire 2.1/3.0. As discussed before, it's now time for volunteers to step up to do