You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Cédric Damioli <cd...@apache.org> on 2023/12/18 18:40:52 UTC

[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 
whatever is needed to actively maintain a now-refocused Cocoon project 
(migration to Git, dependencies upgrades, ...).

Farewell, good old 2.1 :)

Regards,
Cédric

Le 13/12/2023 à 15:00, Cédric Damioli a écrit :
> Hi,
>
> Following and according to last weeks' discussions, it seems that the 
> general consensus would be to retire 2.1 (too old to be maintained) 
> and 3.0 (too alpha to be maintained), and keep 2.x around for now.
>
> If I try to summarize what have been said, refocusing on a single 
> product would give the project a chance to 1) provide a clear upgrade 
> path to existing 2.1 users and 2) gather renewed interest.
> For the still many existing 2.1 users, this would give a clear signal 
> that it's time to consider other options.
>
> It's now time to formally vote:
>
> [ ] +1 accept (retire and officially stop the maintenance of 2.1/3.0 
> branches, only keeping 2.x)
> [ ] -1 reject (explanation required)
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 
> are required to pass.
> This vote will be open for at least 72 hours.
>
> Best regards,
> Cédric
>

-- 
Cédric Damioli
CMS - Java - Open Source
www.ametys.org

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

Posted by Torsten Curdt <tc...@apache.org>.
> 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

Posted by Christofer Dutz <ch...@c-ware.de>.
Well,

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


Chris


Von: Christofer Dutz <ch...@c-ware.de>
Datum: Dienstag, 30. Januar 2024 um 10:41
An: dev@cocoon.apache.org <de...@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 <ga...@workflow.at>
Datum: Sonntag, 28. Januar 2024 um 16:50
An: dev@cocoon.apache.org <de...@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<https://aka.ms/AAb9ysg>
________________________________
From: Jörg Heinicke <jo...@gmx.de>
Sent: Sunday, January 28, 2024 4:37:25 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

I'd also rather go with porting to Git as next step.

Besides, this seems a necessary prerequisite to revive the community
since it reduces the hurdle to get people involved.

Jörg

On 23.01.24 17:54, Christofer Dutz wrote:
> Possibly worth discussing if it’s easier to port to Git and do 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 <cd...@apache.org>
> *Datum: *Dienstag, 23. Januar 2024 um 17:30
> *An: *dev@cocoon.apache.org <de...@cocoon.apache.org>
> *Betreff: *Re: AW: 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

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

Posted by Christofer Dutz <ch...@c-ware.de>.
I’d be happy to take care of that.

Chris

Von: Gabriel Gruber <ga...@workflow.at>
Datum: Sonntag, 28. Januar 2024 um 16:50
An: dev@cocoon.apache.org <de...@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<https://aka.ms/AAb9ysg>
________________________________
From: Jörg Heinicke <jo...@gmx.de>
Sent: Sunday, January 28, 2024 4:37:25 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

I'd also rather go with porting to Git as next step.

Besides, this seems a necessary prerequisite to revive the community
since it reduces the hurdle to get people involved.

Jörg

On 23.01.24 17:54, Christofer Dutz wrote:
> Possibly worth discussing if it’s easier to port to Git and do 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 <cd...@apache.org>
> *Datum: *Dienstag, 23. Januar 2024 um 17:30
> *An: *dev@cocoon.apache.org <de...@cocoon.apache.org>
> *Betreff: *Re: AW: 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

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

Posted by Gabriel Gruber <ga...@workflow.at>.
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 <jo...@gmx.de>
Sent: Sunday, January 28, 2024 4:37:25 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: Re: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

I'd also rather go with porting to Git as next step.

Besides, this seems a necessary prerequisite to revive the community
since it reduces the hurdle to get people involved.

Jörg

On 23.01.24 17:54, Christofer Dutz wrote:
> Possibly worth discussing if it’s easier to port to Git and do 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 <cd...@apache.org>
> *Datum: *Dienstag, 23. Januar 2024 um 17:30
> *An: *dev@cocoon.apache.org <de...@cocoon.apache.org>
> *Betreff: *Re: AW: 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

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

Posted by Jörg Heinicke <jo...@gmx.de>.
I'd also rather go with porting to Git as next step.

Besides, this seems a necessary prerequisite to revive the community
since it reduces the hurdle to get people involved.

Jörg

On 23.01.24 17:54, Christofer Dutz wrote:
> Possibly worth discussing if it’s easier to port to Git and do 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 <cd...@apache.org>
> *Datum: *Dienstag, 23. Januar 2024 um 17:30
> *An: *dev@cocoon.apache.org <de...@cocoon.apache.org>
> *Betreff: *Re: AW: 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

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

Posted by Christofer Dutz <ch...@c-ware.de>.
Possibly worth discussing if it’s easier to port to Git and do 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 <cd...@apache.org>
Datum: Dienstag, 23. Januar 2024 um 17:30
An: dev@cocoon.apache.org <de...@cocoon.apache.org>
Betreff: Re: AW: 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 <cd...@apache.org>
Datum: Freitag, 12. Januar 2024 um 20:48
An: dev@cocoon.apache.org<ma...@cocoon.apache.org> <de...@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 the deletion of the “retired” branches should probably be done 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 <ch...@c-ware.de>
Datum: Montag, 18. Dezember 2023 um 20:25
An: dev@cocoon.apache.org<ma...@cocoon.apache.org> <de...@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 <cd...@apache.org>
Datum: Montag, 18. Dezember 2023 um 19:40
An: dev@cocoon.apache.org<ma...@cocoon.apache.org> <de...@cocoon.apache.org>
Betreff: [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 whatever is needed to actively maintain a now-refocused Cocoon project (migration to Git, dependencies upgrades, ...).

Farewell, good old 2.1 :)

Regards,
Cédric
Le 13/12/2023 à 15:00, Cédric Damioli a écrit :
Hi,

Following and according to last weeks' discussions, it seems that the general consensus would be to retire 2.1 (too old to be maintained) and 3.0 (too alpha to be maintained), and keep 2.x around for now.

If I try to summarize what have been said, refocusing on a single product would give the project a chance to 1) provide a clear upgrade path to existing 2.1 users and 2) gather renewed interest.
For the still many existing 2.1 users, this would give a clear signal that it's time to consider other options.

It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of 2.1/3.0 branches, only keeping 2.x)
[ ] -1 reject (explanation required)
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass.
This vote will be open for at least 72 hours.
Best regards,
Cédric




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

Posted by Cédric Damioli <cd...@apache.org>.
+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 <cd...@apache.org>
> *Datum: *Freitag, 12. Januar 2024 um 20:48
> *An: *dev@cocoon.apache.org <de...@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 the deletion of the “retired” branches should probably
>     be done 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 <ch...@c-ware.de>
>     <ma...@c-ware.de>
>     *Datum: *Montag, 18. Dezember 2023 um 20:25
>     *An: *dev@cocoon.apache.org <de...@cocoon.apache.org>
>     <ma...@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 <cd...@apache.org>
>     <ma...@apache.org>
>     *Datum: *Montag, 18. Dezember 2023 um 19:40
>     *An: *dev@cocoon.apache.org <de...@cocoon.apache.org>
>     <ma...@cocoon.apache.org>
>     *Betreff: *[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
>     whatever is needed to actively maintain a now-refocused Cocoon
>     project (migration to Git, dependencies upgrades, ...).
>
>     Farewell, good old 2.1 :)
>
>     Regards,
>     Cédric
>
>     Le 13/12/2023 à 15:00, Cédric Damioli a écrit :
>
>         Hi,
>
>         Following and according to last weeks' discussions, it seems
>         that the general consensus would be to retire 2.1 (too old to
>         be maintained) and 3.0 (too alpha to be maintained), and keep
>         2.x around for now.
>
>         If I try to summarize what have been said, refocusing on a
>         single product would give the project a chance to 1) provide a
>         clear upgrade path to existing 2.1 users and 2) gather renewed
>         interest.
>         For the still many existing 2.1 users, this would give a clear
>         signal that it's time to consider other options.
>
>         It's now time to formally vote:
>
>         [ ] +1 accept (retire and officially stop the maintenance of
>         2.1/3.0 branches, only keeping 2.x)
>         [ ] -1 reject (explanation required)
>
>         A minimum of 3 binding +1 votes and more binding +1 than
>         binding -1 are required to pass.
>         This vote will be open for at least 72 hours.
>
>         Best regards,
>         Cédric
>

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

Posted by Christofer Dutz <ch...@c-ware.de>.
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 <cd...@apache.org>
Datum: Freitag, 12. Januar 2024 um 20:48
An: dev@cocoon.apache.org <de...@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 the deletion of the “retired” branches should probably be done 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 <ch...@c-ware.de>
Datum: Montag, 18. Dezember 2023 um 20:25
An: dev@cocoon.apache.org<ma...@cocoon.apache.org> <de...@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 <cd...@apache.org>
Datum: Montag, 18. Dezember 2023 um 19:40
An: dev@cocoon.apache.org<ma...@cocoon.apache.org> <de...@cocoon.apache.org>
Betreff: [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 whatever is needed to actively maintain a now-refocused Cocoon project (migration to Git, dependencies upgrades, ...).

Farewell, good old 2.1 :)

Regards,
Cédric
Le 13/12/2023 à 15:00, Cédric Damioli a écrit :
Hi,

Following and according to last weeks' discussions, it seems that the general consensus would be to retire 2.1 (too old to be maintained) and 3.0 (too alpha to be maintained), and keep 2.x around for now.

If I try to summarize what have been said, refocusing on a single product would give the project a chance to 1) provide a clear upgrade path to existing 2.1 users and 2) gather renewed interest.
For the still many existing 2.1 users, this would give a clear signal that it's time to consider other options.

It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of 2.1/3.0 branches, only keeping 2.x)
[ ] -1 reject (explanation required)
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass.
This vote will be open for at least 72 hours.
Best regards,
Cédric



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

Posted by Cédric Damioli <cd...@apache.org>.
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 the deletion of the “retired” branches should probably be 
> done 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 <ch...@c-ware.de>
> *Datum: *Montag, 18. Dezember 2023 um 20:25
> *An: *dev@cocoon.apache.org <de...@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 <cd...@apache.org>
> *Datum: *Montag, 18. Dezember 2023 um 19:40
> *An: *dev@cocoon.apache.org <de...@cocoon.apache.org>
> *Betreff: *[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 
> whatever is needed to actively maintain a now-refocused Cocoon project 
> (migration to Git, dependencies upgrades, ...).
>
> Farewell, good old 2.1 :)
>
> Regards,
> Cédric
>
> Le 13/12/2023 à 15:00, Cédric Damioli a écrit :
>
>     Hi,
>
>     Following and according to last weeks' discussions, it seems that
>     the general consensus would be to retire 2.1 (too old to be
>     maintained) and 3.0 (too alpha to be maintained), and keep 2.x
>     around for now.
>
>     If I try to summarize what have been said, refocusing on a single
>     product would give the project a chance to 1) provide a clear
>     upgrade path to existing 2.1 users and 2) gather renewed interest.
>     For the still many existing 2.1 users, this would give a clear
>     signal that it's time to consider other options.
>
>     It's now time to formally vote:
>
>     [ ] +1 accept (retire and officially stop the maintenance of
>     2.1/3.0 branches, only keeping 2.x)
>     [ ] -1 reject (explanation required)
>
>     A minimum of 3 binding +1 votes and more binding +1 than binding
>     -1 are required to pass.
>     This vote will be open for at least 72 hours.
>
>     Best regards,
>     Cédric
>

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

Posted by Christofer Dutz <ch...@c-ware.de>.
So, I guess the deletion of the “retired” branches should probably be done 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 <ch...@c-ware.de>
Datum: Montag, 18. Dezember 2023 um 20:25
An: dev@cocoon.apache.org <de...@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 <cd...@apache.org>
Datum: Montag, 18. Dezember 2023 um 19:40
An: dev@cocoon.apache.org <de...@cocoon.apache.org>
Betreff: [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 whatever is needed to actively maintain a now-refocused Cocoon project (migration to Git, dependencies upgrades, ...).

Farewell, good old 2.1 :)

Regards,
Cédric
Le 13/12/2023 à 15:00, Cédric Damioli a écrit :
Hi,

Following and according to last weeks' discussions, it seems that the general consensus would be to retire 2.1 (too old to be maintained) and 3.0 (too alpha to be maintained), and keep 2.x around for now.

If I try to summarize what have been said, refocusing on a single product would give the project a chance to 1) provide a clear upgrade path to existing 2.1 users and 2) gather renewed interest.
For the still many existing 2.1 users, this would give a clear signal that it's time to consider other options.

It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of 2.1/3.0 branches, only keeping 2.x)
[ ] -1 reject (explanation required)
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass.
This vote will be open for at least 72 hours.
Best regards,
Cédric


--

Cédric Damioli

CMS - Java - Open Source

www.ametys.org<http://www.ametys.org>

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

Posted by Christofer Dutz <ch...@c-ware.de>.
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 <cd...@apache.org>
Datum: Montag, 18. Dezember 2023 um 19:40
An: dev@cocoon.apache.org <de...@cocoon.apache.org>
Betreff: [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 whatever is needed to actively maintain a now-refocused Cocoon project (migration to Git, dependencies upgrades, ...).

Farewell, good old 2.1 :)

Regards,
Cédric
Le 13/12/2023 à 15:00, Cédric Damioli a écrit :
Hi,

Following and according to last weeks' discussions, it seems that the general consensus would be to retire 2.1 (too old to be maintained) and 3.0 (too alpha to be maintained), and keep 2.x around for now.

If I try to summarize what have been said, refocusing on a single product would give the project a chance to 1) provide a clear upgrade path to existing 2.1 users and 2) gather renewed interest.
For the still many existing 2.1 users, this would give a clear signal that it's time to consider other options.

It's now time to formally vote:

[ ] +1 accept (retire and officially stop the maintenance of 2.1/3.0 branches, only keeping 2.x)
[ ] -1 reject (explanation required)

A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass.
This vote will be open for at least 72 hours.
Best regards,
Cédric



--

Cédric Damioli

CMS - Java - Open Source

www.ametys.org<http://www.ametys.org>