kicad-developers team mailing list archive

["Dick H." <dick@...>]

--6-1460394613-7835979897=:7 Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

1) The November release candidate has been copied into
https://kicad.svn.sourceforge.net/svnroot/kicad/tags/kicad-2007-Nov

Notice that the day of month has been dropped and we are using 'Nov'
instead of 11. This sub-tree can contain fixes to anything in the
legacy of the "Nov 2007" release. For new users, they can check out the
latest from this subtree using this command:

svn co
https://kicad.svn.sourceforge.net/svnroot/kicad/tags/kicad-2007-Nov

(all on one line.)

2) As of this snap shot, and for the immediate and indefinite future,
HEAD is no longer considered stable. It is no longer to be considered
representative of the "Nov 2007" release or release candidate. For
maintainers/developers or users wanting to change their working copy
temporarily to the stable kicad-2007-Nov tree, say in order to fix bugs
in the release candidate or to grab the latest stable "Nov 2007"
version, then:

cd <existing working copy>

svn switch
https://kicad.svn.sourceforge.net/svnroot/kicad/tags/kicad-2007-Nov

(svn command all on one line.)

If you need more info on svn switch, read more about switch here:

http://svnbook.red-bean.com/en/1.4/svn-book.html#svn.branchmerge.switchw\
c

After the switch, your working copy can be used to commit changes to the
kicad-2007-Nov subtree in a normal way.


3) To switch your working copy back to the HEAD of the trunk:

cd <working copy>

svn switch https://kicad.svn.sourceforge.net/svnroot/kicad/trunk/kicad

(svn command all on one line.)


4) HEAD is subject to immediate and potentially drastic change, whatever
it takes for us to do the zone improvements. Please don't expect it to
be usable soon.


5) With this strategy in place, I see no reason to also copy the "Nov
2007" release to the branch subtree, as originally discussed here.



Regards,

Dick Hollenbeck
SoftPLC Corporation
http://softplc.com


 --6-1460394613-7835979897=:7 Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

1) The November release candidate has been copied into <br><b>https://kicad=
.svn.sourceforge.net/svnroot/kicad/tags/kicad-2007-Nov</b><br><br>Notice th=
at the day of month has been dropped and we are using 'Nov' instead of 11.&=
nbsp; This sub-tree can contain fixes to anything in the legacy of the "Nov=
2007" release.&nbsp; For new users, they can check out the latest from thi=
s subtree using this command:<br><br><blockquote><font color=3D"#0000ff">sv=
n co https://kicad.svn.sourceforge.net/svnroot/kicad/tags/kicad-2007-Nov</f=
ont><br></blockquote><br>(all on one line.)<br><br><br>2) As of this snap s=
hot, and for the immediate and indefinite future, <b><font color=3D"#ff007f=
">HEAD is no longer considered stable</font></b>.&nbsp; It is no longer to =
be considered representative of the "Nov 2007" release or release candidate=
.&nbsp; For maintainers/developers or users wanting to change their working=
copy temporarily to the stable kicad-2007-Nov tree, say in order to fix bu=
gs in the release candidate or to grab the latest stable "Nov 2007" version=
, then:<br><br>cd &lt;<b>existing</b> working copy&gt;<br><br><blockquote><=
font color=3D"#0000ff">svn switch https://kicad.svn.sourceforge.net/svnroot=
/kicad/tags/kicad-2007-Nov</font><br></blockquote><br>(svn command all on o=
ne line.)<br><br>If you need more info on svn switch, read more about switc=
h here:<br><br><blockquote>http://svnbook.red-bean.com/en/1.4/svn-book.html=
#svn.branchmerge.switchwc<br></blockquote><br>After the switch, your workin=
g copy can be used to commit changes to the kicad-2007-Nov subtree in a nor=
mal way.<br><br><br>3) To switch your working copy back to the HEAD of the =
trunk:<br><br>cd &lt;working copy&gt;<br><br><blockquote><font color=3D"#00=
00ff">svn switch https://kicad.svn.sourceforge.net/svnroot/kicad/trunk/kica=
d</font><br></blockquote><br>(svn command all on one line.)<br><br><br>4) H=
EAD is subject to immediate and potentially drastic change, whatever it tak=
es for us to do the zone improvements.&nbsp; Please don't expect it to be u=
sable soon.<br><br><br>5) With this strategy in place, I see no reason to a=
lso copy the "Nov 2007" release to the branch subtree, as originally discus=
sed here.<br><br><br><br>Regards,<br><br>Dick Hollenbeck<br>SoftPLC Corpora=
tion<br>http://softplc.com<br><br>
 --6-1460394613-7835979897=:7--