Fwd: Preparing FPC 3.2.4 RC2

Florian Klämpfl via fpc-pascal <[email protected]> Wed, 22 Apr 2026 20:50:12 +0200
Newsgroups gmane.comp.compilers.free-pascal.general
Message-ID <[email protected]>
--===============6276499617727001132==
Content-Type: multipart/alternative; boundary=Apple-Mail-FB9B5483-933E-4543-8E28-35CA6247578A
Content-Transfer-Encoding: 7bit


--Apple-Mail-FB9B5483-933E-4543-8E28-35CA6247578A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html class=3D"apple-mail-supports-explicit-dark-mode"><head><meta http-equi=
v=3D"content-type" content=3D"text/html; charset=3Dutf-8"></head><body dir=3D=
"auto"><div dir=3D"ltr"></div><div dir=3D"ltr"><br><br><br>Anfang der weiter=
geleiteten Nachricht:<br><br></div><blockquote type=3D"cite"><div dir=3D"ltr=
"><b>Von:</b> Florian Kl=C3=A4mpfl &lt;florian-y8GAwIkqPAJpn7uciFS/[email protected]&gt;<br><b>Datu=
m:</b> 22. April 2026 um 20:46:36 MESZ<br><b>An:</b> Warren Postma &lt;warre=
[email protected]&gt;<br><b>Betreff:</b> <b>Aw: [fpc-pascal] Preparing FPC 3=
.2.4 RC2</b><br><br></div></blockquote><blockquote type=3D"cite"><div dir=3D=
"ltr">=EF=BB=BF<meta http-equiv=3D"content-type" content=3D"text/html; chars=
et=3Dutf-8"><div dir=3D"ltr"></div><div dir=3D"ltr"><br></div><div dir=3D"lt=
r"><br><blockquote type=3D"cite">Am 22.04.2026 um 20:30 schrieb Warren Postm=
a &lt;[email protected]&gt;:<br><br></blockquote></div><blockquote typ=
e=3D"cite"><div dir=3D"ltr">=EF=BB=BF<div dir=3D"ltr"><div>Inbetween "we nev=
er use branches" and "infinite branches bad" is every sane git workflow.</di=
v><div><br></div><div>Git flow, or something.&nbsp; &nbsp; stable, trunk, at=
 least.</div></div></div></blockquote><div><br></div>Git flow requires a bra=
nch for every fix and change someone has to merge. Who will do this? To prev=
ent errors, direct committing to stable and trunk should be forbidden so som=
eone has always to merge. Not doable for FPC.<div><br><blockquote type=3D"ci=
te"><div dir=3D"ltr"><div dir=3D"ltr"><div><br></div></div><br><div class=3D=
"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Wed, Apr 22, 2026 at 11:29=E2=80=AFAM Florian Kl=C3=A4mpfl via fpc-pascal &=
lt;<a href=3D"mailto:[email protected]">[email protected]=
ascal.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div><br id=3D"m_932646899227624173lineBreakAtBeginningOfMessage"><di=
v><br><blockquote type=3D"cite"><div>Am 22.04.2026 um 20:01 schrieb Warren P=
ostma via fpc-pascal &lt;<a href=3D"mailto:[email protected]" t=
arget=3D"_blank">[email protected]</a>&gt;:</div><br><div><div=
 dir=3D"ltr"><div><div>&gt;As they should. It's then up to the FPC team to b=
ackport (cherry-pick) them to&nbsp;&nbsp;a fixes branch.<span></span></div><=
br></div><div>This feels weird to me for some reason, maybe that's normal in=
 this project, but it seems more Git-normal to not commit bugfixes straight t=
o trunk. Is this a holdover from the svn days when that's the only workflow y=
ou had because svn branching was... broken?</div></div></div></blockquote><d=
iv><br></div>No. But managing a branch for every change would basically mean=
 thousands of branches. This is possible for projects like linux or whatever=
 when there are people doing nothing else than managing branches. FPC does n=
ot have such resources. Despite this, I think also LLVM despite having huge s=
upport uses a cherry pick based approach to port fixes to stable branches.<b=
r><br><blockquote type=3D"cite"><div><div dir=3D"ltr"><div><br></div><div><b=
r></div><div>W</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Tue, Apr 21, 2026 at 11:04=E2=80=AFPM Graeme Geldenhuy=
s via fpc-pascal &lt;<a href=3D"mailto:[email protected]" targ=
et=3D"_blank">[email protected]</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">On Tuesday, 21 April 2026 00:16:4=
6 BST Warren Postma via fpc-pascal wrote:<br>
&gt; The currently open PRs seem to 100% target main, not 3_2_4 and<br>
<br>
As they should. It's then up to the FPC team to backport (cherry-pick) them t=
o <br>
a fixes branch.<br>
<br>
&gt; few seem to be cleanly even able to land on main anymore after the many=
<br>
&gt; months of them sitting open, that's the trick, I think.<br>
<br>
Correct. I'll be starting this week, going through all the open MRs and <br>=

triage/label them for the authors to action, so we can get them back up to <=
br>
date (or closed).<br>
<br>
Regards,<br>
&nbsp; Graeme<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
fpc-pascal maillist&nbsp; -&nbsp; <a href=3D"mailto:[email protected]=
cal.org" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal"=
 rel=3D"noreferrer" target=3D"_blank">https://lists.freepascal.org/cgi-bin/m=
ailman/listinfo/fpc-pascal</a><br>
</blockquote></div>
_______________________________________________<br>fpc-pascal maillist &nbsp=
;- &nbsp;<a href=3D"mailto:[email protected]" target=3D"_blank=
">[email protected]</a><br><a href=3D"https://lists.freepascal=
.org/cgi-bin/mailman/listinfo/fpc-pascal" target=3D"_blank">https://lists.fr=
eepascal.org/cgi-bin/mailman/listinfo/fpc-pascal</a><br></div></blockquote><=
/div><br></div>_______________________________________________<br>
fpc-pascal maillist&nbsp; -&nbsp; <a href=3D"mailto:[email protected]=
cal.org" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal"=
 rel=3D"noreferrer" target=3D"_blank">https://lists.freepascal.org/cgi-bin/m=
ailman/listinfo/fpc-pascal</a><br>
</blockquote></div>
</div></blockquote></div></div></blockquote></body></html>=

--Apple-Mail-FB9B5483-933E-4543-8E28-35CA6247578A--

--===============6276499617727001132==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
fpc-pascal maillist  -  [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

--===============6276499617727001132==--