Mailing-List: contact ctakes-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ctakes-dev@incubator.apache.org
Date: Fri, 13 Jul 2012 17:59:35 +0000 (UTC)
From: "Pei Chen (JIRA)" <jira@apache.org>
To: ctakes-dev@incubator.apache.org
Message-ID: <751960694.49395.1342202375171.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (CTAKES-10) Pre-Migration- Pre initial code base
 from sourceforge to ASF SVN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Pei Chen created CTAKES-10:
------------------------------

             Summary: Pre-Migration- Pre initial code base from sourceforge=
 to ASF SVN
                 Key: CTAKES-10
                 URL: https://issues.apache.org/jira/browse/CTAKES-10
             Project: cTAKES
          Issue Type: Task
            Reporter: Pei Chen
            Assignee: Joern Kottmann


Agree on how do we migrate from sourceforge SVN to Apache SVN  (One option =
is to create an exact copy of current SVN from sourceforge and check it int=
o Apache in order to have a complete audit trail of refactoring changes mad=
e within Apache.)
                I think that this is a good idea, but I think that we might=
 do well committing refactoring changes to a branch and then when =E2=80=93=
done- (we need to have defined goals) move the branch to trunk all in a sin=
gle go.  That way the trunk history has a decent starting point.  But I don=
=E2=80=99t think that it really much matters.  SPF


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira