Thanks for your consideration again ...  The difference this time around is
that I know a major release milestone is coming up, and I'd hate it to ship
with an outdated mTCP.  But I'm also getting some late surprises with the
most current code, and not all of it bugs.

Right now the newest mTCP should be held back and miss FreeDOS 1.4, not
because I want to see where the downloads are, but just to avoid some
teething pains.


-Mike


On Fri, Jan 17, 2025 at 5:04 AM Jerome Shidel via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:

> Hi Mike,
>
> > On Jan 16, 2025, at 12:43 PM, Michael Brutman via Freedos-devel <
> freedos-devel@lists.sourceforge.net> wrote:
> >
> > Hi Jerome, I know you are following ... ;-0
> >
> > Please hold off on updating FreeDOS with this mTCP.  It works but there
> are some small bugs that are bothering me and some error messages that I
> want to improve, so I'm going to update it again.  I'd rather FreeDOS ship
> with the previous version (Oct 2024) than ship with the current version
> with its warts.
> >
> >
> > Thanks,
> > Mike
> >
>
> In the past, you have usually asked me not to update our package
> immediately. Waiting to update would help you gain insight into the users
> interest on your update.
>
> I assumed this release would be the same. I intended not to update our
> package version until after the FreeDOS 1.4 release unless you specifically
> requested otherwise.
>
> :-)
>
> Jerome
>
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to