community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anto...@gmx.de
Subject Re: [reporter.apache.org] Using SVN to record current deployed code
Date Mon, 06 Jul 2015 18:19:05 GMT
Sounds good.

Sent from my android device.

-----Original Message-----
From: sebb <sebbaz@gmail.com>
To: dev@community.apache.org
Sent: Mon, 06 Jul 2015 2:11 PM
Subject: [reporter.apache.org] Using SVN to record current deployed code

The reporter.apache.org code on disk has diverged from the copy in SVN.
There are several files that are not in SVN, and there a several
differences from the ones that are.

One approach to this might be to copy  the current sources into SVN
into a new folder.
Then we can look at merging the current code and redeploying.

I was thinking of using an SVN tag for the deployed source, but the
SVN directory for reporter.a.o does not use tags/trunk. I could use a
new directory name like

https://svn.apache.org/repos/asf/comdev/reporter.apache.org-ondisk

but this is not the normal way to use SVN, and might prove confusing later.

So I would like to start by moving the current code under

https://svn.apache.org/repos/asf/comdev/reporter.apache.org
to
https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk
(i.e. drop it down a level)
and then use tags/disk-2015-07-06 (or whatever) to record the current setup

Note that the generated data files (*.json) don't need to be stored in SVN.

Thoughts?
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message