Hi Glenn,
On 18/12/2012 16:27, Glenn Adams wrote:
On Mon, Dec 17, 2012 at 7:54 AM, Chris Bowditch
bowditch_ch...@hotmail.com mailto:bowditch_ch...@hotmail.com wrote:
Hi Glenn,
On 17/12/2012 15:24, Glenn Adams wrote:
but after a new release, the issue would effectively
On Mon, Dec 17, 2012 at 7:54 AM, Chris Bowditch
bowditch_ch...@hotmail.comwrote:
Hi Glenn,
On 17/12/2012 15:24, Glenn Adams wrote:
but after a new release, the issue would effectively apply to both trunk
and the new release, and an issue can only be associated with one version
in JIRA;
Hi list,
In order to keep trace about works on versions, we should use the Jira
feature to indicate what version is fixed.
in almost cases, fixes are against the trunk. Since in Jira one can
rename the version name (see [1]), during the FOP release process (at
branching or tagging stage), we
On 17/12/2012 09:08, Pascal Sancho wrote:
Hi list,
Hi Pascal,
In order to keep trace about works on versions, we should use the Jira
feature to indicate what version is fixed.
I agree.
in almost cases, fixes are against the trunk. Since in Jira one can
rename the version name (see
Hi,
Well, the fixed list has become not empty!
I've added a link to JIRA in changes list.
You can see it on http://xmlgraphics.staging.apache.org/fop/changes.html.
If there is no objection, I'll commit it on site prod tomorrow.
2012/12/17 Chris Bowditch bowditch_ch...@hotmail.com:
On
but after a new release, the issue would effectively apply to both trunk
and the new release, and an issue can only be associated with one version
in JIRA;
if the issue isn't fixed by the time the release occurs, then it is
unlikely to be fixed in the release version as much as being fixed in
Hmm,
2012/12/17 Glenn Adams gl...@skynav.com:
but after a new release, the issue would effectively apply to both trunk and
the new release, and an issue can only be associated with one version in
JIRA;
I'm not sure if you speak about the [Affect] field, or the [Fix] field.
The former can be
Hi Glenn,
On 17/12/2012 15:24, Glenn Adams wrote:
but after a new release, the issue would effectively apply to both
trunk and the new release, and an issue can only be associated with
one version in JIRA;
But why does that matter? If a bug is fixed then in v3 say, then its
obvious its also
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530948#comment-13530948
]
Alexios Giotis commented on FOP-1840:
-
Luis Robert thank you for your quick replies
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530948#comment-13530948
]
Alexios Giotis commented on FOP-1840:
-
Luis Robert thank you for your quick replies
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530458#comment-13530458
]
Luis Bernardo commented on FOP-1840:
you need to have the fo:block span=all / for the
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530494#comment-13530494
]
Luis Bernardo commented on FOP-1840:
applied attachment 12560540 (patch):
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530494#comment-13530494
]
Luis Bernardo commented on FOP-1840:
applied attachment 12560540 (patch):
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529137#comment-13529137
]
Alexios Giotis commented on FOP-1840:
-
The algorithm seems broken when the content is
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529137#comment-13529137
]
Alexios Giotis commented on FOP-1840:
-
The algorithm seems broken when the content is
[
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527667#comment-13527667
]
Luis Bernardo commented on FOP-1840:
applied patch 12559043:
16 matches
Mail list logo
