From 6c0c95d6045d2d2b4e6a3a2f11457850031c57bc Mon Sep 17 00:00:00 2001 From: marha Date: Fri, 22 Aug 2014 21:55:11 +0200 Subject: fontconfig libxcb/xcb-proto mesa xkeyboard-config git update 22 Aug 2014 libxcb/xcb-proto commit 8e3db42d67a0035bb16d16da28bd5eea7a269178 xkeyboard-config commit 10fce2c2baae471795d069f3a5f1307eedb9ff0a fontconfig commit 286cdc9c10b0453c25950103b6a1f7170d15bfdc mesa commit 97d03b9366bfa55b27feb92aa5afacd9c5f6f421 --- mesalib/docs/GL3.txt | 58 ++++++-- mesalib/docs/autoconf.html | 54 +++++-- mesalib/docs/devinfo.html | 300 +++++++++++++++++++++++++++++++++----- mesalib/docs/index.html | 6 + mesalib/docs/relnotes.html | 1 + mesalib/docs/relnotes/10.2.6.html | 118 +++++++++++++++ mesalib/docs/relnotes/10.3.html | 17 ++- 7 files changed, 486 insertions(+), 68 deletions(-) create mode 100644 mesalib/docs/relnotes/10.2.6.html (limited to 'mesalib/docs') diff --git a/mesalib/docs/GL3.txt b/mesalib/docs/GL3.txt index 3d610f6e1..76412c3dc 100644 --- a/mesalib/docs/GL3.txt +++ b/mesalib/docs/GL3.txt @@ -94,18 +94,18 @@ GL 4.0, GLSL 4.00: GL_ARB_draw_buffers_blend DONE (i965, nv50, nvc0, r600, radeonsi, softpipe) GL_ARB_draw_indirect DONE (i965, nvc0, radeonsi, softpipe, llvmpipe) - GL_ARB_gpu_shader5 started + GL_ARB_gpu_shader5 DONE (i965, nvc0) - 'precise' qualifier DONE - - Dynamically uniform sampler array indices started (Chris) - - Dynamically uniform UBO array indices started (Chris) + - Dynamically uniform sampler array indices DONE () + - Dynamically uniform UBO array indices DONE () - Implicit signed -> unsigned conversions DONE - - Fused multiply-add DONE (i965, nvc0) - - Packing/bitfield/conversion functions DONE (i965, nvc0, r600) - - Enhanced textureGather DONE (i965, nvc0, r600, radeonsi) - - Geometry shader instancing DONE (i965, nvc0) - - Geometry shader multiple streams DONE (i965, nvc0) - - Enhanced per-sample shading DONE (i965, r600) - - Interpolation functions DONE (i965) + - Fused multiply-add DONE () + - Packing/bitfield/conversion functions DONE (r600) + - Enhanced textureGather DONE (r600, radeonsi) + - Geometry shader instancing DONE () + - Geometry shader multiple streams DONE () + - Enhanced per-sample shading DONE (r600) + - Interpolation functions DONE () - New overload resolution rules DONE GL_ARB_gpu_shader_fp64 started (Dave) GL_ARB_sample_shading DONE (i965, nv50, nvc0, radeonsi) @@ -125,13 +125,13 @@ GL 4.1, GLSL 4.10: GL_ARB_get_program_binary DONE (0 binary formats) GL_ARB_separate_shader_objects DONE (all drivers) GL_ARB_shader_precision started (Micah) - GL_ARB_vertex_attrib_64bit not started + GL_ARB_vertex_attrib_64bit started (Dave) GL_ARB_viewport_array DONE (i965, nv50, nvc0, r600) GL 4.2, GLSL 4.20: - GL_ARB_texture_compression_bptc not started + GL_ARB_texture_compression_bptc DONE (i965, nvc0, r600, radeonsi) GL_ARB_compressed_texture_pixel_storage DONE (all drivers) GL_ARB_shader_atomic_counters DONE (i965) GL_ARB_texture_storage DONE (all drivers) @@ -147,7 +147,7 @@ GL 4.2, GLSL 4.20: GL 4.3, GLSL 4.30: GL_ARB_arrays_of_arrays started (Timothy) - GL_ARB_ES3_compatibility DONE (i965) + GL_ARB_ES3_compatibility DONE (all drivers that support GLSL 3.30) GL_ARB_clear_buffer_object DONE (all drivers) GL_ARB_compute_shader started (currently stalled) GL_ARB_copy_image DONE (i965) @@ -182,6 +182,38 @@ GL 4.4, GLSL 4.40: GL_ARB_texture_stencil8 not started GL_ARB_vertex_type_10f_11f_11f_rev DONE (i965, nv50, nvc0, r600, radeonsi) +GL 4.5, GLSL 4.50: + + GL_ARB_ES3_1_compatibility not started + GL_ARB_clip_control not started + GL_ARB_conditional_render_inverted DONE (i965, nvc0, softpipe, llvmpipe) + GL_ARB_cull_distance not started + GL_ARB_derivative_control DONE (i965, nv50, nvc0, r600) + GL_ARB_direct_state_access not started + GL_ARB_get_texture_sub_image started (Brian Paul) + GL_ARB_shader_texture_image_samples not started + GL_ARB_texture_barrier DONE (nv50, nvc0, r300, r600, radeonsi) + GL_KHR_context_flush_control not started + GL_KHR_robust_buffer_access_behavior not started + GL_KHR_robustness 90% done (the ARB variant) + +These are the extensions cherry-picked to make GLES 3.1 +GLES3.1, GLSL ES 3.1 + GL_ARB_arrays_of_arrays started (Timothy) + GL_ARB_compute_shader started (currently stalled) + GL_ARB_explicit_uniform_location DONE (all drivers that support GLSL) + GL_ARB_framebuffer_no_attachments not started + GL_ARB_program_interface_query not started + GL_ARB_shader_atomic_counters DONE (i965) + GL_ARB_shader_image_load_store in progress (curro) + GL_ARB_shader_storage_buffer_object not started + GL_ARB_separate_shader_objects DONE (all drivers) + GL_ARB_stencil_texturing DONE (i965/gen8+, nv50, nvc0, r600, radeonsi) + GL_ARB_vertex_attrib_binding DONE (all drivers) + GS5 Enhanced textureGather DONE (i965, nvc0, r600, radeonsi) + GS5 Packing/bitfield/conversion functions DONE (i965, nvc0, r600) + GL_EXT_shader_integer_mix DONE (all drivers that support GLSL) + More info about these features and the work involved can be found at http://dri.freedesktop.org/wiki/MissingFunctionality diff --git a/mesalib/docs/autoconf.html b/mesalib/docs/autoconf.html index d4e8a35d8..2ef8c63db 100644 --- a/mesalib/docs/autoconf.html +++ b/mesalib/docs/autoconf.html @@ -97,20 +97,22 @@ shared libraries in a single pass.

CC, CFLAGS, CXX, CXXFLAGS

These environment variables control the C and C++ compilers used during the build. By default, -gcc and g++ are used with the options -"-g -O2".

+gcc and g++ are used and the debug/optimisation +level is left unchanged.

LDFLAGS

An environment variable specifying flags to -pass when linking programs. These are normally empty, but can be used -to direct the linker to use libraries in nonstandard directories. For -example, LDFLAGS="-L/usr/X11R6/lib".

+pass when linking programs. These should be empty and +PKG_CONFIG_PATH is recommended to be used instead. If needed +it can be used to direct the linker to use libraries in nonstandard +directories. For example, LDFLAGS="-L/usr/X11R6/lib".

PKG_CONFIG_PATH
-

When available, the -pkg-config utility is used to search for external libraries +

The +pkg-config utility is a hard requirement for cofiguring and +building mesa. It is used to search for external libraries on the system. This environment variable is used to control the search path for pkg-config. For instance, setting PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig will search for @@ -135,14 +137,32 @@ one of these architectures is detected. This option ensures that assembly will not be used.

-
--enable-32-bit
-
--enable-64-bit
-

By default, the build will compile code as directed by the environment -variables -CC, CFLAGS, etc. If the compiler is -gcc, these options offer a helper to add the compiler flags -to force 32- or 64-bit code generation as used on the x86 and x86_64 -architectures. Note that these options are mutually exclusive.

+
--build=
+
--host=
+

By default, the build will compile code for the architecture that +it's running on. In order to build cross-compile Mesa on a x86-64 machine +that is to run on a i686, one would need to set the options to:

+ +

--build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu

+ +Note that these can vary from distribution to distribution. For more +information check with the + +autoconf manual. +Note that you will need to correctly set PKG_CONFIG_PATH as well. + + +

In some cases a single compiler is capable of handling both architectures +(multilib) in that case one would need to set the CC,CXX variables +appending the correct machine options. Seek your compiler documentation for +further information - + gcc +machine dependent options

+ +

In addition to specifying correct PKG_CONFIG_PATH for the target +architecture, the following should be sufficient to configure multilib Mesa

+ +./configure CC="gcc -m32" CXX="g++ -m32" --build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu ...
@@ -194,7 +214,9 @@ kernel DRM modules are not available.
--enable-glx-tls

Enable Thread Local Storage (TLS) in GLX. -

--with-expat=DIR
The DRI-enabled libGL uses expat to +
--with-expat=DIR +

DEPRECATED, use PKG_CONFIG_PATH instead.

+

The DRI-enabled libGL uses expat to parse the DRI configuration files in /etc/drirc and ~/.drirc. This option allows a specific expat installation to be used. For example, --with-expat=/usr/local will diff --git a/mesalib/docs/devinfo.html b/mesalib/docs/devinfo.html index a947b0d39..8d20eea3c 100644 --- a/mesalib/docs/devinfo.html +++ b/mesalib/docs/devinfo.html @@ -218,15 +218,93 @@ commit ID of the commit of interest (as it appears in the mesa master branch). The latest set of patches that have been nominated, accepted, or rejected for the upcoming stable release can always be seen on the -Mesa Stable Queue +Mesa Stable Queue page. -

Cherry-picking candidates for a stable branch

+

Criteria for accepting patches to the stable branch

-

-Please use git cherry-pick -x <commit> for cherry-picking a commit -from master to a stable branch. -

+Mesa has a designated release manager for each stable branch, and the release +manager is the only developer that should be pushing changes to these +branches. Everyone else should simply nominate patches using the mechanism +described above. + +The stable-release manager will work with the list of nominated patches, and +for each patch that meets the crtieria below will cherry-pick the patch with: +git cherry-pick -x <commit>. The -x option is +important so that the picked patch references the comit ID of the original +patch. + +The stable-release manager may at times need to force-push changes to the +stable branches, for example, to drop a previously-picked patch that was later +identified as causing a regression). These force-pushes may cause changes to +be lost from the stable branch if developers push things directly. Consider +yourself warned. + +The stable-release manager is also given broad discretion in rejecting patches +that have been nominated for the stable branch. The most basic rule is that +the stable branch is for bug fixes only, (no new features, no +regressions). Here is a non-exhaustive list of some reasons that a patch may +be rejected: + +

Making a New Mesa Release

@@ -237,64 +315,205 @@ These are the instructions for making a new Mesa release.

Get latest source files

Use git to get the latest Mesa files from the git repository, from whatever -branch is relevant. +branch is relevant. This document uses the convention X.Y.Z for the release +being created, which should be created from a branch named X.Y. +

+ +

Perform basic testing

+

+The release manager should, at the very least, test the code by compiling it, +installing it, and running the latest piglit to ensure that no piglit tests +have regressed since the previous release. +

+ +

+The release manager should do this testing with at least one hardware driver, +(say, whatever is contained in the local development machine), as well as on +both Gallium and non-Gallium software drivers. The software testing can be +performed by running piglit with the following environment-variable set: +

+ +
+LIBGL_ALWAYS_SOFTWARE=1
+
+ +And Gallium vs. non-Gallium software drivers can be obtained by using the +following configure flags on separate builds: + +
+--with-dri-drivers=swrast
+--with-gallium-drivers=swrast
+
+ +

+Note: If both options are given in one build, both swrast_dri.so drivers will +be compiled, but only one will be installed. The following command can be used +to ensure the correct driver is being tested:

+
+LIBGL_ALWAYS_SOFTWARE=1 glxinfo | grep "renderer string"
+
+ +If any regressions are found in this testing with piglit, stop here, and do +not perform a release until regressions are fixed. -

Verify and update version info in VERSION

+

Update version in file VERSION

-Create a docs/relnotes/x.y.z.html file. -The bin/bugzilla_mesa.sh and bin/shortlog_mesa.sh scripts can be used to -create the HTML-formatted lists of bugfixes and changes to include in the file. -Link the new docs/relnotes/x.y.z.html file into the main relnotes.html file. +Increment the version contained in the file VERSION at Mesa's top-level, then +commit this change.

+

Create release notes for the new release

+

-Update docs/index.html. +Create a new file docs/relnotes/X.Y.Z.html, (follow the style of the previous +release notes). Note that the sha256sums section of the release notes should +be empty at this point.

-Tag the files with the release name (in the form mesa-x.y) -with: git tag -s mesa-x.y -m "Mesa x.y Release" -Then: git push origin mesa-x.y +Two scripts are available to help generate portions of the release notes: + +

+	./bin/bugzilla_mesa.sh
+	./bin/shortlog_mesa.sh
+
+ +

+The first script identifies commits that reference bugzilla bugs and obtains +the descriptions of those bugs from bugzilla. The second script generates a +log of all commits. In both cases, HTML-formatted lists are printed to stdout +to be included in the release notes.

+

+Commit these changes +

-

Make the tarballs

+

Make the release archives, signatures, and the release tag

-Make the distribution files. From inside the Mesa directory: +From inside the Mesa directory: 

 	./autogen.sh
-	make tarballs
+	make -j1 tarballs

-After the tarballs are created, the md5 checksums for the files will -be computed. -Add them to the docs/relnotes/x.y.html file. +After the tarballs are created, the sha256 checksums for the files will +be computed and printed. These will be used in a step below.

-Copy the distribution files to a temporary directory, unpack them, -compile everything, and run some demos to be sure everything works. +It's important at this point to also verify that the constructed tar file +actually builds:

-

Update the website and announce the release

+
+	tar xjf MesaLib-X.Y.Z.tar.bz2
+	cd Mesa-X.Y.Z
+	./configure --enable-gallium-llvm
+	make -j6
+	make install
+
+

-Make a new directory for the release on annarchy.freedesktop.org with: -
- -mkdir /srv/ftp.freedesktop.org/pub/mesa/x.y - +Some touch testing should also be performed at this point, (run glxgears or +more involved OpenGL programs against the installed Mesa).

-Basically, to upload the tarball files with: -
- -rsync -avP -e ssh MesaLib-x.y.* USERNAME@annarchy.freedesktop.org:/srv/ftp.freedesktop.org/pub/mesa/x.y/ - +Create detached GPG signatures for each of the archive files created above: +

+ +
+	gpg --sign --detach MesaLib-X.Y.Z.tar.gz
+	gpg --sign --detach MesaLib-X.Y.Z.tar.bz2
+	gpg --sign --detach MesaLib-X.Y.Z.zip
+
+ +

+Tag the commit used for the build: +

+ +
+	git tag -s mesa-X.Y.X -m "Mesa X.Y.Z release"
+
+ +

+Note: It would be nice to investigate and fix the issue that causes the +tarballs target to fail with multiple build process, such as with "-j4". It +would also be nice to incorporate all of the above commands into a single +makefile target. And instead of a custom "tarballs" target, we should +incorporate things into the standard "make dist" and "make distcheck" targets. +

+ +

Add the sha256sums to the release notes

+ +

+Edit docs/relnotes/X.Y.Z.html to add the sha256sums printed as part of "make +tarballs" in the previous step. Commit this change. +

+ +

Push all commits and the tag creates above

+ +

+This is the first step that cannot easily be undone. The release is going +forward from this point: +

+ +
+	git push origin X.Y --tags
+
+ +

Install the release files and signatures on the distribution server

+ +

+The following commands can be used to copy the release archive files and +signatures to the freedesktop.org server: +

+ +
+	scp MesaLib-X.Y.Z* people.freedesktop.org:
+	ssh people.freedesktop.org
+	cd /srv/ftp.freedesktop.org/pub/mesa
+	mkdir X.Y.Z
+	cd X.Y.Z
+	mv ~/MesaLib-X.Y.Z* .
+
+ +

Back on mesa master, andd the new release notes into the tree

+ +

+Something like the following steps will do the trick: +

+ +
+	cp docs/relnotes/X.Y.Z.html /tmp
+        git checkout master
+        cp /tmp/X.Y.Z.html docs/relnotes
+        git add docs/relnotes/X.Y.Z.html
+
+ +

+Also, edit docs/relnotes.html to add a link to the new release notes, and edit +docs/index.html to add a news entry. Then commit and push: +

+ +
+	git commit -a -m "docs: Import X.Y.Z release notes, add news item."
+        git push origin
+
+ +

Update the mesa3d.org website

+ +

+NOTE: The recent release managers have not been performing this step +themselves, but leaving this to Brian Paul, (who has access to the +sourceforge.net hosting for mesa3d.org). Brian is more than willing to grant +the permission necessary to future release managers to do this step on their +own.

@@ -306,13 +525,22 @@ sftp USERNAME,mesa3d@web.sourceforge.net

+ +

Announce the release

Make an announcement on the mailing lists: mesa-dev@lists.freedesktop.org, -mesa-users@lists.freedesktop.org and mesa-announce@lists.freedesktop.org + +Follow the template of previously-sent release announcements. The following +command can be used to generate the log of changes to be included in the +release announcement: + +

+	git shortlog mesa-X.Y.Z-1..mesa-X.Y.Z
+

diff --git a/mesalib/docs/index.html b/mesalib/docs/index.html index 584bc4ec7..5fb55670e 100644 --- a/mesalib/docs/index.html +++ b/mesalib/docs/index.html @@ -16,6 +16,12 @@

News

+

August 19, 2014

+

+Mesa 10.2.6 is released. +This is a bug-fix release. +

+

August 2, 2014

Mesa 10.2.5 is released. diff --git a/mesalib/docs/relnotes.html b/mesalib/docs/relnotes.html index c7e0983a8..b84f498ca 100644 --- a/mesalib/docs/relnotes.html +++ b/mesalib/docs/relnotes.html @@ -21,6 +21,7 @@ The release notes summarize what's new or changed in each Mesa release.