You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2004/10/12 06:24:04 UTC
[Important] please test the release candidate
Please everybody do that, not just the committers.
We need people to test the release candidate
on your own projects, especially on different
operating systems. Just send a short reply to
this thread that it works for you.
We intend to make the announcement this Friday
2004-10-15 during the European day-time.
So we have approximately 3 days.
Download the release candidate and supporting files:
apache.org /~brondsem/forrest/0.6-rc5/
Compiled with Java 1.3 from SVN r54198
For Windows get *.zip md5sum 33d8de744ce6150aac0c18c85a65e803
For UNIX get *.tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
Get the *.asc and *.md5 that match your chosen download.
If you want to verify the download, then follow:
http://forrest.apache.org/mirrors.cgi#verify
Otherwise just get on with testing.
Here are some hints:
* Ensure that the compressed archive will unpack properly.
* Follow the README.txt and index.html
* Set environment variables.
* Don't worry too much about minor bugs. We are looking
for blockers, such as it will not run. Many known issues
are recorded at our Jira, perhaps you can add more.
* Make a fresh site ...
cd my-new-dir
forrest seed
forrest
forrest run
forrest war ... and try with your Jetty or Tomcat
* Try it on the Forrest core docs ...
cd apache-forrest-0.6
forrest run
* Forrest was already pre-build. Try building it again.
cd apache-forrest-0.6
build
build test
* Try it on your own project, especially if you have
a project sitemap.
--
David Crossley
Re: [Important] please test the release candidate
Posted by Clay Leeds <cl...@medata.com>.
On Oct 13, 2004, at 2:12 PM, Rick Tessner wrote:
> Issues (Minor)
> --------------
> 1. Odd behaviour with Search box on both the seed and Forrest docs.
> This
> happens with the "forrest site", "forrest run" and "forrest war".
>
> To reproduce,
>
> 1. Clear browser cache
> 2. Bring up build/site/index.html. Note position of search
> box. I'm seeing in top right corner, immediately below
> the div.breadtrail.
> 3. Refresh button on browser. Search box moves to immediately
> above the div#publishedStrip. Seen in both Firefox 1.0PR
> and Galeon 1.3.14.
I notice this issue under Mac OS X 10.3.5, Firefox 0.10.1 (aka Firefox
1.0PR... confusing numbering scheme!). I tested with Mozilla 1.8a4, and
notice the same behavior. I don't have to refresh--resizing the window
is enough to 'fix' the problem. In addition, the content area is moved
down below the leftNav column of links.
You can see for yourself how it looks on Firefox[1] and Mozilla[2].
Of course, there's also the annoying problem with the rounded PNG
corners (not to mention the background color for the Forrest logo)
being a slightly different blue than the background-color of the
.header as seen in my Safari screenshot[3]. I understand this problem
also affects all flavors of M$IE.
[1]
http://homepage.mac.com/webmaestro/forrest/forrest-0.6_001.pdf
[2]
http://homepage.mac.com/webmaestro/forrest/forrest-0.6_002.pdf
[3]
http://homepage.mac.com/webmaestro/forrest/forrest-0.6_002.pdf
> 2. publishedStrip colouring
>
> [ I believe this is the same issue identified by Ross G. in
> http://marc.theaimsgroup.com/?l=forrest-dev&m=109741615818940&w=2 ]
>
> This happens under a "forrest site", "forrest run" and "forrest war"
>
> Under the seed site, the publishedStrip element (where the sub-tags
> and published message appear) has the same colour as the unselected
> tabs. This has a bit of a odd look to it.
>
> The Forrest Docs themselves do not have this issue. The selected
> tab,
> publishedStrip and left navigation menu all have the same colour
> giving a sense of "unity".
I didn't notice this.
> Issue (Major or higher)
> -----------------------
>
> None found. :)
I would agree that these are not 'showstoppers' :-) and may just be
quirkiness in the browsers... Which leads me to question if this could
be some sort of quirks mode problem?
> --
> rick@onnadayr.ca
> IT Firefighting and Prevention
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: [Important] please test the release candidate
Posted by Rick Tessner <ri...@onnadayr.ca>.
David Crossley wrote:
> Please everybody do that, not just the committers.
Hi all,
Platform
--------
RC: apache-forrest-0.6.tar.gz (MD5: c1a9ee2e6c604c62933a39234ba8dabe)
OS: Linux (SuSE 9.0)
Java: 1.4.2 (build 1.4.2-b28)
Browsers: Firefox 1.0 PR and Galeon 1.3.14
Servlet Engine: Jetty 4.2.21 (under above OS and java)
Tested
------
1. Forrest Docs
(a) forrest site
(b) forrest run
(c) forrest war
2. Seed Site
(a) forrest site
(b) forrest run
(c) forrest war
Issues (Minor)
--------------
1. Odd behaviour with Search box on both the seed and Forrest docs. This
happens with the "forrest site", "forrest run" and "forrest war".
To reproduce,
1. Clear browser cache
2. Bring up build/site/index.html. Note position of search
box. I'm seeing in top right corner, immediately below
the div.breadtrail.
3. Refresh button on browser. Search box moves to immediately
above the div#publishedStrip. Seen in both Firefox 1.0PR
and Galeon 1.3.14.
2. publishedStrip colouring
[ I believe this is the same issue identified by Ross G. in
http://marc.theaimsgroup.com/?l=forrest-dev&m=109741615818940&w=2 ]
This happens under a "forrest site", "forrest run" and "forrest war"
Under the seed site, the publishedStrip element (where the sub-tags
and published message appear) has the same colour as the unselected
tabs. This has a bit of a odd look to it.
The Forrest Docs themselves do not have this issue. The selected tab,
publishedStrip and left navigation menu all have the same colour
giving a sense of "unity".
Issue (Major or higher)
-----------------------
None found. :)
--
rick@onnadayr.ca
IT Firefighting and Prevention
Re: [Important] please test the release candidate
Posted by Clay Leeds <cl...@medata.com>.
On Oct 12, 2004, at 5:31 PM, David Crossley wrote:
> Clay Leeds wrote:
>> David Crossley wrote:
>>> Download the release candidate and supporting files:
>>> apache.org /~brondsem/forrest/0.6-rc5/
>>>
>>> Compiled with Java 1.3 from SVN r54198
>>> For Windows get *.zip md5sum 33d8de744ce6150aac0c18c85a65e803
>>> For UNIX get *.tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
>>> Get the *.asc and *.md5 that match your chosen download.
>>
>> matches (used the .zip version)
>
> Thanks for doing that testing Clay.
> What operating system and Java version?
Sorry. I should've included that before.
Mac OS X 10.3.5
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-141.3)
Java HotSpot(TM) Client VM (build 1.4.2-38, mixed mode)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: [Important] please test the release candidate
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Download the release candidate and supporting files:
> > apache.org /~brondsem/forrest/0.6-rc5/
> >
> > Compiled with Java 1.3 from SVN r54198
> > For Windows get *.zip md5sum 33d8de744ce6150aac0c18c85a65e803
> > For UNIX get *.tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
> > Get the *.asc and *.md5 that match your chosen download.
>
> matches (used the .zip version)
Thanks for doing that testing Clay.
What operating system and Java version?
--
David Crossley
Re: [Important] please test the release candidate
Posted by Clay Leeds <cl...@medata.com>.
On Oct 11, 2004, at 9:24 PM, David Crossley wrote:
> Download the release candidate and supporting files:
> apache.org /~brondsem/forrest/0.6-rc5/
>
> Compiled with Java 1.3 from SVN r54198
> For Windows get *.zip md5sum 33d8de744ce6150aac0c18c85a65e803
> For UNIX get *.tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
> Get the *.asc and *.md5 that match your chosen download.
matches (used the .zip version)
> If you want to verify the download, then follow:
> http://forrest.apache.org/mirrors.cgi#verify
>
> Otherwise just get on with testing.
>
> Here are some hints:
> * Ensure that the compressed archive will unpack properly.
> * Follow the README.txt and index.html
> * Set environment variables.
> * Don't worry too much about minor bugs. We are looking
> for blockers, such as it will not run. Many known issues
> are recorded at our Jira, perhaps you can add more.
>
> * Make a fresh site ...
> cd my-new-dir
> forrest seed
Works!
> forrest
Works!
> forrest run
Works!
> forrest war ... and try with your Jetty or Tomcat
Didn't check this.
> * Try it on the Forrest core docs ...
> cd apache-forrest-0.6
> forrest run
Works!
> * Forrest was already pre-build. Try building it again.
> cd apache-forrest-0.6
> build
> build test
Didn't test this.
> * Try it on your own project, especially if you have
> a project sitemap.
> --
> David Crossley
Tested with Barcode4J web site. Noticed that <jump/> links don't spawn
a new window (as I'd thought they did). At first I thought that was
only true for /forrest run/, but it appears when using /forrest/ as
well.
NOTE: Could this be related to their old skinconf.xml file? I intend to
update it with the newer version (with the external DTD), but haven't
gotten around to it yet.
BTW on a side note, I've never really played with /forrest run/ before
(I always just do /forrest/)... It's really nifty! I really like the
way I can modify src *.xml file, and see the change immediately! Wow!
I'm impressed. Never again will I wile away waiting for 2-6 minutes for
each minor change... :-)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: [Important] please test the release candidate
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> David Crossley wrote:
>
>>Please everybody do that, not just the committers.
>>
>>We need people to test the release candidate
>>on your own projects, especially on different
>>operating systems. Just send a short reply to
>>this thread that it works for you.
>
Looks good on my JDK1.4, XP an 2000 machines.
Also good on the LTSP version of Redhat 9 with JDK1.4
No problems builing my sites with custom skins and some extensive xmap
customisations.
Ross
Re: [Important] please test the release candidate
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Please everybody do that, not just the committers.
>
> We need people to test the release candidate
> on your own projects, especially on different
> operating systems. Just send a short reply to
> this thread that it works for you.
I tested the UNIX dist, including the war on a full Jetty,
with Java 1.4 on Linux. All run okay.
With java-1.3 the svg generated logos fail both on 'forrest run'
and 'forrest'. I did not try 'forrest war' with 1.3
Pages look okay on oldish Mozilla and Galeon.
The main trouble that i see, is the issue with integrating
with another project's build system. Might deserve 0.6.1
http://marc.theaimsgroup.com/?t=109747836500001
http://issues.cocoondev.org/browse/FOR-145
--
David Crossley