[Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

[Tom Russo]

On Thu, Feb 08, 2018 at 04:00:22PM +0000, we recorded a bogon-computron collision of the <xastir at dbrooke.me.uk> flavor, containing:
> On Wed, Feb 07, 2018 at 11:52:48AM -0700, Tom Russo wrote:
> > 
> > If you're a package maintainer for any OS, you might start looking into how
> > you have to change your package build process to access the Github release
> > tarballs instead of SourceForge.
> 
> I've made the necessary changes for CRUX.
> 
> https://github.com/dbrooke/crux-ports/commit/c8c7b1563752298c432199723dd2a82b8f8d5793

Thank you for testing out the new release process on this old release!

> > If you have heartache with how I've done this 2.0.8 recreation and would hate
> > to see it perpetuate into all future releases, please let me know so I can
> > rethink the procedure.  But I think this is a pretty close simulation of how
> > release tarballs on sourceforge were, and should be an easy way for folks to
> > grab stable releases without using git.
> 
> It seems OK for me and thanks for taking care to include the project
> name in the tarball as without that a common download cache directory
> fails to work due to name conflicts.

Yes, I was worried about that, and by default Github doesn't prepend the 
project name to the tag name when creating the tarball file --- but *DOES*
prepend the project name for the directory INSIDE the tarball.  I was concerned
about *exactly* the issue you note here.

> Looking forward to the new release, hopefully I'll only need to bump the
> version and set the package release back to 1 for that to work.

Unless there is a major backlash in the next couple of days against the 
tagging scheme I've come up with, that should be the only difference from 
release to release.

I was up late cleaning up documentation and wiki pages in preparation for
this release.  I'm thinking I'll do the release on Saturday, which is the
first day I'll have free to do the necessary steps.

If there is anyone who would like to take on tasks of wiki clean-up (it's
pretty stale) and documentation proofreading, please jump on board.  Otherwise
this release will just have whatever documentation fixes I can find the time
to make myself (and that others have already taken the time to do, like the
Cygwin updates and platform-specific HowTos on the wiki).

-- 
Tom Russo    KM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]