mirror of
https://github.com/openssl/openssl.git
synced 2024-11-21 01:15:20 +08:00
b0b0b6a41d
The old release script that exists in another repository has aged, and risks becoming messy beyond maintainability if it's made to deal with multiple OpenSSL version schemes. A solution, which has been seen in other projects, is to have the release script as part of the versioned source tree, and ensure it's adapted for the ongoing version scheme in that source tree. This introduces dev/, a directory of OpenSSL developer "stuff". We may expand it with other practical scripts to easy development setup and other similar things that developers may need. For now, it's the release script dev/release.sh, with auxilliary files in dev/release-aux/. The script is self describing, the manual is available by running the command `./dev/release.sh --manual`. The dev/ directory shall never appear in a source distribution. Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/11516)
17 lines
511 B
Perl
17 lines
511 B
Perl
#! /usr/bin/env perl -p
|
|
|
|
BEGIN {
|
|
our $count = 1; # Only the first one
|
|
our $RELEASE = $ENV{RELEASE};
|
|
our $RELEASE_TEXT = $ENV{RELEASE_TEXT};
|
|
our $RELEASE_DATE = $ENV{RELEASE_DATE};
|
|
|
|
$RELEASE_DATE = 'in pre-release'
|
|
if ($RELEASE =~ /\d+\.\d+\.\d+-(?:alpha|beta)/)
|
|
}
|
|
|
|
if (/^### Major changes between OpenSSL (\S+) and OpenSSL (\S+) \[under development\]/
|
|
&& $count-- > 0) {
|
|
$_ = "### Major changes between OpenSSL $1 and OpenSSL $RELEASE_TEXT [$RELEASE_DATE]$'";
|
|
}
|