Changes between Version 1 and Version 2 of DeveloperDoc

Timestamp:

Nov 17, 2006 7:00:25 PM (17 years ago)

Author:

Horst Meyerdierks

Comment:

--

DeveloperDoc

@@ -7 +7 @@
 Q: I've done that, but the user still can't check out from the repository!?
 
-A: The user has to wait until tomorrow. They can use the source browser in the wiki in the meantime. You have changed only the access to the trac environment (wiki, tickets, source browser etc.). Overnight a cron job will collect access permission information from all projects and compose a new, equivalent set of svn access permissions. So by tomorrow the svn repository should be available to the user.
+A: The user has to wait for up to one hour. They can use the source browser in the wiki in the meantime. You have changed only the access to the trac environment (wiki, tickets, source browser etc.). Once every hour a cron job will collect access permission information from all projects and compose a new, equivalent set of svn access permissions. So by within the hour, the svn repository should be available to the user.
 
 Q: !NewUser wants to be developer on our project, and we agree. How do we set that up?
@@ -13 +13 @@
 A: While you are logged onto the project as one of its developers there will be an "Admin" button, click it. Select General : Permissions on the left. At the bottom right you then have a panel "Add Subject to Group". The subject is "!NewUser" and the group is "developer". Once filled in hit the "Add" button in that panel.
 
-Q: I suppose the new developer on our project can't commit to the repository until the new permissions have been propageted overnight from the trac environment to the svn repository?
+Q: I suppose the new developer on our project can't commit to the repository until the new permissions have been propagated from the trac environment to the svn repository?
 
-A: That's correct.
+A: That's correct. Should be no longer than an hour.