I realized that tags were a good thing and have been reading about them. Thanks for confirming and suggesting the right way to use them. I'll use them for the next round.
On Fri, May 27, 2016 at 5:40 PM, <[email protected]> wrote: > Eric Iverson <[email protected]> wrote: > > > > This release is beta-4. > > Important: please add tags to these little mile stones. Simply > > git tag j805-beta-4 > > when you are going to do the beta build, or right after you've done it. > > There are options for adding commentary or digitally signing > a release but you can ignore all that. Make a simple tag and > be done. > > Pick any naming scheme you want but then try to be consistent. > Don't use special or space characters in tags. > > > > See http://www.jsoftware.com/download/jengine for more details, > > I already find decent markers there. (Having both an "804 initial > release" and an "804 release" is confusing but not deadly.) > > Please apply corresponding tags to respective commits in the tree, > using commit ids to refer to the old versions you used: > > git tag j805-beta-3 4975251 > > > > Changes are documented only by their branch name, but details can be > easily > > found by searching this forum. > > No need to. With tags, things get much simpler: > > # What happend since beta3? > git log j805-beta-3.. > > # What happened between beta3 and 4? > git diff j805-beta-3..j805-beta-4 > > And when we get a bug report ("I'm using 805 beta-3, and 6 is 9!"), > we could > > git checkout j805-beta-3 > > and start debugging, without figuring out "4975251". Tags are vital. > > > > If interested please install and play with these builds. Problems are > much > > better found now than later. > > I suggest to announce any binary beta kits to your "beta" forum. > That's what subscribers there are just waiting for. (I hasn't seen > any traffic since Jan 1.) > > Over here in this source forum, you can expect us developers to compile > our own binaries, related to announced beta releases, too, and help > hunting down bugs. > > But in order to sync to one of your betas, we need one thing: > > A tag. > > Martin > > PS: again, the unbox fellows are doing things right: > > unbox 636 > git tag -l > v0 > v0.1 > v0.1-rc1 > v0.2-rc1 > > unbox 637 > git shortlog v0.1-rc1..v0.1 > Thomas Costigliola (4): > Update contributing section in README > Update build scripts for new config > Remove stray file > Merge remote-tracking branch 'github/release' into release > > > unbox 638 > git show v0.1-rc1 > tag v0.1-rc1 > Tagger: Thomas Costigliola <[email protected]> > Date: Wed Jan 20 12:41:06 2016 -0500 > > 1st release candidate for v0.1 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAABAgAGBQJWn8bvAAoJELLI4Og1RrRGcXMIALFPsq4vYtrJur+wg8qp+emC > AuUIMKnyE2FwTDpr/O0cVlccjPZxx7n2/Hgu6LV9Wl8/UjQImYnUtnXIvvT/iJY7 > 2/JDNu/oGO71elnEAJuTmbbK40QNtQF9eNqQql0xMWmCfy3P5OOGfvciBhmMRoCg > zKvjz5xui2FT/Sc+LlJvBLuzMKkB24iXmd/hlwaIzOeCDbhDBEKxtZQ+PpEPhKrC > mbAR03ZPJtxM67l9siRwe0qmD1NwlB/lkfCzae2YKtiVQbPz/VWMyVi5vxkXf7Di > vi1K/pUpWRJyv4O8njhdmlfNiE1S76NI/gePU7K1Hg8eylzPa0ymf9IZ8Wh3wA8= > =z3pB > -----END PGP SIGNATURE----- > > commit 9986a050cbaf16e58b54a0586aa5e79f32d8dff3 > Merge: d2f7b6b f3d5678 > Author: Thomas Costigliola <[email protected]> > Date: Wed Jan 20 12:24:32 2016 -0500 > > Merge pull request #9 from hoosierEE/develop > > Compile on OSX, closes #8 > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
