<html><head></head><body>I think Paul meant that the "official" release would be the act of tagging the repo with the new version, not any random change.<br><br><div class="gmail_quote">On November 4, 2016 1:43:26 PM EDT, Brian Inglis <Brian.Inglis@SystematicSw.ab.ca> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 2016-11-03 16:08, Paul Eggert wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> On 11/02/2016 09:57 AM, Deborah Goldsmith wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> I know it’s checked into the informal GitHub repository. That<br /> doesn’t work for everyone.<br /></blockquote> Now that we have an official release with the Tonga changes, your<br /> developers should be OK to run with it.<br /> Why doesn't the GitHub development repository work for them? Are<br /> there technical problems with using Git or GitHib? Or is this more a<br /> case of not using the data until it's "blessed" somehow? Either way,<br /> there should be some way to address the problem other than by having<br /> your folks wait impatiently for tarballs to show up at <a href="http://iana.org">iana.org</a>.<br /></blockquote><br />With processes checking if a new release has been packaged or announced<br />and sources have been updated and tagged, kicking off the download,<br />build, test, package, release, announce cycle, you need a reliable flag<br />or flags to kick off the process, which could be one, more, or all of<br />the above checks.<br />Triggering on just any change in the remote GitHub repo, which does see<br />a fair amount of churn many months, may not be acceptable, where it may<br />be with projects in local repos using Continuous Integration processes.<br /><br />Changing one of these production processes in any org is not likely to<br />be a lightweight undertaking, and involve spending budget on process<br />changedevelopment and testing, where it may be considered better spent<br />on more pressing significant current problems.<br /><br />Personally, a cron job checks daily if IANA ...latest symlinks contain<br />a version differing from the last download, then downloads, archives,<br />diffs, builds, compares, installs, and emails a file:// link to the log,<br />to let me know something (attempted to be) changed.<br /></pre></blockquote></div></body></html>