[xiphos-devel] release this weekend?

[Greg Hellings]

I know of nothing to hinder us.

1) Yes, that PR is ready to go
2) I just added a second PR to move us to using the pre-built Fedora
MinGW-Biblesync package

Making a release, after the PR is in, from your local system is:
# Only if you're not on the HEAD of master locally
git co master
git pull
# actual release
git tag 4.2.0
git push origin 4.2.0

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.

--Greg

On Fri, May 1, 2020 at 7:51 AM Karl Kleinpaste <karl at kleinpaste.org> wrote:

> Is there anything to stop us from letting 4.2.0 out the door this weekend?
> I need to update a new top section in RELEASE-NOTES, of course.
> Greg, is that PR ready to go?
>
> 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.
> _______________________________________________
> xiphos-devel mailing list
> xiphos-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/xiphos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/xiphos-devel/attachments/20200501/9278c990/attachment.html>