| Newsgroups |
gmane.comp.sysutils.cfengine.general |
| Message-ID |
<[email protected]> |
------=_Part_43876_2118109067.1737651807105
Content-Type: multipart/alternative;
boundary="----=_Part_43877_1857853822.1737651807105"
------=_Part_43877_1857853822.1737651807105
Content-Type: text/plain; charset="UTF-8"
Nick,
Many thanks for your reply.
I think we can live with it for now. As part of my "running hard to seem
to stay still" I hope to start us on the pilgrimage towards 3.21 (MPF, then
binaries) over the next few months, so that will probably be our best way
out of this minor annoyance. (Of course the 3.18->3.21 journey will
involve navigating "rxdirs" and the change from "main" to "mpf_main"...
both in our noticeably mixed-version environment.)
We've already come a long way since being locked on 3.10 and non-MPF a few
years ago; just before Christmas I had introduced our first ever use of
"trigger_upgrade" to pull some recalcitrant straggling machines up to
3.18. Indeed, it was my jumping to 3.18.8 for this exercise on them (and
a couple of others) that introduced this fresh problem there.
Thanks again.
All the best.
-- David Lee
On Friday, 20 December 2024 at 18:08:36 UTC [email protected] wrote:
> Hi David,
>
> Why introduce such a visible change just before EOL-ing a release-series?
>
> As with most bugs, we didn't expect the change to introduce a problem.
>
> I know 3.18 is now EOL. But given that this NEW BUG was introduced at the
> last minute, please could the fix (presumably CFE-4398) be applied
> (cherry-picked) to the 3.18 series? Please?
>
> I can't see that we would pick up maintenance for the EOL branch do builds
> and cut a new release. It doesn't make sense for us to pick changes back to
> 3.18.x that we have no intention of releasing but you could certainly pick
> the changes back to 3.18 and build yourself.
>
> These sort of things are something we generally would consider doing for
> enterprise customers as one-off builds. Beyond that it might be possible to
> do as paid development / professional services / extended support.
>
> Happy Feature Friday #41
> <https://cfengine.com/blog/2024/feature-friday-41-how-can-i-quote-thee/>,
> and Happy Holidays!
>
--
You received this message because you are subscribed to the Google Groups "help-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/help-cfengine/9f39c8ce-bb46-4d8e-802f-2d3180de5ffbn%40googlegroups.com.
------=_Part_43877_1857853822.1737651807105
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div>Nick,</div><div><br /></div><div>Many thanks for your reply.</div><div=
><br /></div><div>I think we can live with it for now.=C2=A0 As part of my =
"running hard to seem to stay still" I hope to start us on the pilgrimage t=
owards 3.21 (MPF, then binaries) over the next few months, so that will pro=
bably be our best way out of this minor annoyance.=C2=A0 (Of course the 3.1=
8->3.21 journey will involve navigating "rxdirs" and the change from "ma=
in" to "mpf_main"... both in our noticeably mixed-version environment.)<br =
/></div><div><br /></div><div>We've already come a long way since being loc=
ked on 3.10 and non-MPF a few years ago; just before Christmas I had introd=
uced our first ever use of "trigger_upgrade" to pull some recalcitrant stra=
ggling machines up to 3.18.=C2=A0=C2=A0 Indeed, it was my jumping to 3.18.8=
for this exercise on them (and a couple of others) that introduced this fr=
esh problem there.</div><div><br /></div><div>Thanks again.<br /></div><div=
><br /></div><div>All the best.</div><div><br /></div><div>-- David Lee<br =
/></div><br /><div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_a=
ttr">On Friday, 20 December 2024 at 18:08:36 UTC [email protected] wr=
ote:<br/></div><blockquote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8=
ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><p>
Hi David,
</p>
<blockquote style=3D"border-left:2px solid gray;padding-left:4px">
<p>
Why introduce such a visible change just before EOL-ing a release-series?
</p>
</blockquote>
<p>
As with most bugs, we didn't expect the change to introduce a problem.
</p>
<blockquote style=3D"border-left:2px solid gray;padding-left:4px">
<p>
I know 3.18 is now EOL. But given that this NEW BUG was introduced at the =
last minute, please could the fix (presumably CFE-4398) be applied
(cherry-picked) to the 3.18 series? Please?
</p>
</blockquote>
<p>
I can't see that we would pick up maintenance for the EOL branch do bui=
lds and cut a new release. It doesn't make sense for us to pick changes=
back to 3.18.x that we have no intention of releasing but you could certai=
nly pick the changes back to 3.18 and build yourself.
</p>
<p>
These sort of things are something we generally would consider doing for en=
terprise customers as one-off builds. Beyond that it might be possible to d=
o as paid development / professional services / extended support.
</p>
<p>
<a href=3D"https://cfengine.com/blog/2024/feature-friday-41-how-can-i-quote=
-thee/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https://=
www.google.com/url?hl=3Den-GB&q=3Dhttps://cfengine.com/blog/2024/featur=
e-friday-41-how-can-i-quote-thee/&source=3Dgmail&ust=3D173773629474=
5000&usg=3DAOvVaw0ekEYed9zH2KTYLl24Y0H_">Happy Feature Friday #41</a>, =
and Happy Holidays!
</p>
</blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;help-cfengine" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">help-=
[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
help-cfengine/9f39c8ce-bb46-4d8e-802f-2d3180de5ffbn%40googlegroups.com?utm_=
medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/help-=
cfengine/9f39c8ce-bb46-4d8e-802f-2d3180de5ffbn%40googlegroups.com</a>.<br /=
>
------=_Part_43877_1857853822.1737651807105--
------=_Part_43876_2118109067.1737651807105--