Re: Why were Velocity Engine v2.4 and v2.4.1 never released?

--0000000000008f0173061bd79320
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

There were problems with the process and the developer driving the effort
has not prioritized another attempt since. See this thread and others:

https://lists.apache.org/[email protected]:2024-2

As usual, Velocity moves slow and in fits due to its stability and general
focused-on-other-things developer community. We would, of course, always
appreciate more volunteer help!

On Tue, Jun 25, 2024 at 5:47=E2=80=AFPM Philip Schlesinger
<[email protected]> wrote:

> Hi folks,
>
>
> I went looking at the GitHub repo and there was a version 2.4 prepared:
>
> https://github.com/apache/velocity-engine/commit/5d9e48ca0f1776300f1cf071=
99eb79c34dbe9cb7
>
>
>
> =E2=80=A6and week later a version 2.4.1 prepared as well:
>
>
> https://github.com/apache/velocity-engine/commit/3987078ad7af781d5e6e438b=
65da852d3e589ade
>
>
>
> Why were these never tagged as released =E2=80=93 or mentioned in the Use=
r or
> General mailing lists =E2=80=93 or mentioned in the Velocity news feed?
>
>
>
>
>
>
>
>
>
> *Philip Schlesinger*
> *Solution Architect =E2=80=93 Core Systems*
>
>
>
> [image: Blue text on a black background Description automatically
> generated] <http://www.cryoport.com/>
>
> *=C2=AD=C2=AD*
>
> *Office:  *+1 (949) 681-2794
>
> *24/7/365 Support:  *+1 (949) 470-2305
>
>
>
> *Americas **=E2=80=A2** EMEA **=E2=80=A2* *APAC*
>
> *cryoport.com* <http://cryoport.com/>
>
>
>
> [image: A blue circle with white and black logo Description automatically
> generated] <https://www.linkedin.com/company/856887>[image: A blue circle
> with white x in it Description automatically generated]
> <https://twitter.com/cryoport> [image: A blue circle with a white play
> button Description automatically generated]
> <https://www.youtube.com/user/CryoportVideo>
>
> =C2=AD=C2=AD
>
> The information contained in this e-mail message is privileged and
> confidential information and is intended only for the use of the individu=
al
> and/or entity identified in the address of this message. If the reader of
> this message is not the intended recipient, or an employee or agent
> responsible to deliver it to the intended recipient, you are hereby
> notified that any disclosure, copying, distribution, or reliance upon the
> contents of this email is strictly prohibited. If you have received this
> communication in error, please notify us by return e-mail. In this
> circumstance, we request that you delete the original message from your
> system.
>
>
>

--0000000000008f0173061bd79320--