GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » General » Rearrangement of repository
Rearrangement of repository [message #7077] Fri, 18 July 2008 13:16 Go to next message
Mohammad Al-Turany is currently offline  Mohammad Al-Turany
Messages: 518
Registered: April 2004
Location: GSI, Germany
first-grade participant
From: *gsi.de
Hi all,
The SVN repository will be rearranged today, to avoid
inconsistencies occuring during the transformation process, the read and
write access to the repository will be blocked from today 16 am CEST.

The work should be finished by Monday afternoon (21 July). You will be informed
once the repository will be available again.

The new SVN will looks like:

Fairroot/pandaroot/trunk
Fairroot/pandaroot/release
Fairroot/pandaroot/stable
Fairroot/pandaroot/development


The permissions for all will stay the same, based on the directory structure of the packages for the trunk, stable and release will have different permissions, and the development is read/write for every body, so every developer can make his own branch there and then merge it (or synchronize it) with the trunk and even remove it when he finished (if he likes!).

To check out the trunk (Head) one has to do:

svn co https//subversion.gsi.de/fairroot/pandaroot/trunk

Be careful if you call "svn co https//subversion.gsi.de/fairroot/pandaroot " you will check out every thing!! Which will take time!


Re: Rearrangement of repository [message #7083 is a reply to message #7077] Mon, 21 July 2008 11:32 Go to previous messageGo to next message
Mohammad Al-Turany is currently offline  Mohammad Al-Turany
Messages: 518
Registered: April 2004
Location: GSI, Germany
first-grade participant
From: *gsi.de
Hi everybody,

The rearrangement of the SVN repository is finished! You can see the new structure on:

https://subversion.gsi.de/trac/fairroot/browser/pandaroot

Please type the following line in your working directory before you try to update or commit anything to the svn (do not forget the space and dot at the end of the line ):

Quote:

svn switch https://subversion.gsi.de/fairroot/pandaroot/trunk .


With this you switch your repository to the new structure and then you can work on the trunk as before! So there is no need to checkout everything from scratch!

The Releases are also moved so if you need to checkout a release (e.g. ju08) you have to do:

svn co https://subversion.gsi.de/fairroot/pandaroot/release/jun08

If you have already a release and you want to update (bug corrections) or you have permissions to correct a release you have also to switch the repository:

svn switch https://subversion.gsi.de/fairroot/pandaroot/release/jun08 .


Be careful if you call "svn co https//subversion.gsi.de/fairroot/pandaroot " you will check out every thing!! Which will take time!

there is also a new branch pandaroot/development which is accessible for everybody, so you can create your own directory there, copy the trunk to this directory do what you want to do merge it back to trunk and then you can delete it or keep it!


Best regards

Mohammad

Re: Rearrangement of repository [message #7088 is a reply to message #7083] Mon, 21 July 2008 19:09 Go to previous messageGo to next message
Aida Galoyan is currently offline  Aida Galoyan
Messages: 79
Registered: May 2007
Location: Dubna
continuous participant
From: *jinr.ru
Hi Mohammad,

what is a difference between pandaroot versions:

https://subversion.gsi.de/fairroot/pandaroot/trunk
and
https://subversion.gsi.de/fairroot/pandaroot/stable

Best regards,
Aida

Re: Rearrangement of repository [message #7089 is a reply to message #7088] Mon, 21 July 2008 19:32 Go to previous message
Mohammad Al-Turany is currently offline  Mohammad Al-Turany
Messages: 518
Registered: April 2004
Location: GSI, Germany
first-grade participant
From: *dip.t-dialin.net
Hi Aida,

For now I just copy the head to trunk and stable, we discuss that sometime ago in the software meeting and the results can be summarized as following:

development is for your development just to keep track of what you do, it will not go through any tests or nightly build, usually people who plan big changes in the software copy the trunk there and works on it, and at some point they copy it back to the trunk.

For small changes one can work directly on the trunk, the trunk should at least compile, it will also be build nightly and the rule checker will also run on the trunk! and when you think it is now stable you copy it to the stable branch, where it should compile and run the test macros successfully!

People who only need to run some simulations or analysis and do not develop code should take either a release or the stable branch which could have new features that is still not in the last release!

regards

Mohammad
Previous Topic: Length of track
Next Topic: New classes for event display
Goto Forum:
  


Current Time: Sat Jun 29 18:06:48 CEST 2024

Total time taken to generate the page: 0.01181 seconds