[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    kdesupport changes
From:       "Benoit Jacob" <jacob.benoit.1 () gmail ! com>
Date:       2008-09-02 14:01:48
Message-ID: d9f848520809020701p513cfc50v4594dd6a430d0c58 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi,

I just found out these discussions on the release-team list, to which I was
not
subscribed:

http://mail.kde.org/pipermail/release-team/2008-August/002395.html
http://mail.kde.org/pipermail/release-team/2008-August/002433.html

My questions are:

1. Is /trunk/kdesupport going to be no longer recommended to build KDE SVN?
I
mean e.g. on the techbase page,
http://techbase.kde.org/Getting_Started/Build/KDE4/Prerequisites#kdesupport
Any plan to update that page to no longer recommend to
checkout /trunk/kdesupport?

2. What is the difference between a "tag" and a "branch" ? I seem to see a
lot
of overlap between /tags and /branches.

3. So what is the "tag" that I should create for version x.y of eigen: is
it /tags/eigen/x.y ?

4. We are about to release a beta version of eigen but the 2.0 final will
have
to wait about 6-10 more weeks. Shall I still create a tag as soon as
possible? /tags/eigen/2.0-beta1 ? Or wait until 2.0 to create a tag?

5. After we create a tag does that mean that we can do whatever we want
in /trunk/kdesupport/eigen2 without risking to break compilation for other
people? This is related to question 1. As long as we tell people to use
trunk/kdesupport, making tags is rather pointless.

Cheers,
Benoit


> Howdy,
>
> If you are a developer of a kdesupport project, please make sure
> that your latest-and-greatest stable version is tagged
> in our subversion tags repository.
>
> The "lastest-and-greatest stable version" should be the version
> that we need to use when building trunk.
>
> If you need help with this, please send a note to release-team ML.
>
> -Allen

[Attachment #5 (text/html)]

<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">htt \
p://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 &quot;tag&quot; and a \
&quot;branch&quot; ? I seem to see a lot <br>of overlap between /tags and \
/branches.<br><br>3. So what is the &quot;tag&quot; 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>&gt; Howdy,<br>&gt;<br>&gt; If you are \
a developer of a kdesupport project, please make sure<br>&gt; that your \
latest-and-greatest stable version is tagged<br> &gt; in our subversion tags \
repository.<br>&gt;<br>&gt; The &quot;lastest-and-greatest stable version&quot; \
should be the version<br>&gt; that we need to use when building \
trunk.<br>&gt;<br>&gt; If you need help with this, please send a note to release-team \
ML.<br> &gt;<br>&gt; -Allen<br></div>



_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


[prev in list] [next in list] [prev in thread] [next in thread]