Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.currently the recommended way for redesign implementers to work on the drupalorg module is very convoluted:
1) checkout a redesign_module_sandbox/stagingX from SVN, this is where implementers check in their code to test it on the staging servers.
2) grab the latest version of drupalorg module from CVS-head.
3) checkin drupalorg module into redesign_module_sandbox/stagingX/patched/
4) start doing your modifications, check them into SVN, test results on the staging server
5) ocasionally pull from cvs head to get latest code, and check it into svn
6) once you're satisfied with your modifications, create a patch (step 5 is required before creating a patch to make sure you really have the latest gratest and are patching against HEAD)
Step 2 is the fatal flaw... it causes developer to have to start syncing with CVS and pushing to svn to stay up-to-date.
This makes little sense to require the developers to pull from CVS and commit to their svn sandbox when cvs and svn are already being synced. It pollutes the svn repository revisions with multiple copies of the same code, and makes it harder for a developer to differentiate between his own changes and those he pulled from a CVS-sync. We should use a workflow that takes advantage of the ability in svn to branch and merge directly with a 'main' branch that is being synced automatically with CVS.
Comments
Comment #1
calebgilbert commentedChanged the component to staging.drupal.org for visibility purposes.
Comment #2
rfayYou don't have to do step 2 - you can svn cp from the redesign version of drupalorg, as we'll keep that up to HEAD.
Comment #3
jwilson3ok, i stand corrected.
as rfay indicates above, the way this is to work (for redesign implementers anyway) is they need to branch from redesign/sites/all/modules/drupalorg into their staging module sandbox in svn. (instructions here) If you need to get an updated / clean version of drupalorg from HEAD, find rfay and ask him to run a sync.... and then merge your sandbox with the redesign branch.
however, this is still an underlying issue, not exclusively related to staging. It would be awesome to have all syncing setup automatically probably with the vendor branch, somewhat in the same way that http://subversible.com/svn/drupal and http://subversible.com/svn/modules works.
Comment #4
jwilson3freakin browser caching form-items is killing me today.
Comment #5
drummNo longer using SVN.