Re: prominent message on website about "use only on

Quoting [email protected] (from Tue, 01 Aug 2017 10:18:03 +0200):

> On 2017-07-31 23:11, Thomas Orgis wrote:
>> Am Mon, 31 Jul 2017 17:25:03 -0300
>> schrieb Rogério Brito <[email protected]>:
>>
>>> I'm sorry if this has already been mentioned here, but this seems like
>>> an excellent opportunity to switch to git.
>>
>> An easier migration would be to subversion, though. It supports proper
>> branching and merging nowadays and the migration from CVS is very well
>> established, along with easy migration of the mind as the command set
>> is very similar.
>
> I am going to disapoint everyone, and really question the  
> benefits/efforts ratio in a migration away from CVS.
> Of course, CVS is obsolete within the versionning tools, and for  
> sure it's not hype/trendy.
> However, if the last Lame release is from 5 years ago, this is  
> clearly not because of the versionning tool, but because of the lack  
> of time/willingness to invest time in Lame.

I agree and disagree at the same time. :)

For those people which have write access to LAME already, the point is  
not the tool, it's time.
For the new kids on the block, git matters. It's the tool they know,  
it's distributed so that they first can play around in their own repo  
(not that you couldn't to something like that in CVS in some manual  
way, but they usually only know how to do it in git).

I agree with Thomas, that it doesn't has to be git (I prefer SVN), but  
on the other hand, if we switch, we should switch to git just because  
the user base of git is bigger (not based on facts, just my personal  
impression/opinion).

> My feeling is that switching tool will likely require more efforts  
> than moving current head to a branch in CVS + correcting the issues  
> reported on libmp3lame.

Well... what about first doing a summer-cleaning (fixing the issues),  
and then switching (if there is a volunteer, why not?) for the  
hope/benefit of maybe attracting new blood?

One more thing which may play a role here... we don't really have the  
release process written down, do we? And not everyone knows what needs  
to be done where with which account/password. Everyone would have to  
come up with his own way... like changing the version, updating the  
ChangeLog (I would have to check myself now how... I think I have a  
script for this) running "make distribution" (or is it "make  
distrib"?) and then... the generated tarball needs to be uploaded  
somewhere... and then I would wonder what else has to be done  
(something in the SF webinterface?).

Bye,
Alexander.

-- 
http://www.Leidinger.net [email protected]: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    [email protected]  : PGP 0x8F31830F9F2772BF
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev