org
<mailto:fop-dev@xmlgraphics.apache.org>
Subject: New FOP Release [was: Re: FOP Release Automation]
Hi,
On 15/07/14 16:53, Clay Leeds wrote:
On Jul 15, 2014, at 7:46 AM, Glenn Adams mailto:gl...@skynav.com>> wrote:
I suppose it de
e.g., when should last
changes be integrated?
- what additional integrations (if known) are planned before release?
>
> Vincent
>
>
> Thanks
>>
>> -Original Message-
>> From: Vincent Hennebert [mailto:vhenneb...@gmail.com]
>> Sent: 16 July 201
ready.
Vincent
Thanks
-Original Message-
From: Vincent Hennebert [mailto:vhenneb...@gmail.com]
Sent: 16 July 2014 12:56
To: fop-dev@xmlgraphics.apache.org
Subject: New FOP Release [was: Re: FOP Release Automation]
Hi,
On 15/07/14 16:53, Clay Leeds wrote:
On Jul 15, 2014, at 7:46 AM
Subject: New FOP Release [was: Re: FOP Release Automation]
Hi,
On 15/07/14 16:53, Clay Leeds wrote:
> On Jul 15, 2014, at 7:46 AM, Glenn Adams wrote:
>> I suppose it depends on whether or not we need to hack perl to use the
>> facility. If there is any alternative that doesn't
Hi,
On 15/07/14 16:53, Clay Leeds wrote:
On Jul 15, 2014, at 7:46 AM, Glenn Adams wrote:
I suppose it depends on whether or not we need to hack perl to use the
facility. If there is any alternative that doesn't use perl, then that would be
preferable.
Frankly, I've never been happy with the
dated.
> Subject: Re: FOP Release Automation
> From: the.webmaes...@gmail.com
> Date: Tue, 15 Jul 2014 07:53:19 -0700
> To: fop-dev@xmlgraphics.apache.org
>
> On Jul 15, 2014, at 7:46 AM, Glenn Adams wrote:
> > I suppose it depends on whether or not we need to hack perl to use t
I prefer python but bash is fine. OTOH, anything written by Larry Wall
should be avoided like the plague.
On Tue, Jul 15, 2014 at 8:53 AM, Clay Leeds
wrote:
> On Jul 15, 2014, at 7:46 AM, Glenn Adams wrote:
> > I suppose it depends on whether or not we need to hack perl to use the
> facility.
On Jul 15, 2014, at 7:46 AM, Glenn Adams wrote:
> I suppose it depends on whether or not we need to hack perl to use the
> facility. If there is any alternative that doesn't use perl, then that would
> be preferable.
>
> Frankly, I've never been happy with the new MD based documentation, though
s for the time being. I will keep an eye
>> out on the infrastructure page and prod them occasionally to see if I can
>> move things along.
>>
>> Apologies for the long e-mail but just wanted to keep you all updated.
>>
>> Robert Meyer
>>
>> > Date
d feature and as such knowledge on the subject may be in short supply. As
>> such and without possibility of using the markdown extension we're left with
>> the manual process for the time being. I will keep an eye out on the
>> infrastructure page and prod them o
> Apologies for the long e-mail but just wanted to keep you all updated.
>
> Robert Meyer
>
> > Date: Mon, 2 Jun 2014 14:44:58 +0100
> > From: bowditch_ch...@hotmail.com
> > To: fop-dev@xmlgraphics.apache.org
> > Subject: Re: FOP Release Automation
> >
>
f I can move things along.
Apologies for the long e-mail but just wanted to keep you all updated.
Robert Meyer
> Date: Mon, 2 Jun 2014 14:44:58 +0100
> From: bowditch_ch...@hotmail.com
> To: fop-dev@xmlgraphics.apache.org
> Subject: Re: FOP Release Automation
>
> Hi All,
&g
From: simonsteiner1...@gmail.com <mailto:simonsteiner1...@gmail.com>
To: fop-dev@xmlgraphics.apache.org
<mailto:fop-dev@xmlgraphics.apache.org>
Subject: RE: FOP Release Automation
Date: Fri, 30 May 2014 14:48:15 +0100
Hi,
Simple way is to store docs inside fop repo:
Fop/docs/index.markdown
Insi
Robert Meyer :
> I'll definitely look into those. I'm going to be away on holiday now for a
> week or so but will continue once I get back.
>
> Many thanks!
>
> Robert
>
> From: Clay Leeds
> Sent: 5/30/2014 17:24
> To: Apache FOP
P<mailto:fop-dev@xmlgraphics.apache.org>
Subject: Re: FOP Release Automation
Agreed, ‘some’ people wouldn’t be happy with that. ;-)
I wonder if the CMS Web interface could be extended to allow for a few keywords
like FOP_VERSION, FOP_REVISION, FOP_BRANCH, etc.
The CMS tool's WYSIWYG interface in
copy would become out of date.
>
> We could always shutdown the web interface, but I don't think too many people
> would be happy with that ;-)
>
> Regards,
>
> Robert
>
> From: simonsteiner1...@gmail.com
> To: fop-dev@xmlgraphics.apache.org
> Subject
think too many people
would be happy with that ;-)
Regards,
Robert
From: simonsteiner1...@gmail.com
To: fop-dev@xmlgraphics.apache.org
Subject: RE: FOP Release Automation
Date: Fri, 30 May 2014 14:48:15 +0100
Hi, Simple way is to store docs inside fop repo: Fop/docs/index.markdown Inside
mar
bert Meyer [mailto:rme...@hotmail.co.uk]
Sent: 30 May 2014 14:05
To: fop-dev@xmlgraphics.apache.org
Subject: RE: FOP Release Automation
Hi,
After investigating your suggestions Clay I have found that svn-hooks can't
be used for the purpose we require unfortunately as it may lead to proble
Hi,
After investigating your suggestions Clay I have found that svn-hooks can't be
used for the purpose we require unfortunately as it may lead to problems with
how SVN operates and also may have some unexpected results with files being
committed. This is stated in the documentation under "Crea
the
> idea of copying the trunk folder and doing a find / replace on say "trunk"
> and replacing with "2.0" would be an option (with some caveats), but I'll
> investigate the other methods first.
>
> I'll keep you posted.
>
> Regards,
>
> Robert Me
ace on say "trunk" and replacing with
"2.0" would be an option (with some caveats), but I'll investigate the other
methods first.
I'll keep you posted.
Regards,
Robert Meyer
> Subject: Re: FOP Release Automation
> From: the.webmaes...@gmail.com
> Da
in released versions until v1.1, whole website was included in
src/documentation, using the old Forrest schema.
So, until v1.1, the website repo may embed directly versionned doc.
I don't think we need to remove them, just adding or removing a link
in sidenav will be sufficient (0.95 doc is always
Hi,
I thought I'd give an update on my research of speeding the RELEASE process...
I've spent some time researching, and I've asked for some assistance from
site-dev@...
Among the ideas I've been researching are:
- MarkDown PreProcessor[1]
- svn hook
I'm not married to either of these solution
Hi,
The FOP package should not embed the whole website, but only the
documentation part, more precisely only the relevant version folder.
Currently, FOP doc folder is referenced as svn:externals in FOP repo,
resulting on extra irrelevant info, such as other versions,
miscellaneous processes, gene
Thank you for looking at this, Robert. I'll take a look at MarkDown solutions
as well.
Cheers!
Clay
--
"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet
> On May 21, 2014, at 2:24 AM, Robert Meyer wrote:
>
> Hi All,
>
> I've been asked to look at a way to autom
25 matches
Mail list logo
