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 fixed in v4.
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
trunk; so that would argue for keeping the issue associated with trunk
and not the new version
Are you saying there is a possible flaw in the suggested process that
mean some bugs fixed after the release branch were created are marked
incorrectly. IIUC, As long as the fixed in version is updated at the
same point in time the release branch is created this should be a non issue.
so i think i don't agree with this suggestion as i understand it
Thanks,
Chris
On Mon, Dec 17, 2012 at 2:08 AM, Pascal Sancho <[email protected]
<mailto:[email protected]>> wrote:
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 could rename (in Jira) the "trunk" to
the released version name, then create a new "trunk" entry.
WDYT?
[1]
https://confluence.atlassian.com/display/JIRA/Managing+Versions#ManagingVersions-Editingaversion%27sdetails
2012/12/14 Alexios Giotis <[email protected]
<mailto:[email protected]>>:
> Hi Pascal,
>
> I noticed the "Fix Version/s" Jira field and I was tempted to
update it while resolving the issue. But the only version that
applies is "trunk" which is a moving target...
>
> I have not seen any guidelines related to Jira and FOP. If I
miss something, please do tell me. I think, one should first
decide the version number of the trunk (1.2 ? 2.0 ?) and add it to
Jira. If an issue requires changes in code, then committers need
to resolve it and update the "Fix" version. Finally, Jira creates
"Release notes" based on this information and one should consider
if and how this affects the usage of the status.xml
>
> Alexis
>
>
>
>
>
> On 14 Dec 2012, at 17:07, Pascal Sancho <[email protected]
<mailto:[email protected]>> wrote:
>
>> Hi,
>>
>> before closing a bug, I think one should indicate what version its
>> resolution does affect.
>>
>> The goal is to easily manage changes pages in FOP website.
>>
>> 2012/12/14 Alexis Giotis (JIRA) <[email protected]
<mailto:[email protected]>>:
>>>
>>> [
https://issues.apache.org/jira/browse/FOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
>>>
>>> Alexis Giotis closed FOP-1840.
>>> ------------------------------
>>>
>>>
>>>> [PATCH] Region-Body Column balancing incorrect if content is
table with header
>>>>
------------------------------------------------------------------------------
>>>>
>>>> Key: FOP-1840
>>>> URL:
https://issues.apache.org/jira/browse/FOP-1840
>>>> Project: Fop
>>>> Issue Type: Improvement
>>>> Components: page-master/layout
>>>> Affects Versions: 1.0
>>>> Environment: Operating System: All
>>>> Platform: PC
>>>> Reporter: a.kovacs
>>>> Assignee: fop-dev
>>>>
>>>> (...)
--
pascal
