On Wed, Mar 07, 2018 at 06:07:30PM +0100, Geert Stappers wrote: > On Sun, Mar 04, 2018 at 12:31:09PM +0100, Kolja Waschk wrote: > > On Fri, Mar 02, 2018 at 03:04:17PM +0100, Geert Stappers wrote: > > >If there are already some notes on doing a release, > > >then please tell the mailinglist(archive) about it. > > > > Hi, > > > > work to do that already kept me from "simply releasing" a few times > > because it takes a bit of time and diligence: > > > > urjtag/ > > > > - update ChangeLog, NEWS and THANKS > > - update doc/UrJTAG.txt and README > > - update version in configure.ac > > > > Those files are updated. > Available in git@SF and tagged URJTAG_2017_10pre1 > > It is in preparation for releasing 2017.10 > That version number is date related. > In october 2017 was the latest code change (DirtyJTAG cable) > > > Creating a tarball with `make dist-xz` fails.
Fixed with putting the exact version number also in NEWS. > If you have patches, tell the mailinglist. > That is nothing new. > > New are > https://gitlab.com/stappersg/urjtag > https://github.com/stappersg/urjtag > Yes, they can be used for getting changes in urjtag. > It seems (to me) that I'm not allowed to upload files to SourceForge urjtag project. Please extent my SF urjtag privileges. Groeten Geert Stappers P.S. sourceforge git server had/has intermitted problems on march 8th -- Leven en laten leven ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
