<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/dev, branch openssl-3.0.0-alpha4</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=openssl-3.0.0-alpha4</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=openssl-3.0.0-alpha4'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2020-05-15T10:20:31Z</updated>
<entry>
<title>dev/release.sh: Add --reviewer to set reviewers</title>
<updated>2020-05-15T10:20:31Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2020-04-24T09:03:28Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=64af3aecaea73906325c64d3cf36c9f4e3f180a4'/>
<id>urn:sha1:64af3aecaea73906325c64d3cf36c9f4e3f180a4</id>
<content type='text'>
Doing this is kind of contrary to how we normally do things, as this
constitutes a kind of pre-approval.  However, without this, the normal
review process will modify the reviewed commits, and render the
annotated release tag invalid, which forces the person doing the
release to re-tag manually.

Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/11630)
</content>
</entry>
<entry>
<title>travis: enable markdownlint checks</title>
<updated>2020-05-08T14:22:01Z</updated>
<author>
<name>Rich Salz</name>
<email>rsalz@akamai.com</email>
</author>
<published>2020-05-07T11:42:14Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=4ef0ddc9d8ee829bf9dceae73f7a48a55f512739'/>
<id>urn:sha1:4ef0ddc9d8ee829bf9dceae73f7a48a55f512739</id>
<content type='text'>
Reviewed-by: Tomas Mraz &lt;tmraz@fedoraproject.org&gt;
Reviewed-by: Matthias St. Pierre &lt;Matthias.St.Pierre@ncp-e.com&gt;
(Merged from https://github.com/openssl/openssl/pull/11739)
</content>
</entry>
<entry>
<title>Fix dev/release-aux-openssl-announce-pre-release.tmpl</title>
<updated>2020-04-25T02:02:10Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2020-04-23T14:38:40Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=8d6fc5f4d29522a9ca67c122496aef518497f191'/>
<id>urn:sha1:8d6fc5f4d29522a9ca67c122496aef518497f191</id>
<content type='text'>
$LABEL -&gt; $label

Removed link to release notes, as we don't produce them for master.

Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/11617)
</content>
</entry>
<entry>
<title>Mention the 3.0 wiki page in the release announcement emails</title>
<updated>2020-04-23T10:28:37Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2020-04-21T14:13:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=486d8973bf2726e3d24438006fd2449bdab24e9e'/>
<id>urn:sha1:486d8973bf2726e3d24438006fd2449bdab24e9e</id>
<content type='text'>
Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
(Merged from https://github.com/openssl/openssl/pull/11593)
</content>
</entry>
<entry>
<title>Developer scripts: Release script</title>
<updated>2020-04-21T08:11:41Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2020-04-06T21:58:24Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=b0b0b6a41dd4418bab19cdd28c01ce248fee6af7'/>
<id>urn:sha1:b0b0b6a41dd4418bab19cdd28c01ce248fee6af7</id>
<content type='text'>
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 &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/11516)
</content>
</entry>
</feed>
