Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-19 Thread Chris Bowditch
On 18/07/2012 15:24, Clay Leeds wrote: Hi Clay, OT, but I've made some progress on the CMS. I now have dynamic content working (separate header and sidenav for FOP, Batik XGC). Thanks for the update. That is good news. Chris More relevant comments below... On Jul 18, 2012, at 5:17 AM,

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-19 Thread Chris Bowditch
On 18/07/2012 14:06, mehdi houshmand wrote: Hi Mehdi, As we've seen this morning, my ineptitude at even basic bureaucracy doesn't really qualify me to show a bias to either side, but I'll give my 2 cents worth since I am a stakeholder in this debate: On 18 July 2012 13:17, Vincent Hennebert

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-19 Thread mehdi houshmand
I know this isn't directly relevant to this tread, but something else to consider while we're on the subject of JIRA and bug tracking is integration between SVN and JIRA itself. Having worked a little bit with PDFBox, they seem to have quite tight integration between the two such that (I think)

Re: SVN/Jira integration was: [Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-19 Thread Alexios Giotis
Hi Mehdi, I will continue the hijacking of the commit message . I feel that opening a new thread might be disturbing and I don't know if the FOP community is interested. I hope I am helping a little to improve the processes and not spamming your inbox. I am not familiar with the Apache

Re: SVN/Jira integration was: [Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-19 Thread mehdi houshmand
Hi Alex, Thanks for the response, that's been very informative, I think if we considered SVN/Jenkins integration, it'd make life a lot easier. The more we can automate, the fewer the mistakes, that's pretty much my only reasoning, though obviously it'd have to be investigated to come up with a

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-18 Thread Vincent Hennebert
Hi Alexios, thanks for you input. On 18/07/12 01:05, Alexios Giotis wrote: Hi Vincent, On Jul 17, 2012, at 12:10 PM, Vincent Hennebert wrote: On 13/07/12 22:52, Alexios Giotis wrote: A change log or release notes can be generated by Jira [1]. For example, [2] is the release notes for

Switching to JIRA [was: Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/]

2012-07-18 Thread Vincent Hennebert
On 18/07/12 01:14, Glenn Adams wrote: On Tue, Jul 17, 2012 at 6:05 PM, Alexios Giotis alex.gio...@gmail.comwrote: The end result is to provide a documentation trail. I initially replied to this thread because Jira is not (yet) used in FOP and it happens to provide this feature. FYI,

Re: Switching to JIRA [was: Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/]

2012-07-18 Thread Alexios Giotis
On Jul 18, 2012, at 3:19 PM, Vincent Hennebert wrote: On 18/07/12 01:14, Glenn Adams wrote: On Tue, Jul 17, 2012 at 6:05 PM, Alexios Giotis alex.gio...@gmail.comwrote: The end result is to provide a documentation trail. I initially replied to this thread because Jira is not (yet) used in

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-18 Thread mehdi houshmand
As we've seen this morning, my ineptitude at even basic bureaucracy doesn't really qualify me to show a bias to either side, but I'll give my 2 cents worth since I am a stakeholder in this debate: On 18 July 2012 13:17, Vincent Hennebert vhenneb...@gmail.com wrote: snip/ Well, the problem is

Re: Switching to JIRA [was: Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/]

2012-07-18 Thread Vincent Hennebert
On 18/07/12 13:46, Alexios Giotis wrote: On Jul 18, 2012, at 3:19 PM, Vincent Hennebert wrote: On 18/07/12 01:14, Glenn Adams wrote: On Tue, Jul 17, 2012 at 6:05 PM, Alexios Giotis alex.gio...@gmail.comwrote: The end result is to provide a documentation trail. I initially replied to

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-18 Thread Clay Leeds
OT, but I've made some progress on the CMS. I now have dynamic content working (separate header and sidenav for FOP, Batik XGC). More relevant comments below... On Jul 18, 2012, at 5:17 AM, Vincent Hennebert vhenneb...@gmail.com wrote: Hi Alexios, thanks for you input. On 18/07/12

Re: Switching to JIRA [was: Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/]

2012-07-18 Thread Glenn Adams
On Wed, Jul 18, 2012 at 7:44 AM, Vincent Hennebert vhenneb...@gmail.comwrote: On 18/07/12 13:46, Alexios Giotis wrote: On Jul 18, 2012, at 3:19 PM, Vincent Hennebert wrote: On 18/07/12 01:14, Glenn Adams wrote: On Tue, Jul 17, 2012 at 6:05 PM, Alexios Giotis alex.gio...@gmail.com

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-17 Thread Chris Bowditch
On 16/07/2012 14:33, Glenn Adams wrote: Hi Glenn, On Mon, Jul 16, 2012 at 5:19 AM, Chris Bowditch bowditch_ch...@hotmail.com mailto:bowditch_ch...@hotmail.com wrote: I'm in favour of changing the policy to always open a Bugzilla/Jira entry for every bug fixed in FOP. However, it

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-17 Thread Vincent Hennebert
On 13/07/12 22:52, Alexios Giotis wrote: A change log or release notes can be generated by Jira [1]. For example, [2] is the release notes for Apache PDFBox 1.7. Bug or issue titles (at least) tend to be better, if it is known that the change log is generated by such a system. Glenn wrote

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-17 Thread Alexios Giotis
Hi Vincent, On Jul 17, 2012, at 12:10 PM, Vincent Hennebert wrote: On 13/07/12 22:52, Alexios Giotis wrote: A change log or release notes can be generated by Jira [1]. For example, [2] is the release notes for Apache PDFBox 1.7. Bug or issue titles (at least) tend to be better, if it is

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-17 Thread Glenn Adams
On Tue, Jul 17, 2012 at 6:05 PM, Alexios Giotis alex.gio...@gmail.comwrote: The end result is to provide a documentation trail. I initially replied to this thread because Jira is not (yet) used in FOP and it happens to provide this feature. FYI, Alex, if you aren't aware of it, the project

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-16 Thread Chris Bowditch
On 13/07/2012 09:05, Pascal Sancho wrote: Hi, Hi Pascal, IMHO, using a bugtracker system to list bugfix or changes is a good idea. But today, the practice in FOP project is to fill this list directly in the cited page. We can adopt a new policy here and have a change/bugfix list using

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-16 Thread Glenn Adams
On Mon, Jul 16, 2012 at 5:19 AM, Chris Bowditch bowditch_ch...@hotmail.comwrote: I'm in favour of changing the policy to always open a Bugzilla/Jira entry for every bug fixed in FOP. However, it won't always be possible to upload resources to replicate the issue. Whilst we can clean any FO

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-13 Thread Pascal Sancho
Hi, IMHO, using a bugtracker system to list bugfix or changes is a good idea. But today, the practice in FOP project is to fill this list directly in the cited page. We can adopt a new policy here and have a change/bugfix list using bugtracker facilities. That could be done when we'll migrate to

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-13 Thread Glenn Adams
On Fri, Jul 13, 2012 at 2:05 AM, Pascal Sancho psancho@gmail.comwrote: IMHO, using a bugtracker system to list bugfix or changes is a good idea. But today, the practice in FOP project is to fill this list directly in the cited page. We can adopt a new policy here and have a change/bugfix

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-13 Thread Pascal Sancho
I'm ok with that, but all fop team should be convinced... So debate (if that need to discuss) is open ;-) 2012/7/13 Glenn Adams gl...@skynav.com: On Fri, Jul 13, 2012 at 2:05 AM, Pascal Sancho psancho@gmail.com wrote: IMHO, using a bugtracker system to list bugfix or changes is a good

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-13 Thread Vincent Hennebert
On 13/07/12 14:07, Glenn Adams wrote: On Fri, Jul 13, 2012 at 2:05 AM, Pascal Sancho psancho@gmail.comwrote: IMHO, using a bugtracker system to list bugfix or changes is a good idea. But today, the practice in FOP project is to fill this list directly in the cited page. We can adopt a

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-13 Thread Glenn Adams
On Fri, Jul 13, 2012 at 9:08 AM, Vincent Hennebert vhenneb...@gmail.comwrote: We can decide to change that and use a bug tracking system instead, but in the same time we do that we will have to have in place a new mechanism to generate the changes [1] page. Also, we will most likely have to

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-13 Thread Alexios Giotis
A change log or release notes can be generated by Jira [1]. For example, [2] is the release notes for Apache PDFBox 1.7. Bug or issue titles (at least) tend to be better, if it is known that the change log is generated by such a system. Glenn wrote very good points. It will help the FOP

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-12 Thread Glenn Adams
Is this addressing a specific bug? If not, then please enter a bug and update the status to ensure this association for documentation and release notes tracking purposes. Also, I notice you left a printf in place below. Is that intentional? If so, then I would suggest using something other than

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-12 Thread Vincent Hennebert
On 12/07/12 14:37, Glenn Adams wrote: Is this addressing a specific bug? If not, then please enter a bug and update the status to ensure this association for documentation and release notes tracking purposes. I added an entry in the status.xml file. Also, I notice you left a printf in place

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-12 Thread Glenn Adams
On Thu, Jul 12, 2012 at 7:45 AM, Vincent Hennebert vhenneb...@gmail.comwrote: On 12/07/12 14:37, Glenn Adams wrote: Is this addressing a specific bug? If not, then please enter a bug and update the status to ensure this association for documentation and release notes tracking purposes.

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-12 Thread Vincent Hennebert
On 12/07/12 14:47, Glenn Adams wrote: On Thu, Jul 12, 2012 at 7:45 AM, Vincent Hennebert vhenneb...@gmail.comwrote: On 12/07/12 14:37, Glenn Adams wrote: Is this addressing a specific bug? If not, then please enter a bug and update the status to ensure this association for documentation

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-12 Thread Glenn Adams
On Thu, Jul 12, 2012 at 9:00 AM, Vincent Hennebert vhenneb...@gmail.comwrote: On 12/07/12 14:47, Glenn Adams wrote: On Thu, Jul 12, 2012 at 7:45 AM, Vincent Hennebert vhenneb...@gmail.com wrote: On 12/07/12 14:37, Glenn Adams wrote: Is this addressing a specific bug? If not, then please

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-12 Thread Vincent Hennebert
On 12/07/12 16:17, Glenn Adams wrote: On Thu, Jul 12, 2012 at 9:00 AM, Vincent Hennebert vhenneb...@gmail.comwrote: On 12/07/12 14:47, Glenn Adams wrote: On Thu, Jul 12, 2012 at 7:45 AM, Vincent Hennebert vhenneb...@gmail.com wrote: On 12/07/12 14:37, Glenn Adams wrote: Is this

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

2012-07-12 Thread Glenn Adams
On Thu, Jul 12, 2012 at 10:47 AM, Vincent Hennebert vhenneb...@gmail.comwrote: On 12/07/12 16:17, Glenn Adams wrote: If there is no bug entry in bugzilla, then there is/was no bug. Since this is clearly a bug fix, there should be a documentation trail through the bug database. So please