On 07/28/2017 06:33 AM, Matt Darfeuille wrote: > On 7/27/2017 10:18 PM, Tom Eastep wrote: >> On 07/27/2017 01:11 PM, Matt Darfeuille wrote: >>> Tom, >>> >>> Not sure if it's done on purpose but the tag 5.1.5.1 is not pushed for >>> the trunk (code) repo! :) >>> >>> I built 5.1.5.1 using the 5.1.5 branch though!!! >>> >> >> Pushed. >> >> Thanks! >> > > Tag 5.1.5.1 seems to be an lightweight tag! :) > One way, and probably the safest would be to push a new tag with > something like "5.1.5.1V1". > > I could modified the build script accordingly assuming you agree on the > naming for tag correction?
I think that the current tag convention is okay -- x.x.x-base, then x.x.x.i for the point releases. I've thought about creating a 'release' script that would: - Verify that both the code and release repository paths are clean (no uncommitted changes). - Tag (signed) both paths. - Invoke the existing 'upload' script. I suppose that could also be implemented as a -R option to the 'build' script, or as an enhancement to the 'upload' script. The former is probably easier, since it already has the logic to figure out the path corresponding to a particular release. Thanks, -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Shorewall-devel mailing list Shorewall-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-devel
