Ross Gardler wrote:
Ferdinand Soethe wrote:
DISCLAIMER
I have never done a release so I'm only giving you my interpretation of
the document. Authorative answers will come from elsewhere if I have got
something wrong.
A bit of background might help. Jeff Turner did the releases up to
David Crossley wrote:
Ross Gardler wrote:
...
Does this sound OK?
It sounds brilliant.
Indeed!
The part that i like most is that each project
is focussing on their own tools, we are not duplicating, and we are
collaborating.
David, it seems Ross cracked open the coconut [1] and we now
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
OK, along the same theme of quick hacks I've put a simple demo
together for you. To see it you need to checkout the
locationmap_branch of Forrest. Seed a fresh site, do forrest run and
look at the locaitonmap sample (last item in the samples
There are two skins of uncertain status: leather-dev and corium.
Are they part of the Views now and we don't need them any more?
They are not listed when we do 'forrest available-skins'.
If they are not needed, then can we remove them, as i reckon
they will confuse new users. Alternatively we
Gregor J. Rothfuss wrote:
...
so initially, people could write documents in lenya, publish them, and
then head over to forrest(bot?) to slurp all these pages in?
My personal view is not to use the Forrestbot, but to
mod_proxy/mod_cache a live Forrest instance that gets files from a
David Crossley wrote:
Ross Gardler wrote:
Ferdinand Soethe wrote:
...
- Create a new file, etc/RELEASE-NOTES-x.y.txt, where x.y is the version
currently being released. It is best to copy an earlier RELEASE-NOTES
file,
to keep a common layout.
In this file, provide a summary of changes,
David Crossley wrote:
Ross, are you able to explain what needs to happen with the plugins
at release-time. I mean do they all need to have -0.7 appended
to the names of the zip files?
Blast I forgot that entirely (again!). Yes we need two zipped versions,
a pluginname-0.7.zip and a
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
The new ability might assist, but we still need the RELEASE-NOTES-0.7.txt
file.
cd FORREST_HOME/site-author
forrest run
http://localhost:/releaseNotes_0.7-dev.txt
What's missing from this document, I'll fix it while
[EMAIL PROTECTED] wrote:
Author: crossley
Date: Wed Jun 8 00:29:42 2005
New Revision: 189541
URL: http://svn.apache.org/viewcvs?rev=189541view=rev
Log:
Add missing @type attribute for one entry.
sorry, I was testing jedit for editing status.
Do you think that this attribute should be marked
David Crossley wrote:
This time it sounds like Ferdinand is offering to help.
Yes, I'll try. The reason I didn't say so before asking the questions
was that I want to fully understand what I have to do before I commit
myself to doing it ...
That is great, because we need more people to
Ferdinand Soethe wrote:
David Crossley wrote:
...
A first step would be to update the instructions before i start.
Anybody mind if I update them to show more details for people w/o that
background?
Mind, I hate doing those kinds of jobs, please be my guest. (note David
already did some
Nicola Ken Barozzi wrote:
David Crossley wrote:
Ross Gardler wrote:
...
Does this sound OK?
It sounds brilliant.
Indeed!
The part that i like most is that each project
is focussing on their own tools, we are not duplicating, and we are
collaborating.
David, it seems Ross cracked
Nicola Ken Barozzi wrote:
Gregor J. Rothfuss wrote:
...
so initially, people could write documents in lenya, publish them, and
then head over to forrest(bot?) to slurp all these pages in?
My personal view is not to use the Forrestbot, but to
mod_proxy/mod_cache a live Forrest instance
Following the developing discussion amongst you and having tried to do
a few of the things you mentioned, I'm feeling slightly overwhelmed by
the complexity of the task.
So looking at our ambitious time frame I'd like to take up David on
his offer
I reckon it would be better that i do the
Juan Jose Pablos wrote:
[EMAIL PROTECTED] wrote:
Author: crossley
Date: Wed Jun 8 00:29:42 2005
New Revision: 189541
URL: http://svn.apache.org/viewcvs?rev=189541view=rev
Log:
Add missing @type attribute for one entry.
sorry, I was testing jedit for editing status.
Do you think that this
David Crossley wrote:
Tim Williams wrote:
Ross Gardler wrote:
According to my understanding as expressed above a cocoon:/ in the
project sitemap will *not* search the root sitemap, a cocoon:// will.
Of course, you have provided an example that indicates this is not the
case despite the
Add version control to plugins
--
Key: FOR-528
URL: http://issues.apache.org/jira/browse/FOR-528
Project: Forrest
Type: Improvement
Versions: 0.7-dev
Reporter: Ross Gardler
Assigned to: Ross Gardler
Priority: Blocker
David Crossley wrote:
- Set your Java version to be the lowest specified of our supported
versions.
Where is the definitive info on the supported versions? The FAQ says
we need Java 1.4 or better. Does that mean it has to be 1.4.0 or can
it be 1.4.x
1.4.0
Oooh, glad you asked that
On Wed, 2005-06-08 at 16:51 +1000, David Crossley wrote:
There are two skins of uncertain status: leather-dev and corium.
Are they part of the Views now and we don't need them any more?
They are not listed when we do 'forrest available-skins'.
Actually leather-dev is the default skin for
Validate our use of cocoon:// and cocoon://
---
Key: FOR-529
URL: http://issues.apache.org/jira/browse/FOR-529
Project: Forrest
Type: Task
Reporter: Ross Gardler
Priority: Minor
Tim Williams has highlighted an
On Wed, 2005-06-08 at 09:21 +0100, Ross Gardler wrote:
Nicola Ken Barozzi wrote:
Gregor J. Rothfuss wrote:
...
so initially, people could write documents in lenya, publish them, and
then head over to forrest(bot?) to slurp all these pages in?
My personal view is not to use
Thorsten Scherler wrote:
On Wed, 2005-06-08 at 09:21 +0100, Ross Gardler wrote:
Nicola Ken Barozzi wrote:
...
Aditionally, what we would need is just to add an _edit_ link to each
Forrest page that points to the url Lenya uses for editing.
Currently this is done through filter XSL's (see
On Wed, 2005-06-08 at 10:08 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
On Wed, 2005-06-08 at 09:21 +0100, Ross Gardler wrote:
Nicola Ken Barozzi wrote:
...
Aditionally, what we would need is just to add an _edit_ link to each
Forrest page that points to the url Lenya uses
Thorsten Scherler wrote:
On Wed, 2005-06-08 at 10:08 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
...
:) Yeah, that is simply a contract that contains a link to
daisy/lenya/anyOtherCms edit page. I will make an example as soon I have
updated the locationmap branch on my harddrive
On Wed, 2005-06-08 at 11:11 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
On Wed, 2005-06-08 at 10:08 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
...
:) Yeah, that is simply a contract that contains a link to
daisy/lenya/anyOtherCms edit page. I will make an example
David Crossley wrote:
Nicola Ken Barozzi wrote:
David Crossley wrote:
Ross Gardler wrote:
...
Does this sound OK?
It sounds brilliant.
Indeed!
The part that i like most is that each project
is focussing on their own tools, we are not duplicating, and we are
collaborating.
[
http://issues.apache.org/jira/browse/FOR-527?page=comments#action_12313031 ]
Ross Gardler commented on FOR-527:
--
Actually I noted this when making the previous comment:
Searchbox floats to top in Moz browsers
-
Key: FOR-531
URL: http://issues.apache.org/jira/browse/FOR-531
Project: Forrest
Type: Bug
Components: Skins (general issues)
Versions: 0.7-dev
Environment: Netscape 7.x
I just opened a new issue and had to load the screenshot up by attaching
a gif file (using attach file). When I tried to use the attach
screenshot option, it seemed like it was working (paste screenshot, add
comment, click attach) but after I clicked attach and the page reloaded,
there was no
[ http://issues.apache.org/jira/browse/FOR-531?page=all ]
Addison Berry updated FOR-531:
--
Attachment: searchbox_float.gif
Attached screenshot of what I'm seeing. (attached as gif file because I can't
attach a screenshot for some reason.)
Searchbox
Thanks for fixing some of the docs already, David.
Some questions remaining:
- Set your Java version to be the lowest specified of our supported versions.
e.g. J2SDK 1.4.0
See my ealier posting on this.
- Run 'build release-dist' to generate the distributions on a UNIX machine.
-
Hello! Ross!
Ive tried to locate the Eclipse plug-in, that you mentioned, the alpha one.
But I wasnt able to find it in http links download. Tonight I will checkout
forest from trunk
cause it its expensive to do that in the day time.
But even without it here is some kind of my proposition
On Mon, 2005-06-06 at 20:15 +0200, Ferdinand Soethe wrote:
Comments from trying it:
Thorsten Scherler wrote:
I will write a howto on that I promise! For now try the following
survival guide:
*setup*
1) The first step is to build the view and the viewHelper plugins (that
will be
[ http://issues.apache.org/jira/browse/FOR-528?page=all ]
Work on FOR-528 started by Ross Gardler
Add version control to plugins
--
Key: FOR-528
URL: http://issues.apache.org/jira/browse/FOR-528
Project: Forrest
Type:
Nicola Ken Barozzi wrote:
(cc'd to Lenya Dev for their comments as well - please reply-all)
...
Looking at the Doco document [1] I see that Lenya and Forrest are not
directly interacting, as both talk to a common repository.
Right now, what we have is:
--- committers ---. .
Skin sample donation
Key: FOR-534
URL: http://issues.apache.org/jira/browse/FOR-534
Project: Forrest
Type: Improvement
Components: Other
Versions: 0.6
Reporter: Torsten Stolpmann
Priority: Minor
As discussed on
[ http://issues.apache.org/jira/browse/FOR-534?page=all ]
Torsten Stolpmann updated FOR-534:
--
Attachment: verit-forrest-sample.zip
Skin sample donation
Key: FOR-534
URL:
Ross Gardler wrote:
Torsten Stolpmann wrote:
As Claudia already pointed out, most work done on pelt was rather
destructive (disabling/removing features we didn't need/like/got in
the way) than constructive.
I've often wanted to disable certain features in our skins, but never
found the
Auto Generate plugins.xml entry
---
Key: FOR-532
URL: http://issues.apache.org/jira/browse/FOR-532
Project: Forrest
Type: Improvement
Reporter: Ross Gardler
--
This message is automatically generated by JIRA.
-
If you think it
Thorsten Scherler wrote:
David Crossley wrote:
There are two skins of uncertain status: leather-dev and corium.
Are they part of the Views now and we don't need them any more?
They are not listed when we do 'forrest available-skins'.
Actually leather-dev is the default skin for
I've got resources in resources.xmap looking at locationmap now. I
haven't done it for any non-image resource though.Should the
following matches be resolvable through locationmaps too? I can't
off the top of my head think of any reason why not but thought it
important enough to query.
On Wed, 2005-01-06 at 12:02 +0200, Juan Jose Pablos wrote:
Pedro I. Sanchez wrote:
Anyway, first I verified that setting value=es_ES in
main/webapp/sitemap.xmap indeed works. It brings the Spanish strings
from the right catalogue. I also verified that value=${env.LANG} does
*not* work.
I apologize up front for being a pest while you guys are prepping for
the release but...
I started my queries into sitemaps with the cocoon:/ cocoon://
protocols but now I'm starting to wonder whether we have other sitemap
related issues too. (Not issues in the sense of bugs, but issues in
the
[ http://issues.apache.org/jira/browse/FOR-527?page=all ]
David Crossley closed FOR-527:
--
The project.issues-rss-url in forrest.properties need to refer to apache.org
Tim Williams wrote:
I apologize up front for being a pest while you guys are prepping for
the release but...
No worries. Development continues on. You are not being a pest,
far from it. Thanks anyway for being so considerate.
I started my queries into sitemaps with the cocoon:/ cocoon://
45 matches
Mail list logo
