This post is not to be taken as a flame or anything (or remotely) similar, but...
Taking a quick look at the mesa/drm gitlog, it seems there haven't been any tarball releases since the last year, and quite irregular, as both the 2.2.0 and the 2.3.0 versions were released 'more or less' in the same time frame
Googling for a concrete release date doesn't even help, as there's many changes a day, curiously observed allmost all of them related to the nouveau driver, but that's ok for me, as there's tons of updates for the general DRM and the part I'm really interested in, the Intel driver...
Anyway... is this development cycle leading to a new release or will we have to make a clone of the git tree forever? Last time I did it, the internal version said '2.3.1' (looking at the .pc file) and it had some flaws like invalid memory allocations or faulty allocations at all...
Would be nice if they come to release a new version by the end of the year, at least... because it's not nice for users to be presented with the only choice between using the now 1-year aged DRM or biting the bullet with a git clone...
Julio
Taking a quick look at the mesa/drm gitlog, it seems there haven't been any tarball releases since the last year, and quite irregular, as both the 2.2.0 and the 2.3.0 versions were released 'more or less' in the same time frame
Googling for a concrete release date doesn't even help, as there's many changes a day, curiously observed allmost all of them related to the nouveau driver, but that's ok for me, as there's tons of updates for the general DRM and the part I'm really interested in, the Intel driver...
Anyway... is this development cycle leading to a new release or will we have to make a clone of the git tree forever? Last time I did it, the internal version said '2.3.1' (looking at the .pc file) and it had some flaws like invalid memory allocations or faulty allocations at all...
Would be nice if they come to release a new version by the end of the year, at least... because it's not nice for users to be presented with the only choice between using the now 1-year aged DRM or biting the bullet with a git clone...
Julio
Comment