summaryrefslogtreecommitdiff
path: root/RELEASING
AgeCommit message (Collapse)AuthorFilesLines
2016-07-24Simplify the RELEASING steps based on current release.sh.Eric Anholt1-20/+6
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>
2015-03-20RELEASING: Fix annouce typoDamien Lespiau1-1/+1
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-20RELEASING: Fix the step numberingDamien Lespiau1-6/+6
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-20RELEASING: Fix releasing instructions to match the latest release.shDamien Lespiau1-10/+9
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>
2009-12-03Add RELEASING to document the release processKristian Høgsberg1-0/+66