4.2.0

4.2.0

[Paul Zimmermann]

       Hi,

on https://sourceware.org/newlib -> Download -> http there is a file
newlib-4.2.0.20211231.tar.gz. Is that the official 4.2.0 release or
a pre-release?

Best regards,
Paul Zimmermann

Re: 4.2.0

[Brian Inglis]

On 2022-02-03 01:36, Paul Zimmermann wrote:
> on https://sourceware.org/newlib -> Download -> http there is a file
> newlib-4.2.0.20211231.tar.gz. Is that the official 4.2.0 release or
> a pre-release?

Official release and year end snapshot:

Update newlib to 4.2.0 newlib-snapshot-20211231

https://cygwin.com/git/?p=newlib-cygwin.git;h=484d2ebf8d825b28af47b8ee88cd845f1d2c7c6e

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

Re: 4.2.0

[Paul Zimmermann]

> Date: Thu, 3 Feb 2022 02:14:20 -0700
> From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
> 
> On 2022-02-03 01:36, Paul Zimmermann wrote:
> > on https://sourceware.org/newlib -> Download -> http there is a file
> > newlib-4.2.0.20211231.tar.gz. Is that the official 4.2.0 release or
> > a pre-release?
> 
> Official release and year end snapshot:
> 
> Update newlib to 4.2.0 newlib-snapshot-20211231
> 
> https://cygwin.com/git/?p=newlib-cygwin.git;h=484d2ebf8d825b28af47b8ee88cd845f1d2c7c6e

thank you Brian. I did wonder since the naming scheme changed (it was
newlib-4.1.0.tar.gz for the previous release).

Best regards,
Paul

Re: 4.2.0

[Jeff Johnston]

That was the official yearly snapshot.  Newlib was bumped to 4.2.0 as there
were configuration changes.
I imagine that another snapshot is warranted soon with all the other
various configuration changes being made recently.

-- Jeff J.

On Thu, Feb 3, 2022 at 3:36 AM Paul Zimmermann <Paul.Zimmermann@inria.fr>
wrote:

>        Hi,
>
> on https://sourceware.org/newlib -> Download -> http there is a file
> newlib-4.2.0.20211231.tar.gz. Is that the official 4.2.0 release or
> a pre-release?
>
> Best regards,
> Paul Zimmermann
>
>

Re: 4.2.0

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]

On 03 Feb 2022 12:50, Jeff Johnston wrote:
> That was the official yearly snapshot.  Newlib was bumped to 4.2.0 as there
> were configuration changes.
> I imagine that another snapshot is warranted soon with all the other
> various configuration changes being made recently.

i would have leaned the other direction ... give them longer to bake by devs
building the latest git before kicking out a "release" that other people might
expect to be pretty stable.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: 4.2.0

[Corinna Vinschen]

On Feb  3 20:23, Mike Frysinger wrote:
> On 03 Feb 2022 12:50, Jeff Johnston wrote:
> > That was the official yearly snapshot.  Newlib was bumped to 4.2.0 as there
> > were configuration changes.
> > I imagine that another snapshot is warranted soon with all the other
> > various configuration changes being made recently.
> 
> i would have leaned the other direction ... give them longer to bake by devs
> building the latest git before kicking out a "release" that other people might
> expect to be pretty stable.
> -mike

I agree with Mike here.  A blatant bug might warrant a new release,
autotool changes... not so much.  Better we let them simmer and be
worked on so they stabilize until the next EOY release.


Corinna

Re: 4.2.0

[Jeff Johnston]

Fine by me.

On Fri, Feb 4, 2022 at 4:23 AM Corinna Vinschen <vinschen@redhat.com> wrote:

> On Feb  3 20:23, Mike Frysinger wrote:
> > On 03 Feb 2022 12:50, Jeff Johnston wrote:
> > > That was the official yearly snapshot.  Newlib was bumped to 4.2.0 as
> there
> > > were configuration changes.
> > > I imagine that another snapshot is warranted soon with all the other
> > > various configuration changes being made recently.
> >
> > i would have leaned the other direction ... give them longer to bake by
> devs
> > building the latest git before kicking out a "release" that other people
> might
> > expect to be pretty stable.
> > -mike
>
> I agree with Mike here.  A blatant bug might warrant a new release,
> autotool changes... not so much.  Better we let them simmer and be
> worked on so they stabilize until the next EOY release.
>
>
> Corinna
>
>