Commit Graph

6 Commits (9d07fbf5939011f7fdf6329689ef9dcc1c6648ff)

Author SHA1 Message Date
Marek Olšák e87a87925e RELEASING: mention meson 2018-02-17 20:25:02 +01:00
Eric Anholt f19cd3a528 Simplify the RELEASING steps based on current release.sh.
Since release.sh creates and pushes a libdrm-$VERSION tag for us,
there's no need to also have the user manually generating a $VERSION
tag as well.

I also dropped the "optional" part of distcheck.  You shouldn't have
pushed master with a version bump that hasn't passed distcheck.

Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
2016-07-24 18:36:34 -07:00
Damien Lespiau e2acca4e40 RELEASING: Fix annouce typo
That's the only typo :set spell found.

v2: Fix typo in commit message (Ilia Mirkin)

Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2015-03-20 15:55:23 +00:00
Damien Lespiau 992940ca64 RELEASING: Fix the step numbering
v2: Really fix the numbering (Emil Velikov)

Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2015-03-20 15:55:23 +00:00
Damien Lespiau 8f245b777b RELEASING: Fix releasing instructions to match the latest release.sh
It seems that the tests don't need DRM master anymore? at least make
distcheck passes when X is running.

release.sh is also invoked with just the path to the libdrm git checkout
and we don't want to pass additional arguments that will be treated as
additional modules we want to release.

Also, make a note that release.sh will run make distcheck for you, so we
don't strickly need to run it beforehand.

Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2015-03-20 15:53:57 +00:00
Kristian Høgsberg be957cc219 Add RELEASING to document the release process 2009-12-03 17:50:37 -05:00