On 1/13/2011 11:03 AM, Pablo Beltran wrote:
Relationships between issues and releases/tags are well supported by
Subversion because the concept "Release" in a tracker can be directly
related with a tag in Subversion. Depending of your needs, tracking
revisions only at the "release" level may be
Hola,
I think the problem is we are using the same words with a different
criteria. So let me clarify with a real example.
Below is a link to a real Apache's tracker issue: DERBY-4857
https://issues.apache.org/jira/browse/DERBY-4857?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-comm
Hola, Pablo.
El 20:59, Pablo Beltran escribió:
>
[...]
That is mainly because many things happens BEFORE Subversion revisions
are created. For example, when a bug is detected there is not a
revision to be related until the bug is fixed in Subversion.
[...]
I'm afraid I don't understand you
LABELS might add a new dimension to Subversion: (2D -> 3D)
http://www.svnflash.com/images/svnflash/subversion_3d.gif
I've used Jira issues instead of LABELS because I think that people will
better understand the example more easily.
Subversion is a very good tool for SCM (Software Configuration
That sort of information can be represented in the current 2D Subversion
space as the line between two points:
Example: http://www.svnflash.com/images/svnflash/branch_is_2d.png
If the */a/b* item at the *N+2* revision is replaced (could be also copied
or merged) with the previous content of the *
On Mon, 2011-01-10 at 18:46 +0100, Pablo Beltran wrote:
> Hi,
>
> Subversion tracks the evolution of a tree structure along the time.
> Changes can be represented in a bi-dimensional system coordinates:
> time vs space.
>
> The vertical coordinate (space) is the path of the items of the tree
> st
