On 06/06/2014 09:52 PM, Laurent Carlier wrote:
> Le vendredi 6 juin 2014 21:38:23, vous avez écrit :
>> On 06/06/2014 09:35 PM, Laurent Carlier wrote:
>>> Le vendredi 6 juin 2014, 21:20:12 Ian Romanick a écrit :
Mesa 10.2 has been released! Mesa 10.2 is a feature release that
includes man
Le vendredi 6 juin 2014 21:38:23, vous avez écrit :
> On 06/06/2014 09:35 PM, Laurent Carlier wrote:
> > Le vendredi 6 juin 2014, 21:20:12 Ian Romanick a écrit :
> >> Mesa 10.2 has been released! Mesa 10.2 is a feature release that
> >> includes many updates and enhancements. The full list is avail
Le vendredi 6 juin 2014, 21:38:23 Ian Romanick a écrit :
> On 06/06/2014 09:35 PM, Laurent Carlier wrote:
> > Le vendredi 6 juin 2014, 21:20:12 Ian Romanick a écrit :
> >> Mesa 10.2 has been released! Mesa 10.2 is a feature release that
> >> includes many updates and enhancements. The full list is
On 06/06/2014 09:35 PM, Laurent Carlier wrote:
> Le vendredi 6 juin 2014, 21:20:12 Ian Romanick a écrit :
>> Mesa 10.2 has been released! Mesa 10.2 is a feature release that
>> includes many updates and enhancements. The full list is available in
>> the release notes file in docs/relnotes/10.2.html
Le vendredi 6 juin 2014, 21:20:12 Ian Romanick a écrit :
> Mesa 10.2 has been released! Mesa 10.2 is a feature release that
> includes many updates and enhancements. The full list is available in
> the release notes file in docs/relnotes/10.2.html.
>
It fails to build here:
make[3]: Leaving direc
Mesa 10.2 has been released! Mesa 10.2 is a feature release that
includes many updates and enhancements. The full list is available in
the release notes file in docs/relnotes/10.2.html.
The tag in the GIT repository for Mesa 10.2 is 'mesa-10.2'. I have
verified that the tag is in the correct plac
(Resend with GPG signature.)
Mesa 10.2 release candidate 5 is now available for testing. The current
plan of record was for this to be the last release candidate, and the
10.2 release is planned for Friday, June 6th.
The tag in the GIT repository for Mesa 10.2-rc5 is 'mesa-10.2-rc5'. I
have ver
Mesa 10.2 release candidate 5 is now available for testing. The current
plan of record was for this to be the last release candidate, and the
10.2 release is planned for Friday, June 6th.
The tag in the GIT repository for Mesa 10.2-rc5 is 'mesa-10.2-rc5'. I
have verified that the tag is in the c
Mesa 10.2 release candidate 4 is now available for testing. The current
plan of record was for this to be the last release candidate, and the
10.2 release is planned for Friday, May 30th.
There are *45* patches in this release candidate. 21 of them are in the
freedreno driver, and 2 of them are
On Fri, May 23, 2014 at 12:50 PM, Ian Romanick wrote:
> On 05/20/2014 06:31 AM, Rob Clark wrote:
>> Hey Ian,
>>
>> I wonder to what extent you might tolerate a late freedreno pull req?
>> I've backported nearly all of the recent freedreno commits on master
>> to a 10.2 based branch:
>>
>> https:
On 05/20/2014 06:31 AM, Rob Clark wrote:
> Hey Ian,
>
> I wonder to what extent you might tolerate a late freedreno pull req?
> I've backported nearly all of the recent freedreno commits on master
> to a 10.2 based branch:
>
> https://github.com/freedreno/mesa/commits/freedreno-10.2
Are these
Hey Ian,
I wonder to what extent you might tolerate a late freedreno pull req?
I've backported nearly all of the recent freedreno commits on master
to a 10.2 based branch:
https://github.com/freedreno/mesa/commits/freedreno-10.2
I guess it will be a while before 10.3 makes it in to distros, so
Mesa 10.2 release candidate 3 is now available for testing. The current
plan of record is to have an additional release candidate each Friday
until the 10.2 release on Friday, May 30th.
The tag in the GIT repository for Mesa 10.2-rc3 is 'mesa-10.2-rc3'. I
have verified that the tag is in the cor
On Wed, May 14, 2014 at 3:14 PM, Ian Romanick wrote:
> On 05/09/2014 08:28 PM, Ian Romanick wrote:
>> (This is a re-send with a GPG signature.)
>>
>> Mesa 10.2 release candidate 2 is now available for testing. The current
>> plan of record is to have an additional release candidate each Friday
>>
On 05/09/2014 08:28 PM, Ian Romanick wrote:
> (This is a re-send with a GPG signature.)
>
> Mesa 10.2 release candidate 2 is now available for testing. The current
> plan of record is to have an additional release candidate each Friday
> until the 10.2 release on Friday, May 30th (correcte from t
(This is a re-send with a GPG signature.)
Mesa 10.2 release candidate 2 is now available for testing. The current
plan of record is to have an additional release candidate each Friday
until the 10.2 release on Friday, May 30th (correcte from the RC1
announcement e-mail).
Note: there is a possibl
Mesa 10.2 release candidate 2 is now available for testing. The current
plan of record is to have an additional release candidate each Friday
until the 10.2 release on Friday, May 30th (correcte from the RC1
announcement e-mail).
Note: there is a possible front-buffer rendering regression in the
On 03/05/14 05:48, Ian Romanick wrote:
> Mesa 10.2 release candidate 1 is now available for testing. The current
> plan of record is to have an additional release candidate each Friday
> until the 10.2 release on Friday, May 28th.
>
> The tag in the GIT repository for Mesa 10.2-rc1 is 'mesa-10.2-
Mesa 10.2 release candidate 1 is now available for testing. The current
plan of record is to have an additional release candidate each Friday
until the 10.2 release on Friday, May 28th.
The tag in the GIT repository for Mesa 10.2-rc1 is 'mesa-10.2-rc1'.
After Eric's suggestion, I have also pushe
On 04/04/2014 05:18 PM, Ian Romanick wrote:
> Fast forwarding 3 months from the 10.1 release (March 4th, planned for
> February 28th) is May 30th. I'd like to propose the following set of dates:
(Slight edits to the quoted e-mail to account for changes to the RC plan.)
> May 2nd: Feature freeze
On 04/11/2014 10:07 AM, Eric Anholt wrote:
> Ian Romanick writes:
>
>> On 04/07/2014 03:27 PM, Eric Anholt wrote:
>>> Ian Romanick writes:
>>>
On 04/07/2014 09:14 AM, Eric Anholt wrote:
> Ian Romanick writes:
>
>> On 04/04/2014 05:52 PM, Matt Turner wrote:
>>> On Fri, Apr 4
Ian Romanick writes:
> On 04/07/2014 03:27 PM, Eric Anholt wrote:
>> Ian Romanick writes:
>>
>>> On 04/07/2014 09:14 AM, Eric Anholt wrote:
Ian Romanick writes:
> On 04/04/2014 05:52 PM, Matt Turner wrote:
>> On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick
>> wrote:
>>
On 04/07/2014 03:27 PM, Eric Anholt wrote:
> Ian Romanick writes:
>
>> On 04/07/2014 09:14 AM, Eric Anholt wrote:
>>> Ian Romanick writes:
>>>
On 04/04/2014 05:52 PM, Matt Turner wrote:
> On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
>> Fast forwarding 3 months from the 10.1
Ian Romanick writes:
> On 04/07/2014 09:14 AM, Eric Anholt wrote:
>> Ian Romanick writes:
>>
>>> On 04/04/2014 05:52 PM, Matt Turner wrote:
On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
> Fast forwarding 3 months from the 10.1 release (March 4th, planned for
> February 28th)
On 04/07/2014 11:47 AM, Ian Romanick wrote:
> On 04/07/2014 09:14 AM, Eric Anholt wrote:
>> Ian Romanick writes:
>>
>>> On 04/04/2014 05:52 PM, Matt Turner wrote:
On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
> Fast forwarding 3 months from the 10.1 release (March 4th, planned for
On 04/07/2014 09:14 AM, Eric Anholt wrote:
> Ian Romanick writes:
>
>> On 04/04/2014 05:52 PM, Matt Turner wrote:
>>> On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
Fast forwarding 3 months from the 10.1 release (March 4th, planned for
February 28th) is May 30th. I'd like to prop
Ian Romanick writes:
> On 04/04/2014 05:52 PM, Matt Turner wrote:
>> On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
>>> Fast forwarding 3 months from the 10.1 release (March 4th, planned for
>>> February 28th) is May 30th. I'd like to propose the following set of dates:
>>>
>>> May 2nd: Fe
On 04/04/2014 05:52 PM, Matt Turner wrote:
> On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
>> Fast forwarding 3 months from the 10.1 release (March 4th, planned for
>> February 28th) is May 30th. I'd like to propose the following set of dates:
>>
>> May 2nd: Feature freeze / 10.2 branch cre
On 04/04/2014 05:52 PM, Matt Turner wrote:
> On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
>> Fast forwarding 3 months from the 10.1 release (March 4th, planned for
>> February 28th) is May 30th. I'd like to propose the following set of dates:
>>
>> May 2nd: Feature freeze / 10.2 branch cre
On Fri, Apr 4, 2014 at 5:18 PM, Ian Romanick wrote:
> Fast forwarding 3 months from the 10.1 release (March 4th, planned for
> February 28th) is May 30th. I'd like to propose the following set of dates:
>
> May 2nd: Feature freeze / 10.2 branch created.
>
> May 16th: RC1
Same comment as last tim
Fast forwarding 3 months from the 10.1 release (March 4th, planned for
February 28th) is May 30th. I'd like to propose the following set of dates:
May 2nd: Feature freeze / 10.2 branch created.
May 16th: RC1
May 23rd: RC2
May 30th: 10.2 final release
Does this plan sound reasonable?
_
31 matches
Mail list logo
