Hello all, Last year the discussion was started to move to git. We have decided to continue with this process.
Actions involved: Create a valid authors file so all current and previous commiters on gtk-gnutella's source code are listed correctly. I will send a separate mail containing all the svn usernames we have now so that each person can indicate how he wants to be listed as an author in git. Place the migrated git sources online for you to check to see if anything did go wrong. Prepare 0.97.1 to handle new (extended) version numbers. In SVN we use the revision number in SVN releases to detect if there is a new SVN version. This is a functionality we want to keep. When we switch to git we will still use the 0.97-revnumber like scheme, however it will be in the format of 0.97.1-number-gsha1abbr. Move our sourcecode to github. Those who have worked with git knows one of its strengths is the ease of branching and forking. With github the forking and remerging progress is made very easy. Hopefully this will also attract more people to contribute due to the easy access to the code. Other project related stuff (the mailing lists, releases and our homepage) will all remain on sourceforge so nothing will change there. Status: Update authors file: In progress Request github project account: Done Prepare for new extended version numbering: Pending Discussions? - Jeroen ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
