All,
Just a quick reminder that the Trinity source repositories (but not the packaging repository) remain FROZEN at this time while I complete the SVN to GIT move and get all of the support systems up and running again. All new account requests should sent AFTER the repositories have been thawed.
Also, please remember to remove the nightly build repository lines from your /etc/apt/sources.list file. Within the next few days the contents of that repository will become highly unstable and in all likelihood uninstallable as well.
Now is the time when all developers should be combing through the bug tracker and fixing bugs, uploading their patches to the bug report as attachments.
Tim
2011/11/7 Timothy Pearson kb9vqf@pearsoncomputing.net:
All,
Just a quick reminder that the Trinity source repositories (but not the packaging repository) remain FROZEN at this time while I complete the SVN to GIT move and get all of the support systems up and running again. All new account requests should sent AFTER the repositories have been thawed.
Also, please remember to remove the nightly build repository lines from your /etc/apt/sources.list file. Within the next few days the contents of that repository will become highly unstable and in all likelihood uninstallable as well.
Now is the time when all developers should be combing through the bug tracker and fixing bugs, uploading their patches to the bug report as attachments.
Tim
Do You plan on keeping the frozen code in the SVN and updating it on next froze, or You host source tarballs somewhere? It seems like a good idea to keep the stable code in the svn to me.
2011/11/7 Timothy Pearson kb9vqf@pearsoncomputing.net:
All,
Just a quick reminder that the Trinity source repositories (but not the packaging repository) remain FROZEN at this time while I complete the SVN to GIT move and get all of the support systems up and running again. All new account requests should sent AFTER the repositories have been thawed.
Also, please remember to remove the nightly build repository lines from your /etc/apt/sources.list file. Within the next few days the contents of that repository will become highly unstable and in all likelihood uninstallable as well.
Now is the time when all developers should be combing through the bug tracker and fixing bugs, uploading their patches to the bug report as attachments.
Tim
Do You plan on keeping the frozen code in the SVN and updating it on next froze, or You host source tarballs somewhere? It seems like a good idea to keep the stable code in the svn to me.
I did keep the 3.5.13 code in SVN, however as the KDE project is (AFAIK) trying to get rid of its SVN server I don't know how feasible keeping the stable code in SVN is going to be.
Tim
On Sun, Nov 6, 2011 at 19:24, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
I did keep the 3.5.13 code in SVN, however as the KDE project is (AFAIK) trying to get rid of its SVN server I don't know how feasible keeping the stable code in SVN is going to be.
Tim
After the import, you should tag the last commit each of the repositories as 3.5.13. This way, Git knows that it's a release, and it'll separate that from the rest.
(And if gitweb likes to be tag-happy, it might generate tarballs...)
In article 2570a0110de40f405eb18ee935957a12.squirrel@vali.starlink.edu, Timothy Pearson trinity-devel@lists.pearsoncomputing.net wrote:
I did keep the 3.5.13 code in SVN, however as the KDE project is (AFAIK) trying to get rid of its SVN server I don't know how feasible keeping the stable code in SVN is going to be.
Whilst you're beating the git repo into shape, I updated from svn. I found that changing the code's root directory in svn to 3.5.13_frozen has meant that the svn:externals are now wrong. The paths should be changed from branches/trinity/* to branches/trinity/3.5.13_frozen/* Is it worth doing a quick fix there if the repo will stay around ?
Nick
-
L0ner sh4dou -
Nick Leverton -
Robert Xu -
Timothy Pearson