[Buildroot] 2015.08 release goals

[Buildroot] 2015.08 release goals

[Thomas Petazzoni]

Hello,

Since 2015.05-rc1 is approaching, we will stop merging new features. So
I've started collecting a list of release goals for 2015.08 at
http://elinux.org/Buildroot:2015.08_Release_Goals.

This is not intended to be an exhaustive list of all the package
updates and so on, only the "big" items, either infrastructure changes
or major package changes/updates.

People are welcome to help on those big topics by reviewing/testing the
patch series that have already been proposed.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2015.08 release goals

[Ryan Barnett]

Thomas, All,

On Sun, May 3, 2015 at 4:53 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> Since 2015.05-rc1 is approaching, we will stop merging new features. So
> I've started collecting a list of release goals for 2015.08 at
> http://elinux.org/Buildroot:2015.08_Release_Goals.
>
> This is not intended to be an exhaustive list of all the package
> updates and so on, only the "big" items, either infrastructure changes
> or major package changes/updates.

We were hoping that our outstanding SE Linux patchset could be
targeted for merge during this time too. The patches have seen a lot
of changes since the last version including a reduction in the number
of patches. We plan on sending out a v5 towards the end of this month.

I have updated the elinux page linked above with this.

Thanks,
-Ryan

-- 
Ryan Barnett / Sr Software Engineer
Airborne Information Systems / Security Systems and Software
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
ryan.barnett at rockwellcollins.com
www.rockwellcollins.com

[Buildroot] 2015.08 release goals

[Thomas Petazzoni]

Ryan,

On Mon, 4 May 2015 09:20:50 -0500, Ryan Barnett wrote:

> We were hoping that our outstanding SE Linux patchset could be
> targeted for merge during this time too.

For 2015.05 it's obviously too late, Peter will probably cut -rc1
either today or in the next few days.

> The patches have seen a lot
> of changes since the last version including a reduction in the number
> of patches. We plan on sending out a v5 towards the end of this month.

Have you been able to work with upstream about the Python stuff?

Also, I think if you want to get things merged in 2015.08, it would be
good to increase the frequency of the patch submissions to take into
account review comments and so on. If you wait several months between
each iteration, then it's going to take ages because reviewers are
losing/forgetting the context and you kind of start over again from
scratch each time.

> I have updated the elinux page linked above with this.

Good!

Thanks a lot for working on this!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2015.08 release goals

[Ryan Barnett]

Thomas,

On Mon, May 4, 2015 at 9:30 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Ryan,
>
> On Mon, 4 May 2015 09:20:50 -0500, Ryan Barnett wrote:
>
>> The patches have seen a lot
>> of changes since the last version including a reduction in the number
>> of patches. We plan on sending out a v5 towards the end of this month.
>
> Have you been able to work with upstream about the Python stuff?

We no longer are doing the "Python stuff" in the audit package - which
is what you are referring to here.

> Also, I think if you want to get things merged in 2015.08, it would be
> good to increase the frequency of the patch submissions to take into
> account review comments and so on. If you wait several months between
> each iteration, then it's going to take ages because reviewers are
> losing/forgetting the context and you kind of start over again from
> scratch each time.

Correct - we will make sure that we respond in a much more timely
manner since this has become a priority for us.

Thanks,
-Ryan

-- 
Ryan Barnett / Sr Software Engineer
Airborne Information Systems / Security Systems and Software
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
ryan.barnett at rockwellcollins.com
www.rockwellcollins.com

[Buildroot] 2015.08 release goals

[Thomas Petazzoni]

Ryan,

On Mon, 4 May 2015 09:45:59 -0500, Ryan Barnett wrote:

> > Have you been able to work with upstream about the Python stuff?
> 
> We no longer are doing the "Python stuff" in the audit package - which
> is what you are referring to here.

Yes, exactly. So what was the solution to overcome the
cross-compilation issue of the upstream audit logic?

> 
> > Also, I think if you want to get things merged in 2015.08, it would be
> > good to increase the frequency of the patch submissions to take into
> > account review comments and so on. If you wait several months between
> > each iteration, then it's going to take ages because reviewers are
> > losing/forgetting the context and you kind of start over again from
> > scratch each time.
> 
> Correct - we will make sure that we respond in a much more timely
> manner since this has become a priority for us.

Excellent. I will also try to dedicate some time to reviewing/testing
your submissions, since I did that in the past for the SELinux stuff.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2015.08 release goals

[Ryan Barnett]

Thomas,

On Mon, May 4, 2015 at 9:48 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Ryan,
>
> On Mon, 4 May 2015 09:45:59 -0500, Ryan Barnett wrote:
>
>> > Have you been able to work with upstream about the Python stuff?
>>
>> We no longer are doing the "Python stuff" in the audit package - which
>> is what you are referring to here.
>
> Yes, exactly. So what was the solution to overcome the
> cross-compilation issue of the upstream audit logic?

We have a patch that is based on
https://www.redhat.com/archives/linux-audit/2012-November/msg00000.html

More detail will be provided when v5 of the patchset is sent out in
the next week or two.

Thanks,
-Ryan

-- 
Ryan Barnett / Sr Software Engineer
Airborne Information Systems / Security Systems and Software
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
ryan.barnett at rockwellcollins.com
www.rockwellcollins.com

[Buildroot] 2015.08 release goals

[Arnout Vandecappelle]

On 04/05/15 16:45, Ryan Barnett wrote:
> Thomas,
> 
> On Mon, May 4, 2015 at 9:30 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
[snip]
> 
>> Also, I think if you want to get things merged in 2015.08, it would be
>> good to increase the frequency of the patch submissions to take into
>> account review comments and so on. If you wait several months between
>> each iteration, then it's going to take ages because reviewers are
>> losing/forgetting the context and you kind of start over again from
>> scratch each time.
> 
> Correct - we will make sure that we respond in a much more timely
> manner since this has become a priority for us.

 It would also help if there would be a subset of the series that has some
relevance on its own and that could be reviewed and applied first. A 27-patch
series of large changes is just daunting...

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

[Buildroot] 2015.08 release goals

[Thomas Petazzoni]

Dear Arnout Vandecappelle,

On Mon, 04 May 2015 18:38:12 +0200, Arnout Vandecappelle wrote:

>  It would also help if there would be a subset of the series that has some
> relevance on its own and that could be reviewed and applied first. A 27-patch
> series of large changes is just daunting...

Well, in practice the patch series is like 5 or 7 difficult patches,
the rest being just "let's enable SELinux support in package foo or
bar", and those patches are not very complex to review in general.

But yes, reviewing a 27 patches series takes a while.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com