Upcoming Yocto 1.2.1 "denzil" release this week.
Hello,
After a review of the QA full pass test report for Yocto 1.2.1, the release team has agreed to submit this release candidate as our final release for 1.2.1. Song Liu will organize the release readiness decision, and I expect Beth Flanagan will be able to perform the official release by the end of this week.
Unfortunately the timing of this is such that I will be out of the office for the rest of this week. Saul Wold can handle any questions/concerns in my absence.
Thanks so much to everyone who contributed work that went into 1.2.1! We now have 35 bugfixes and a few further enhancements to denzil since 1.2 to share with our users.
Scott
Signature · 3 lines
Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center
Quoted 10 lines · Scott Garman
Hello,
After a review of the QA full pass test report for Yocto 1.2.1, the release team has agreed to submit this release candidate as our final release for 1.2.1. Song Liu will organize the release readiness decision, and I expect Beth Flanagan will be able to perform the official release by the end of this week.
Unfortunately the timing of this is such that I will be out of the office for the rest of this week. Saul Wold can handle any questions/concerns in my absence.
Thanks so much to everyone who contributed work that went into 1.2.1! We now have 35 bugfixes and a few further enhancements to denzil since 1.2 to share with our users.
Scott
Hi Scott,
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Regards,
Signature · 5 lines
Jack Mitchell ([email protected]) Embedded Systems Engineer http://www.embed.me.uk --
Quoted 17 lines · Jack Mitchell
Quoted 16 lines · Scott Garman
Hello,
After a review of the QA full pass test report for Yocto 1.2.1, the release team has agreed to submit this release candidate as our final release for 1.2.1. Song Liu will organize the release readiness decision, and I expect Beth Flanagan will be able to perform the official release by the end of this week.
Unfortunately the timing of this is such that I will be out of the office for the rest of this week. Saul Wold can handle any questions/concerns in my absence.
Thanks so much to everyone who contributed work that went into 1.2.1! We now have 35 bugfixes and a few further enhancements to denzil since 1.2 to share with our users.
Quoted 6 lines
Quoted 2 lines
Scott
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Cheers,
Richard
Quoted 25 lines · Richard Purdie
Quoted 17 lines · Jack Mitchell
Quoted 16 lines · Scott Garman
Hello,
After a review of the QA full pass test report for Yocto 1.2.1, the release team has agreed to submit this release candidate as our final release for 1.2.1. Song Liu will organize the release readiness decision, and I expect Beth Flanagan will be able to perform the official release by the end of this week.
Unfortunately the timing of this is such that I will be out of the office for the rest of this week. Saul Wold can handle any questions/concerns in my absence.
Thanks so much to everyone who contributed work that went into 1.2.1! We now have 35 bugfixes and a few further enhancements to denzil since 1.2 to share with our users.
Quoted 6 lines
Quoted 2 lines
Scott
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Quoted 7 lines
Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Can you fill me in? Why would a point release include such a dramatic upgrade?
-M
Quoted 11 lines
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 10 lines · On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote:
Quoted 8 lines · Richard Purdie
Quoted 3 lines · Jack Mitchell
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
Quoted 7 lines
Quoted 4 lines
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Can you fill me in? Why would a point release include such a dramatic upgrade?
I think what we would be looking at would be just adding the fixes to allow the native packages to build against eglibc 2.16 so it can work on host distros that use it, not bringing eglibc 2.16 itself in for the target.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 16 lines · Paul Eggleton
Quoted 15 lines · On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote:
Quoted 12 lines · Richard Purdie
Quoted 3 lines · Jack Mitchell
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Quoted 6 lines
Quoted 2 lines
Can you fill me in? Why would a point release include such a dramatic upgrade?
I think what we would be looking at would be just adding the fixes to allow the native packages to build against eglibc 2.16 so it can work on host distros that use it, not bringing eglibc 2.16 itself in for the target.
Right, this would just be to allow edison to work on systems that have a native eglibc 2.16. I'm not convinced we have the patches worked out yet though. Target eglibc would remain with whatever is in edison (2.13?).
Cheers,
Richard
Quoted 20 lines · Richard Purdie
Quoted 19 lines · Paul Eggleton
Quoted 17 lines · On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote:
Quoted 5 lines · Richard Purdie
Quoted 3 lines · Jack Mitchell
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Quoted 7 lines
Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Can you fill me in? Why would a point release include such a dramatic upgrade?
Quoted 8 lines
Quoted 3 lines
I think what we would be looking at would be just adding the fixes to allow the native packages to build against eglibc 2.16 so it can work on host distros that use it, not bringing eglibc 2.16 itself in for the target.
Right, this would just be to allow edison to work on systems that have a native eglibc 2.16. I'm not convinced we have the patches worked out yet though. Target eglibc would remain with whatever is in edison (2.13?).
I assume you mean denzil, not edison, or do we also need to be planning a 1.1.3?
Sau!
Quoted 11 lines
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 37 lines · Saul Wold
Quoted 36 lines · Richard Purdie
Quoted 32 lines · Paul Eggleton
Quoted 15 lines · On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote:
Quoted 12 lines · Richard Purdie
Quoted 5 lines · Jack Mitchell
Are Khems eglibc patches going to make it in for this - 2.16 is playing
havoc with my builds at the moment and surely will with everyone else when the major distros catch up.Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
Quoted 8 lines
Quoted 4 lines
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Can you fill me in? Why would a point release include such a dramatic upgrade?
I think what we would be looking at would be just adding the fixes to allow the
native packages to build against eglibc 2.16 so it can work on host distros
that use it, not bringing eglibc 2.16 itself in for the target.
Quoted 6 lines
Quoted 4 lines
Right, this would just be to allow edison to work on systems that have a native eglibc 2.16. I'm not convinced we have the patches worked out yet though. Target eglibc would remain with whatever is in edison (2.13?).
I assume you mean denzil, not edison, or do we also need to be planning a 1.1.3?
Personally, I'm hoping we at least keep accepted patches to the edison branch... and decide about a release later.
-M
Quoted 21 lines
Sau!
Quoted 11 lines
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 4 lines · Richard Purdie
Right, this would just be to allow edison to work on systems that have a native eglibc 2.16. I'm not convinced we have the patches worked out yet though. Target eglibc would remain with whatever is in edison (2.13?).
Well. The patches are sort of things you would get in a package using gnulib when they update
to newer gnulib but I have been a bit conservative in them so only undefine it if its defined, as far
as patches for native packages are concerned I think they are good and can be taken in even before
we take eglibc 2.16 in. Since they are be indendent of libc version
Just a general update for 1.1.2 (Edison). We're planning to release it next week and currently it is under QA testing. There're bugs(10+) filed against it which are marked WON'T FIX (lots of them relate to multilib) due to the facts of resources and amount of work involved to back port certain patches, etc. We'll add detailed information about these bugs in the release note. Also, as always, the community are welcome to step up and maintain it going forward.
Thanks,
Jessica
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of McClintock Matthew-B29882
Sent: Wednesday, July 11, 2012 1:43 PM
To: Patches and discussions about the oe-core layer
Cc: McClintock Matthew-B29882
Subject: Re: [OE-core] Upcoming Yocto 1.2.1 "denzil" release this week.
Quoted 35 lines · Saul Wold
Quoted 34 lines · Richard Purdie
Quoted 30 lines · Paul Eggleton
Quoted 14 lines · On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote:
Quoted 11 lines · Richard Purdie
Quoted 4 lines · Jack Mitchell
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
Quoted 8 lines
Quoted 4 lines
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Can you fill me in? Why would a point release include such a dramatic upgrade?
I think what we would be looking at would be just adding the fixes to allow the native packages to build against eglibc 2.16 so it can work on host distros that use it, not bringing eglibc 2.16 itself in for the target.
Quoted 6 lines
Quoted 4 lines
Right, this would just be to allow edison to work on systems that
have a native eglibc 2.16. I'm not convinced we have the patches
worked out yet though. Target eglibc would remain with whatever is in edison (2.13?).I assume you mean denzil, not edison, or do we also need to be planning a 1.1.3?
Personally, I'm hoping we at least keep accepted patches to the edison branch... and decide about a release later.
-M
Quoted 17 lines
Sau!
Quoted 11 lines
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 1 line · Jessica
Just a general update for 1.1.2 (Edison). We're planning to release it next week and currently it is under QA testing. There're bugs(10+) filed against it which are marked WON'T FIX (lots of them relate to multilib) due to the facts of resources and amount of work involved to back port certain patches, etc. We'll add detailed information about these bugs in the release note. Also, as always, the community are welcome to step up and maintain it going forward.
Thanks for the update.
-M
Quoted 89 lines
Thanks,
Jessica-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of McClintock Matthew-B29882
Sent: Wednesday, July 11, 2012 1:43 PM
To: Patches and discussions about the oe-core layer
Cc: McClintock Matthew-B29882
Subject: Re: [OE-core] Upcoming Yocto 1.2.1 "denzil" release this week.Quoted 35 lines · Saul Wold
Quoted 34 lines · Richard Purdie
Quoted 30 lines · Paul Eggleton
Quoted 14 lines · On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote:
Quoted 11 lines · Richard Purdie
Quoted 4 lines · Jack Mitchell
Are Khems eglibc patches going to make it in for this - 2.16 is playing havoc with my builds at the moment and surely will with everyone else when the major distros catch up.
Its too late to get those pieces into 1.2.1, they're not even in master yet, let alone in a stable release branch.
Quoted 8 lines
Quoted 4 lines
I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, then port them to the denzil branch quickly post release so they'd make any 1.2.2 release and are available on the git branch for people using the stable branch.
Can you fill me in? Why would a point release include such a dramatic upgrade?
I think what we would be looking at would be just adding the fixes to allow the native packages to build against eglibc 2.16 so it can work on host distros that use it, not bringing eglibc 2.16 itself in for the target.
Quoted 6 lines
Quoted 4 lines
Right, this would just be to allow edison to work on systems that
have a native eglibc 2.16. I'm not convinced we have the patches
worked out yet though. Target eglibc would remain with whatever is in edison (2.13?).I assume you mean denzil, not edison, or do we also need to be planning a 1.1.3?
Personally, I'm hoping we at least keep accepted patches to the edison branch... and decide about a release later.
-M
Quoted 17 lines
Sau!
Quoted 11 lines
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-coreQuoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core