Re: Switching from CVS to XXX

Hello Alexander.
Looking good! I just did a RW checkout and a quick commit, and worked without trouble.
(by God, SVN is so much better than CVS!)
> I think that's it for today. The only open point I have left on my  
> list is: "are we happy and switch to the SVN repo (and update the  
> website from SVN)?".

I'm all for it! Thank you for your work
Regards; -- 
Roberto José de AmorimMSc in Computer Science
Columbia University - New York



      De: Alexander Leidinger <[email protected]>
 Para: [email protected] 
 Enviadas: Sábado, 14 de Outubro de 2017 11:43
 Assunto: Re: [Lame-dev] Switching from CVS to XXX
   
Quoting Alexander Leidinger <[email protected]> (from Sat, 14  
Oct 2017 15:45:57 +0200):

> Outstandings:
>  - validate content (e.g. checkout, build lame, check if pictures  
> are pictures, mp3 is mp3, ...)

I compared the testcase.mp3 and wav to a checked out CVS tree, they  
are byte-identical.
I have re-build lame 3.100 from SVN, it produces the same testcase.mp3.

>  - switch webpages to point to SVN instead of CVS (in progress in  
> the SVN version of the webpages)

Done in SVN, no update on the live-webpage yet. Would be nice to get  
some "svn works for me" from someone else (either RO by some  
non-project-members, or a read-write checkout from a project member)  
before updating the webpage.

>  - if happy make SVN the new master (change SF navbar to not show  
> CVS anymore and remove "not ready" from SVN part)

The old CVS is still there but as "Code (old CVS)", the SVN version is  
visible as "Code (SVN)". We can either keep the CVS version, or delete  
it (later). I have no strong opinion about this.

>  - add some procedures (how to make release from svn, how to update  
> webpages from svn)

https://sourceforge.net/p/lame/svn/HEAD/tree/trunk/process/README_SVN_USE.txt
and other files in trunk/process/.
Feel free to improve them or provide suggestions.

I have updated references to CVS in the lame source too, and switched  
the ChangeLog generator to a tool which uses svn directly  
(http://arthurdejong.org/svn2cl/).

I think that's it for today. The only open point I have left on my  
list is: "are we happy and switch to the SVN repo (and update the  
website from SVN)?".

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


   
------------------------------------------------------------------------------
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