Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon project)
Christofer Dutz <[email protected]> Fri, 1 Dec 2023 18:26:01 +0000
| Newsgroups | gmane.text.xml.cocoon.devel |
|---|---|
| Message-ID | <PAVPR05MB9902BA5042143089D27C3D7CA281A@PAVPR05MB9902.eurprd05.prod.outlook.com> |
--_000_PAVPR05MB9902BA5042143089D27C3D7CA281APAVPR05MB9902eurp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'd be +1 to retire 2.1.x Even if I have fond memories of it, as it was my first major apache project= . However it's grown quite old technically and refreshing things would be a h= uge effort. Some of the jvm versions needed are no longer available and I f= ailed to even build it on 1.8. Don't think it's worth the effort :-( Chris Gesendet von Outlook f=FCr Android<https://aka.ms/AAb9ysg> ________________________________ From: C=E9dric Damioli <[email protected]> Sent: Friday, December 1, 2023 7:06:08 PM To: [email protected] <[email protected]> Subject: Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon proj= ect) Le 01/12/2023 =E0 18:13, C=E9dric Damioli a =E9crit : > > We'd like to know whether you'd prefer: > [ ] retiring Cocoon 2.1.x > [ ] reviving/maintaining Cocoon 2.1.x, meaning that you volunteer to > be somehow involved > I'd vote +/-0 here ... Definitively the toughest for me ... I still heavily use Cocoon 2.1 core, but I recognize that it's an very old piece of software, and that maintaining it here would demand more and more work. Perhaps it could be wiser to also let it go, and then fork the core elsewhere if needed with a new build system, without all block stuff, ... I'm curious to see what will others say about it. C=E9dric --_000_PAVPR05MB9902BA5042143089D27C3D7CA281APAVPR05MB9902eurp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> </head> <body> <div dir=3D"auto">I'd be +1 to retire 2.1.x</div> <div dir=3D"auto"><br> </div> <div dir=3D"auto">Even if I have fond memories of it, as it was my first ma= jor apache project. </div> <div dir=3D"auto"><br> </div> <div dir=3D"auto">However it's grown quite old technically and refreshing t= hings would be a huge effort. Some of the jvm versions needed are no longer= available and I failed to even build it on 1.8.</div> <div dir=3D"auto"><br> </div> <div dir=3D"auto">Don't think it's worth the effort :-(</div> <div dir=3D"auto"><br> </div> <div dir=3D"auto">Chris</div> <div dir=3D"auto"><br> </div> <div dir=3D"auto"><br> </div> <div><br> </div> <div id=3D"ms-outlook-mobile-signature" dir=3D"auto">Gesendet von <a href= =3D"https://aka.ms/AAb9ysg"> Outlook f=FCr Android</a></div> <hr style=3D"display:inline-block;width:98%" tabindex=3D"-1"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st= yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> C=E9dric Damioli <= [email protected]><br> <b>Sent:</b> Friday, December 1, 2023 7:06:08 PM<br> <b>To:</b> [email protected] <[email protected]><br> <b>Subject:</b> Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Coco= on project)</font> <div> </div> </div> <div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;= "> <div class=3D"PlainText"><br> Le 01/12/2023 =E0 18:13, C=E9dric Damioli a =E9crit :<br> ><br> > We'd like to know whether you'd prefer:<br> > [ ] retiring Cocoon 2.1.x<br> > [ ] reviving/maintaining Cocoon 2.1.x, meaning that you volunteer to <= br> > be somehow involved<br> ><br> <br> I'd vote +/-0 here ...<br> Definitively the toughest for me ...<br> I still heavily use Cocoon 2.1 core, but I recognize that it's an very <br> old piece of software, and that maintaining it here would demand more <br> and more work.<br> <br> Perhaps it could be wiser to also let it go, and then fork the core <br> elsewhere if needed with a new build system, without all block stuff, ...<b= r> I'm curious to see what will others say about it.<br> <br> C=E9dric<br> <br> </div> </span></font></div> </body> </html> --_000_PAVPR05MB9902BA5042143089D27C3D7CA281APAVPR05MB9902eurp_--