I'd like to remove the linaro-android- prefix from all our bps, for all bps filed for 12.03 and beyond. Everyone cool with this?
On Thu, Mar 8, 2012 at 11:09 PM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
I'd like to remove the linaro-android- prefix from all our bps, for all bps filed for 12.03 and beyond. Everyone cool with this?
Sounds good... only place where this might still be needed is for session blueprints at connect. For engineering blueprints used for monthly execution the prefix requirement is long gone if it ever existed...
CCing infra folks that could nack that statement and veto ... so hold of a couple days to allow them to chime in...
Thanks!
On 8 March 2012 17:22, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:09 PM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
I'd like to remove the linaro-android- prefix from all our bps, for all bps filed for 12.03 and beyond. Everyone cool with this?
Sounds good... only place where this might still be needed is for session blueprints at connect. For engineering blueprints used for monthly execution the prefix requirement is long gone if it ever existed...
CCing infra folks that could nack that statement and veto ... so hold of a couple days to allow them to chime in...
Blueprints for Connect will continue to need this. We will hopefully not *require* blueprints at Q2.12 to create meetings, however, if a meeting is created via a blueprint, it will continue to require the linaro-android-q2-12 prefix.
Chris
On Thu, Mar 8, 2012 at 11:24 PM, Chris Johnston chris.johnston@linaro.netwrote:
On 8 March 2012 17:22, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:09 PM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
I'd like to remove the linaro-android- prefix from all our bps, for all bps filed for 12.03 and beyond. Everyone cool with this?
Sounds good... only place where this might still be needed is for session blueprints at connect. For engineering blueprints used for monthly execution the prefix requirement is long gone if it ever existed...
CCing infra folks that could nack that statement and veto ... so hold of a couple days to allow them to chime in...
Blueprints for Connect will continue to need this. We will hopefully not *require* blueprints at Q2.12 to create meetings, however, if a meeting is created via a blueprint, it will continue to require the linaro-android-q2-12 prefix.
What other "easy" options would we have? Maybe guessing from the session owner etc. what it's about? or maybe from the project they are filed against would also work?
On 8 March 2012 17:32, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:24 PM, Chris Johnston <chris.johnston@linaro.net
wrote:
Blueprints for Connect will continue to need this. We will hopefully not *require* blueprints at Q2.12 to create meetings, however, if a meeting is created via a blueprint, it will continue to require the linaro-android-q2-12 prefix.
What other "easy" options would we have? Maybe guessing from the session owner etc. what it's about? or maybe from the project they are filed against would also work?
The Summit codebase is not flexible enough to perform any checks like this, and with the new abilities of creating meetings inside of summit, I don't believe it would be worth the dev time to try to make this work for Connect while leaving it as is for UDS.
Chris
On Thu, Mar 8, 2012 at 11:43 PM, Chris Johnston chris.johnston@linaro.netwrote:
On 8 March 2012 17:32, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:24 PM, Chris Johnston < chris.johnston@linaro.net> wrote:
Blueprints for Connect will continue to need this. We will hopefully not *require* blueprints at Q2.12 to create meetings, however, if a meeting is created via a blueprint, it will continue to require the linaro-android-q2-12 prefix.
What other "easy" options would we have? Maybe guessing from the session owner etc. what it's about? or maybe from the project they are filed against would also work?
The Summit codebase is not flexible enough to perform any checks like this, and with the new abilities of creating meetings inside of summit, I don't believe it would be worth the dev time to try to make this work for Connect while leaving it as is for UDS.
Thanks Chris. I think we can survive with this feature. Once you have all other wishlist and critical bugs resolved and wonder what's the next challenge for summit, remind me and we can resurrect this idea :).
Rock on!
On 8 March 2012 16:24, Chris Johnston chris.johnston@linaro.net wrote:
On 8 March 2012 17:22, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:09 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
I'd like to remove the linaro-android- prefix from all our bps, for all bps filed for 12.03 and beyond. Everyone cool with this?
Sounds good... only place where this might still be needed is for session blueprints at connect. For engineering blueprints used for monthly execution the prefix requirement is long gone if it ever existed...
The BP's for connect have a different prefix, linaro-platforms-q112-android etc then the general Android engineering BPs linaro-android.
CCing infra folks that could nack that statement and veto ... so hold of a couple days to allow them to chime in...
Blueprints for Connect will continue to need this. We will hopefully not *require* blueprints at Q2.12 to create meetings, however, if a meeting is created via a blueprint, it will continue to require the linaro-android-q2-12 prefix.
Chris
On 9 March 2012 10:48, Zach Pfeffer zach.pfeffer@linaro.org wrote:
The BP's for connect have a different prefix, linaro-platforms-q112-android etc then the general Android engineering BPs linaro-android.
As long as it stays that way, I have no objection. :-)
Chris
On Thu, Mar 8, 2012 at 11:22 PM, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:09 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
I'd like to remove the linaro-android- prefix from all our bps, for all bps filed for 12.03 and beyond. Everyone cool with this?
Sounds good... only place where this might still be needed is for session blueprints at connect. For engineering blueprints used for monthly execution the prefix requirement is long gone if it ever existed...
It should work. We seem to have missed the notice about the naming convention going away and acted on all the s.l.o errors. We fixed the parts in s.l.o that relied on the naming scheme a couple of months ago, so please go ahead.
CCing infra folks that could nack that statement and veto ... so hold of a couple days to allow them to chime in...
Thanks!
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
Okay the BPs on and after 12.03 have been changed.
Woot.
On 9 March 2012 01:13, Mattias Backman mattias.backman@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:22 PM, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 8, 2012 at 11:09 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
I'd like to remove the linaro-android- prefix from all our bps, for all bps filed for 12.03 and beyond. Everyone cool with this?
Sounds good... only place where this might still be needed is for session blueprints at connect. For engineering blueprints used for monthly execution the prefix requirement is long gone if it ever existed...
It should work. We seem to have missed the notice about the naming convention going away and acted on all the s.l.o errors. We fixed the parts in s.l.o that relied on the naming scheme a couple of months ago, so please go ahead.
CCing infra folks that could nack that statement and veto ... so hold of a couple days to allow them to chime in...
Thanks!
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On Fri, Mar 9, 2012 at 4:57 PM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
Okay the BPs on and after 12.03 have been changed.
Woot.
\o/ Yes, we can!! :-P
linaro-android@lists.linaro.org