On 16.07.2014 06:16, Carl Worth wrote:
Michel Dänzer mic...@daenzer.net writes:
Quite frankly, my real concern with all of this is not that the driver
maintainers will propose something bad, but that I will inadvertently
botch something while cherry-picking or merging a conflict, etc. that I
On 09.07.2014 08:10, Carl Worth wrote:
3. I'd like to receive a testing report from each driver team
This is the meat of my proposal. I'm requesting that each driver
team designate one (or more) people that will be responsible for
running (or collecting) tests for each
On Tue, Jul 15, 2014 at 2:18 AM, Michel Dänzer mic...@daenzer.net wrote:
On 09.07.2014 08:10, Carl Worth wrote:
3. I'd like to receive a testing report from each driver team
This is the meat of my proposal. I'm requesting that each driver
team designate one (or more) people
Michel Dänzer mic...@daenzer.net writes:
configurations are. All I need is something along the lines of:
The radeon team is OK with releasing commit foo
...
[snip of the rest of my proposal]
This sounds good, but...
Good! Thanks for reading this and giving me some
I've been doing stable-branch release of mesa for close to a year now.
In all of that time, there's one thing that I've never been very
comfortable with. Namely, release candidates are not tested very
thoroughly prior to release.[*] I'm glad that we haven't had any major
problems yet with broken
