On Tue, 2016-05-03 at 13:26 +0200, Kevin Sapper wrote: > I'm currently experimenting with travis automated github releases and > finally gotten to the point where things add up. > > I could try to set this up for libzmq but I need to know how to build the > release tarballs, checksums, changelog, debs, rpms, etc. Then I can make > travis upload those artifacts to github releases and even override the > github generated tarballs.
The release tarball can be built with "make dist". I don't think we should start releasing debs/rpms. Remember that debs/rpms are binary releases, which means they MUST be built in the same environment (libc, etc) as where they are targeted for installation. This means you can't have one rpm and one deb, you must have one for each version of each distribution you want to support. It's a pain, and it's the wrong way to do it. The right way is to make things easy for the distro maintainers and work with them, so that the libraries get packaged and distributed from the repositories by the maintainers. If someone wants to build and install locally a newer version that it's available in a distro, make install of the source tarball to /usr/local tree is safer IMHO. > 2016-05-03 12:37 GMT+02:00 Pieter Hintjens <p...@imatix.com>: > > > The ztools/zmqapi tool generates the 4.2 docs from libzmq master (see > > apiall script below). The generation tool checks out specific > > repos/tags for each release, so you can easily set it to generate > > 4.2.0 from a tagged release. > > > > Relevant piece from apiall: > > > > # Directory Tag Category > > $TOOLDIR/apione ../../zeromq3-x master 3-2 > > $TOOLDIR/apione ../../zeromq4-x master 4-0 > > $TOOLDIR/apione ../../zeromq4-1 master 4-1 > > $TOOLDIR/apione ../../libzmq master 4-2 > > > > On Tue, May 3, 2016 at 10:52 AM, Doron Somech <somdo...@gmail.com> wrote: > > > Question about the API documentation, now at api.zeromq.org we have > > docs for > > > each version coming from the stable branches. > > > > > > Should we still have docs for v4.2 separate from master docs? if so where > > > the v4.2 docs are coming from? > > > > > > We can drop the docs per separate versions as we now only have master. > > > > > > > > > > > > On Tue, May 3, 2016 at 11:39 AM, Pieter Hintjens <p...@imatix.com> wrote: > > >> > > >> Hi all, > > >> > > >> I'm just throwing some ideas on the table. We have a good package of > > >> work on master and it's probably time to make a 4.2 release. > > >> > > >> Luca has already back-ported the enable/disable draft design from > > >> zproject (CZMQ et al). Yay! So we can now release stable master > > >> safely, while continuing to refine and extend the draft API sections. > > >> > > >> I propose: > > >> > > >> - to end with the stable fork policy; this was needed years ago when > > >> we had massively unstable masters. It's no longer a problem. > > >> - to use the github release function for libzmq releases and deprecate > > >> the separate delivery of tarballs. > > >> - we aim to make a 4.2.0 rc asap, then fix any issues we get, with > > >> patch releases as usual. > > >> - we backport the release function to older maintained releases (4.1, > > >> 3.2) so that their tarballs are provided by github instead of > > >> downloads.zeromq.org. > > >> > > >> Problems: > > >> > > >> - this will break a few things that depend on downloads.zeromq.org. To > > >> be fixed as we go. > > >> - github tarballs are not identical to source tarballs, particularly > > >> they lack `configure`. I propose changing our autotools build > > >> instructions so they always start with `./autogen,sh` no matter where > > >> the sources come from. > > >> > > >> I think this will work and also let us gracefully deprecate/switch off > > >> the downloads box. > > >> > > >> -Pieter > > >> _______________________________________________ > > >> zeromq-dev mailing list > > >> email@example.com > > >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > > > > > > > > > _______________________________________________ > > > zeromq-dev mailing list > > > firstname.lastname@example.org > > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > _______________________________________________ > > zeromq-dev mailing list > > email@example.com > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > _______________________________________________ > zeromq-dev mailing list > firstname.lastname@example.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Description: This is a digitally signed message part
_______________________________________________ zeromq-dev mailing list email@example.com http://lists.zeromq.org/mailman/listinfo/zeromq-dev