On Tue, Jun 20, 2017 at 6:16 AM Daniel Gruno <[email protected]> wrote:
> On 06/20/2017 12:11 PM, John D. Ament wrote: > > On Mon, Jun 19, 2017 at 5:19 PM Daniel Gruno <[email protected]> > wrote: > > > >> On 06/19/2017 08:32 PM, John D. Ament wrote: > >>> I was searching around for information and wanted to get some simple > >>> examples together. How are the releases for Pony Mail created (tar + > >>> signatures)? > >>> > >>> John > >>> > >> > >> Spotty Internet today, but here goes. > >> > >> Pony Mail is designed to just run out of the box with the code in the > >> repo, no compiling should be required. Furthermore, master is, ideally, > >> always releasable code (there may be times when this isn't true, let's > >> work on that when we have enough people-power), so with that in mind: > >> > >> - Create a a.b branch (0.10, 0.11 etc) from master > >> - tarball it all, it's all read-to-run code > >> - put the tarball somewhere (add checksum file etc) > >> > > > > This is the part I'm missing. What command(s) are you using to generate > > the checksums? > > $checktool tarball.tar.gz > tarball.tar.gz.(md5|sha1|sha256|asc), > where $checktool is: > > for md5: md5sum > for sha1: sha1sum > for sha256: sha256sum > > For the .asc file, I believe I used Kleopatra last time to sign the > tarball. > > Hmmm so if I'm using gpg --encrypt would I just use my own email as the recipient of the file? > I'll set up a page on the web site with the instruction when time allows. > Basically, I'm trying to come up with an ELI5 guide for the incubator website on how to create a source release. > > With regards, > Daniel. > > > > > > >> - hold a vote on the tarball - the git branch will help with provenance > >> - when vote finished, push to dist/release > >> - profit > >> > >> With regards, > >> Daniel. > >> > > > >
