Re: License change for non-free files in fasta3
On Tue, Feb 11, 2020 at 01:14:36PM +0000, Pearson, William R (wrp) wrote:
> Andress --
>
> I'm glad to hear that you will be able to incorporate the latest complete FASTA package into Debian.
>
> I would like to make it easier for Debian (and Anaconda/Bioconda) to track changes in FASTA, so I would like to understand these comments more clearly:
>
> I verified the previous download we have packaged for Debian from your
> server[2] with what I've found there now. There are several other
> changes (like Python3 fixes or so). IMHO its not a good idea to hide
> these changes from other users (than we as Debian) by simply keeping the
> very same version number on your server.
>
> What do you mean by "hide these changes".
I mean a random visitor of your web page will not realise that there is
some new code since there is no version bump. Providing a download file
with different content but same name is a bit unfortunate.
> What can I do (in addition to changing version number) to make the changes more visible.
That's actually my major concern.
> Is the problem that I updated v36.3.8 but not master?
Without any note I would usually clone the default branch which is
master and there was no code change. I was simply *seeking* since due
to your mail I was aware that there is some change I was looking for.
> > That's why I would recommend choosing a new version number. Moreover
> > please use tags at Github which would enable us way more comfortably
> > downloading the latest source.
>
> Again, what would these tags look like? Could you point me to a package on GitHub that does a better job of providing the information you need?
May be I'm not the best person to give advide here since I personally do
not publish software at Github. But these links are looking like what
you are seeking for:
https://help.github.com/en/github/administering-a-repository/creating-releases
https://help.github.com/en/github/administering-a-repository/about-releases
> > You could even add your release notes
> > the according tags and stop maintaining your additional server since all
> > this could be provided by Github and would safe you some manual work
> > (provided you tag also your historic releases).
>
> Thanks,
You are perfectly welcome. I hope my hints were sufficiently
helpful.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: