Upstream-Status finally @ 100%

Upstream-Status finally @ 100%

[Saul Wold]

We finally did it!

After getting some final patches yesterday, we made it to 100% with 
patch Upsteam-Status.

Total Patches Files: 1243
All Upstream-Status: 1243
Fix Upstream-Status: 0
Need Upstream-Status: 0
Pending Upstream-Status: 461

This means we have 461 patches to now work their way into the Upstream
communities.

Let's work to maintain this, I will be watching incoming patches and 
using a check script to verify that patches have Upstream-Status.

Thanks to all those people who worked to get Upstream-Status into their 
patches.

Sau!

Re: [yocto] Upstream-Status finally @ 100%

[Paul Eggleton]

On Wednesday 08 February 2012 09:34:56 Osier-mixon, Jeffrey wrote:
> This sounds fantastic, and I'd love to create a page on the website
> reflecting this. Just so I am clear, what exactly is this 100% of? Do we
> have no local patches to upstream projects at all?

Not quite - we still have most of the patches, it's just we've now declared on 
each and every one whether it can be/has been upstreamed.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [yocto] Upstream-Status finally @ 100%

[Khem Raj]

On Wed, Feb 8, 2012 at 9:34 AM, Osier-mixon, Jeffrey
<jeffrey.osier-mixon@intel.com> wrote:
> This sounds fantastic, and I'd love to create a page on the website
> reflecting this. Just so I am clear, what exactly is this 100% of? Do we
> have no local patches to upstream projects at all?

it means that all patches have a field 'Upstream-Status'
and for most of them it reflects the status of patch w.r.t. upstream
of given package

Re: [yocto] Upstream-Status finally @ 100%

[Saul Wold]

On 02/08/2012 10:04 AM, Osier-mixon, Jeffrey wrote:
> Ah, documentation :)  excellent
>

Jefro:

You can get more info about this from Mark's OE page:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

The Key thing to note on my numbers is that we have 461 patches that 
could potentially be up-streamed to other communities, depending the 
status of those communities, from active communities accepting patches 
to upstream source that is just download-able with no activity or 
maintainers.

We have 1243 patches overall, which include OE Specific configuration 
patches and Embedded specific tweaks to various upstreams that may not 
be appropriate or acceptable to the upstream community.

Sau!




> On Wed, Feb 8, 2012 at 9:45 AM, Khem Raj <raj.khem@gmail.com
> <mailto:raj.khem@gmail.com>> wrote:
>
>     On Wed, Feb 8, 2012 at 9:34 AM, Osier-mixon, Jeffrey
>     <jeffrey.osier-mixon@intel.com
>     <mailto:jeffrey.osier-mixon@intel.com>> wrote:
>      > This sounds fantastic, and I'd love to create a page on the website
>      > reflecting this. Just so I am clear, what exactly is this 100%
>     of? Do we
>      > have no local patches to upstream projects at all?
>
>     it means that all patches have a field 'Upstream-Status'
>     and for most of them it reflects the status of patch w.r.t. upstream
>     of given package
>
>
>
>
> --
> Jeff Osier-Mixon http://jefro.net/blog
> Yocto Project Community Manager @Intel http://yoctoproject.org
> <http://yoctoproject.org/>
>

Re: Upstream-Status finally @ 100%

[Paul Menzel]

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

Am Mittwoch, den 08.02.2012, 10:45 -0800 schrieb Saul Wold:
> On 02/08/2012 10:04 AM, Osier-mixon, Jeffrey wrote:
> > Ah, documentation :)  excellent

Saul, thank you for the update and enforcing that requirement from the
commit and patch message guidelines.

> Jefro:
> 
> You can get more info about this from Mark's OE page:
> http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
> 
> The Key thing to note on my numbers is that we have 461 patches that 
> could potentially be up-streamed to other communities, depending the 
> status of those communities, from active communities accepting patches 
> to upstream source that is just download-able with no activity or 
> maintainers.

Emphasis should be laid on *could*. Sending these patches upstream still
has to be done most of the time and most developers do not spend time
with that. I hope that will improve in the future somehow.

> We have 1243 patches overall, which include OE Specific configuration 
> patches and Embedded specific tweaks to various upstreams that may not 
> be appropriate or acceptable to the upstream community.



Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]