<div dir="ltr"><div>I know of nothing to hinder us.</div><div><br></div><div>1) Yes, that PR is ready to go</div><div>2) I just added a second PR to move us to using the pre-built Fedora MinGW-Biblesync package</div><div><br></div><div>Making a release, after the PR is in, from your local system is:</div><div># Only if you're not on the HEAD of master locally<br></div><div>git co master</div><div>git pull</div><div># actual release</div><div>git tag 4.2.0</div><div>git push origin 4.2.0</div><div><br></div><div>After the build is done, if you want to go in and edit release notes, etc, you're welcome to do that. But the automation will build *.exe, *.rpm, *.deb, *.tar.{gz,xz}, create the release, and add all those to the release commit. After that, you can add release information if you'd like.</div><div><br></div><div>--Greg<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 1, 2020 at 7:51 AM Karl Kleinpaste <<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<font face="FreeSerif">Is there anything to stop us from letting
4.2.0 out the door this weekend?</font><font face="FreeSerif"><font face="FreeSerif"><br>
I need to update a new top section in RELEASE-NOTES, of course.<br>
</font>Greg, is that PR ready to go?<br>
<br>
What exactly is involved now in "making a release," from the
standpoint of all the new automated tag and build processes?
Previously (waf etc), I would edit a version stamp into several
files, the commit of that would become the released version, and
I'd include tarball and Windows *.exe in the releases page. Now,
I'm thinking that we mostly tag the relevant commit and let some
of the new automated machinery do its thing. Details, please, for
the sake of all concerned.<br>
</font>
</div>
_______________________________________________<br>
xiphos-devel mailing list<br>
<a href="mailto:xiphos-devel@crosswire.org" target="_blank">xiphos-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/xiphos-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/xiphos-devel</a><br>
</blockquote></div>