Date: Mon, 11 Mar 2024 12:44:26 +0100 From: Jan Bramkamp <crest@rlwinm.de> To: freebsd-amd64@freebsd.org Subject: Re: Inquiry Regarding FreeBSD 12 Support Procedure Message-ID: <a8fd65f7-0d99-4221-86fa-2ade2ba8d997@rlwinm.de> In-Reply-To: <SA1PR13MB5633A8C5B4518504EC066A5786222@SA1PR13MB5633.namprd13.prod.outlook.com> References: <SA1PR13MB56331652D30DEF52743D903686222@SA1PR13MB5633.namprd13.prod.outlook.com> <SA1PR13MB5633A8C5B4518504EC066A5786222@SA1PR13MB5633.namprd13.prod.outlook.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On 05.03.24 16:18, Poornima D M wrote:
>
> Hi Team,
> I am writing to inquire about the procedure or process for obtaining
> support for FreeBSD 12. I would greatly appreciate any information or
> guidance you could provide regarding the support options available for
> this version. Could you please provide details on how to access
> support resources for FreeBSD 12, including any relevant documentation
> or contact points? Thank you for your time and assistance. I look
> forward to your response.
>
> Thanks and Regards,
>
> Poornima
>
The FreeBSD 12.x branch is EoL (end-of-life) and does not receive
official support from the FreeBSD project anymore. You can find the list
of supported branches, their initial release date and earliest expected
EoL date. It would be hard for anyone to offer viable (security) support
services for FreeBSD 12.x. Is there a reason why you inquire for FreeBSD
12 support explicitly? Did you encounter problems preventing you from
migrating to FreeBSD 13.x or 14.x?
[-- Attachment #2 --]
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 05.03.24 16:18, Poornima D M wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SA1PR13MB5633A8C5B4518504EC066A5786222@SA1PR13MB5633.namprd13.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator"
content="Microsoft Word 15 (filtered medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Aptos",sans-serif;}span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;
mso-ligatures:none;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<p class="MsoNormal"><span
style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#1D1C1D;background:#F8F8F8">Hi
Team,<br>
I am writing to inquire about the procedure or process
for obtaining support for FreeBSD 12. I would greatly
appreciate any information or guidance you could
provide regarding the support options available for
this version. Could you please provide details on how
to access support resources for FreeBSD 12, including
any relevant documentation or contact points? Thank
you for your time and assistance. I look forward to
your response.<br>
<br>
Thanks and Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#1D1C1D;background:#F8F8F8">Poornima</span></p>
</div>
</div>
</div>
</div>
</blockquote>
<p>The FreeBSD 12.x branch is EoL (end-of-life) and does not receive
official support from the FreeBSD project anymore. You can find
the list of supported branches, their initial release date and
earliest expected EoL date. It would be hard for anyone to offer
viable (security) support services for FreeBSD 12.x. Is there a
reason why you inquire for FreeBSD 12 support explicitly? Did you
encounter problems preventing you from migrating to FreeBSD 13.x
or 14.x?<br>
</p>
</body>
</html>
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a8fd65f7-0d99-4221-86fa-2ade2ba8d997>
