<div dir="ltr">Hi,<br><br>I just found out these discussions on the release-team list, to which I was not <br>subscribed:<br><br><a href="http://mail.kde.org/pipermail/release-team/2008-August/002395.html">http://mail.kde.org/pipermail/release-team/2008-August/002395.html</a><br>
<a href="http://mail.kde.org/pipermail/release-team/2008-August/002433.html">http://mail.kde.org/pipermail/release-team/2008-August/002433.html</a><br><br>My questions are:<br><br>1. Is /trunk/kdesupport going to be no longer recommended to build KDE SVN? I <br>
mean e.g. on the techbase page,<br><a href="http://techbase.kde.org/Getting_Started/Build/KDE4/Prerequisites#kdesupport">http://techbase.kde.org/Getting_Started/Build/KDE4/Prerequisites#kdesupport</a><br>Any plan to update that page to no longer recommend to <br>
checkout /trunk/kdesupport?<br><br>2. What is the difference between a "tag" and a "branch" ? I seem to see a lot <br>of overlap between /tags and /branches.<br><br>3. So what is the "tag" that I should create for version x.y of eigen: is <br>
it /tags/eigen/x.y ?<br><br>4. We are about to release a beta version of eigen but the 2.0 final will have <br>to wait about 6-10 more weeks. Shall I still create a tag as soon as <br>possible? /tags/eigen/2.0-beta1 ? Or wait until 2.0 to create a tag?<br>
<br>5. After we create a tag does that mean that we can do whatever we want <br>in /trunk/kdesupport/eigen2 without risking to break compilation for other <br>people? This is related to question 1. As long as we tell people to use <br>
trunk/kdesupport, making tags is rather pointless.<br><br>Cheers,<br>Benoit<br><br><br>> Howdy,<br>><br>> If you are a developer of a kdesupport project, please make sure<br>> that your latest-and-greatest stable version is tagged<br>
> in our subversion tags repository.<br>><br>> The "lastest-and-greatest stable version" should be the version<br>> that we need to use when building trunk.<br>><br>> If you need help with this, please send a note to release-team ML.<br>
><br>> -Allen<br></div>