You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Nicola Ken Barozzi <ni...@apache.org> on 2004/08/31 14:14:10 UTC
[STATUS] Things remaining for 0.6
Let's see if we can finalize this:
1 - I'm actively working to finish off copyless, and it will involve a
change in Cocoon, that I've already proposed on that list. It
will make it possible for mounted pipelines to return back to the
parent for processing if no match is found.
Besides being able to use it to make the internals cleaner, it
will make it possible for users to actually inject theit sitemaps
without having to copy over our things, making it much more
resilient.
2 - Should we switch to pelt after a quick check? it would really be
better to not have to switch skin now and then again in 0.7 if
possible.
3 - There are some buds that are to be fixed to make the dist.
4 - I'd postpone the remaining non-critical bugs to 0.7.
5 - I propose that we add two new matches:
- *.html (that acts like *.ihtml, which itself will be deprecated)
This will make it possible for Forrest to skin any site
that does not have validation included, even if not made
explicitly for Forrest
- *.jspwiki
Use this as an extension instead of *.cwiki, as it
specifies the format better. *.cwiki will remain for
backward compat
Comments welcome :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> Nicola Ken Barozzi wrote:
> >
> > Let's see if we can finalize this:
> >
> > 1 - I'm actively working to finish off copyless, and it will involve a
> > change in Cocoon, that I've already proposed on that list. It
> > will make it possible for mounted pipelines to return back to the
> > parent for processing if no match is found.
> > Besides being able to use it to make the internals cleaner, it
> > will make it possible for users to actually inject theit sitemaps
> > without having to copy over our things, making it much more
> > resilient.
>
> Great.
>
> > 2 - Should we switch to pelt after a quick check? it would really be
> > better to not have to switch skin now and then again in 0.7 if
> > possible.
> >
> > 3 - There are some buds that are to be fixed to make the dist.
And the etc/RELEASE_PROCESS.txt needs review and practice.
> > 4 - I'd postpone the remaining non-critical bugs to 0.7.
>
> Yes. I'd much rather have a release with some bugs than let 0.6 stagnate
> for more months.
Exactly. Thanks Nicola Ken, i was close to sending a similar email.
Some bugs are okay to remain in 0.6 - it is still prior to 1.0
so people must expect issues.
> The only bug I see as critical (besides copyless) is FOR-229 (SVG->PNG).
However, that has a workaround listed in a Jira Comment.
Crude fix, but comment-out the SVG document type declaration.
> I'd like to fix the aggregate html/pdf pages but honestly I doubt I'll be
> able to do it soon.
Delay until 0.7
--
David Crossley
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
> Dave Brondsema wrote:
> ...
> >>5 - I propose that we add two new matches:
> >>
> >> - *.html (that acts like *.ihtml, which itself will be deprecated)
> >>
> >> This will make it possible for Forrest to skin any site
> >> that does not have validation included, even if not made
> >> explicitly for Forrest
> >
> > Is this in line with our plan for xhtml2 and namespaces?
>
> It does not collide. The idea is to reserve *.xhtml for any proper
> xhtml, be it 1.1 or 2.
Yes, we discussed this before:
[VOTE] Finalizing html-ihtml-ehtml
http://marc.theaimsgroup.com/?t=108141201100001
> > I think using this extension in the 'xdocs' dir will confuse people.
>
> Ok, but then we have lots of stuff there than are not x(ml)docs.
People are already a bit confused, so a bit more won't hurt :-)
We just need some better documentation and examples.
The "x" in "xdocs" should just be a wild-card.
We should stop calling the "Apache Forrest document" xml format
as "xdoc format".
> > Especially since
> > the [i]html file has to be valid html (correct me if I'm wrong here) and
> > lots of html in the world is invalid.
>
> AFAIK ihtml can also be invalid, there is a tidy call before.
I tested that just now. The ihtml sample in our "seed site"
has stacks of validation issues. The result seems okay.
--
David Crossley
Re: [STATUS] Things remaining for 0.6
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Dave Brondsema wrote:
...
>>5 - I propose that we add two new matches:
>>
>> - *.html (that acts like *.ihtml, which itself will be deprecated)
>>
>> This will make it possible for Forrest to skin any site
>> that does not have validation included, even if not made
>> explicitly for Forrest
>
> Is this in line with our plan for xhtml2 and namespaces?
It does not collide. The idea is to reserve *.xhtml for any proper
xhtml, be it 1.1 or 2.
> I think using this extension in the 'xdocs' dir will confuse people.
Ok, but then we have lots of stuff there than are not x(ml)docs.
> Especially since
> the [i]html file has to be valid html (correct me if I'm wrong here) and
> lots of html in the world is invalid.
AFAIK ihtml can also be invalid, there is a tidy call before.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> Dave Brondsema wrote:
> > Clay Leeds wrote:
> >>
> >> The primary reason I (and the rest of fop-dev) have been eagerly
> >> awaiting 0.6 is for the aggregate site.pdf output. The thought was
> >> that
> >> FOP should have an aggregate PDF of the site. If this is not going to
> >> happen, I really need to get on the ball and (sigh) figure out how to
> >> make the current xml-fop work with 0.5 ... <snip/>
> >>
> >> Another alternative is to somehow generate the PDF using 0.5, and
> >> inserting it RAW into the site? Anyone another idea? Is there anything
> >> I can do to 'help' get aggregate into 0.6 (ahem... short of learning
> >> Java)?
You do not need to know Java to use or develop Forrest.
The various XSLT and the Cocoon Sitemap are the keys.
> > Both 0.5.1 and 0.6-dev have problems with the aggregate site. Your
> > success with either is highly dependent on how you do linking and image
> > references and if you have duplicate names/ids.
>
> OK... So would (gasp) 0.5 work? As I mentioned, I've been waiting for
> the 0.6 release. I have a few ideas for content changes to xml-fop but
> have waited to make any real changes (other than 'emergency' changes
> which involve the use of vi...) until I have BUILD working.
Why wait? The "whole site capability" is really just an added bonus.
Did you see Thorsten's suggestion of using the "Tab PDF" ability:
http://marc.theaimsgroup.com/?l=forrest-dev&m=109397442105647
> > The knowledge required to help get aggregate sites working is: xslt,
> > forrest site.xml and linkrewriting, cocoon sitemaps, how forrest uses
> > cocoon sitemaps. I don't know it all either.. but I sure learn a lot
> > as I
> > try :-). See FOR-147 for the current status of my attempts. FOR-210
> > and
> > FOR-211 are similiar issues.
>
> The prospect of learning is always a benefit! Makes it all worthwhile!
> If you could point to specific places I can look, I might be if help...
> Then again, if you knew where to look, you could probably fix it
> yourself...
The issue is that Dave has said that he doesn't have time.
It would take time to explain more to you. Start with
sitemap.xmap and use find and grep to follow it from there.
--
David Crossley
Re: [STATUS] Things remaining for 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Aug 31, 2004, at 8:29 AM, Dave Brondsema wrote:
> On Tue, 31 Aug 2004, Clay Leeds wrote:
>>> Yes. I'd much rather have a release with some bugs than let 0.6
>>> stagnate
>>> for more months.
>>>
>>> The only bug I see as critical (besides copyless) is FOR-229
>>> (SVG->PNG).
>>> I'd like to fix the aggregate html/pdf pages but honestly I doubt
>>> I'll
>>> be able to do it soon.
>>
>> The primary reason I (and the rest of fop-dev) have been eagerly
>> awaiting 0.6 is for the aggregate site.pdf output. The thought was
>> that
>> FOP should have an aggregate PDF of the site. If this is not going to
>> happen, I really need to get on the ball and (sigh) figure out how to
>> make the current xml-fop work with 0.5 (which has an aggregate
>> function
>> which works). Obviously, I'd rather use 0.6, but if that's not going
>> to
>> happen... I gave up on 0.5 after much frustration some time ago,
>> thinking it would be better to bide my time for 0.6.
>>
>> Another alternative is to somehow generate the PDF using 0.5, and
>> inserting it RAW into the site? Anyone another idea? Is there anything
>> I can do to 'help' get aggregate into 0.6 (ahem... short of learning
>> Java)?
>
> Both 0.5.1 and 0.6-dev have problems with the aggregate site. Your
> success with either is highly dependent on how you do linking and image
> references and if you have duplicate names/ids.
OK... So would (gasp) 0.5 work? As I mentioned, I've been waiting for
the 0.6 release. I have a few ideas for content changes to xml-fop but
have waited to make any real changes (other than 'emergency' changes
which involve the use of vi...) until I have BUILD working.
> The knowledge required to help get aggregate sites working is: xslt,
> forrest site.xml and linkrewriting, cocoon sitemaps, how forrest uses
> cocoon sitemaps. I don't know it all either.. but I sure learn a lot
> as I
> try :-). See FOR-147 for the current status of my attempts. FOR-210
> and
> FOR-211 are similiar issues.
The prospect of learning is always a benefit! Makes it all worthwhile!
If you could point to specific places I can look, I might be if help...
Then again, if you knew where to look, you could probably fix it
yourself...
Web Maestro Clay
Re: [STATUS] Things remaining for 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
On Tue, 31 Aug 2004, Clay Leeds wrote:
> On Aug 31, 2004, at 5:25 AM, Dave Brondsema wrote:
> >> 2 - Should we switch to pelt after a quick check? it would really be
> >> better to not have to switch skin now and then again in 0.7 if
> >> possible.
> >>
> >> 3 - There are some buds that are to be fixed to make the dist.
> >>
> >> 4 - I'd postpone the remaining non-critical bugs to 0.7.
> >
> > Yes. I'd much rather have a release with some bugs than let 0.6
> > stagnate
> > for more months.
> >
> > The only bug I see as critical (besides copyless) is FOR-229
> > (SVG->PNG).
> > I'd like to fix the aggregate html/pdf pages but honestly I doubt I'll
> > be
> > able to do it soon.
>
> The primary reason I (and the rest of fop-dev) have been eagerly
> awaiting 0.6 is for the aggregate site.pdf output. The thought was that
> FOP should have an aggregate PDF of the site. If this is not going to
> happen, I really need to get on the ball and (sigh) figure out how to
> make the current xml-fop work with 0.5 (which has an aggregate function
> which works). Obviously, I'd rather use 0.6, but if that's not going to
> happen... I gave up on 0.5 after much frustration some time ago,
> thinking it would be better to bide my time for 0.6.
>
> Another alternative is to somehow generate the PDF using 0.5, and
> inserting it RAW into the site? Anyone another idea? Is there anything
> I can do to 'help' get aggregate into 0.6 (ahem... short of learning
> Java)?
>
Both 0.5.1 and 0.6-dev have problems with the aggregate site. Your
success with either is highly dependent on how you do linking and image
references and if you have duplicate names/ids.
The knowledge required to help get aggregate sites working is: xslt,
forrest site.xml and linkrewriting, cocoon sitemaps, how forrest uses
cocoon sitemaps. I don't know it all either.. but I sure learn a lot as I
try :-). See FOR-147 for the current status of my attempts. FOR-210 and
FOR-211 are similiar issues.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [STATUS] Things remaining for 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Aug 31, 2004, at 5:25 AM, Dave Brondsema wrote:
>> 2 - Should we switch to pelt after a quick check? it would really be
>> better to not have to switch skin now and then again in 0.7 if
>> possible.
>>
>> 3 - There are some buds that are to be fixed to make the dist.
>>
>> 4 - I'd postpone the remaining non-critical bugs to 0.7.
>
> Yes. I'd much rather have a release with some bugs than let 0.6
> stagnate
> for more months.
>
> The only bug I see as critical (besides copyless) is FOR-229
> (SVG->PNG).
> I'd like to fix the aggregate html/pdf pages but honestly I doubt I'll
> be
> able to do it soon.
The primary reason I (and the rest of fop-dev) have been eagerly
awaiting 0.6 is for the aggregate site.pdf output. The thought was that
FOP should have an aggregate PDF of the site. If this is not going to
happen, I really need to get on the ball and (sigh) figure out how to
make the current xml-fop work with 0.5 (which has an aggregate function
which works). Obviously, I'd rather use 0.6, but if that's not going to
happen... I gave up on 0.5 after much frustration some time ago,
thinking it would be better to bide my time for 0.6.
Another alternative is to somehow generate the PDF using 0.5, and
inserting it RAW into the site? Anyone another idea? Is there anything
I can do to 'help' get aggregate into 0.6 (ahem... short of learning
Java)?
Web Maestro Clay
Re: [STATUS] Things remaining for 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
On Tue, 31 Aug 2004, Nicola Ken Barozzi wrote:
>
> Let's see if we can finalize this:
>
> 1 - I'm actively working to finish off copyless, and it will involve a
> change in Cocoon, that I've already proposed on that list. It
> will make it possible for mounted pipelines to return back to the
> parent for processing if no match is found.
> Besides being able to use it to make the internals cleaner, it
> will make it possible for users to actually inject theit sitemaps
> without having to copy over our things, making it much more
> resilient.
>
Great.
> 2 - Should we switch to pelt after a quick check? it would really be
> better to not have to switch skin now and then again in 0.7 if
> possible.
>
> 3 - There are some buds that are to be fixed to make the dist.
>
> 4 - I'd postpone the remaining non-critical bugs to 0.7.
>
Yes. I'd much rather have a release with some bugs than let 0.6 stagnate
for more months.
The only bug I see as critical (besides copyless) is FOR-229 (SVG->PNG).
I'd like to fix the aggregate html/pdf pages but honestly I doubt I'll be
able to do it soon.
> 5 - I propose that we add two new matches:
>
> - *.html (that acts like *.ihtml, which itself will be deprecated)
>
> This will make it possible for Forrest to skin any site
> that does not have validation included, even if not made
> explicitly for Forrest
>
Is this in line with our plan for xhtml2 and namespaces? I think using
this extension in the 'xdocs' dir will confuse people. Especially since
the [i]html file has to be valid html (correct me if I'm wrong here) and
lots of html in the world is invalid.
> - *.jspwiki
>
> Use this as an extension instead of *.cwiki, as it
> specifies the format better. *.cwiki will remain for
> backward compat
>
Sounds good.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [STATUS] Things remaining for 0.6
Posted by thorsten <th...@apache.org>.
David Crossley wrote:
> Nicola Ken Barozzi wrote:
>
>>2 - Should we switch to pelt after a quick check? it would really be
>> better to not have to switch skin now and then again in 0.7 if
>> possible.
>
>
> So will we leave the "crust" skin in the distribution
> and note that it is going away, or remove it now?
> If the latter then we need to be sure that all of its
> capabilities are implemented in "pelt".
>
There is one thing still missing that I saw last night:
sub-tab support
+ 1 to remove it now when we agree pelt is good enough.
King regards
thorsten
Re: [STATUS] Things remaining for 0.6
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> Nicola Ken Barozzi wrote:
>
>>2 - Should we switch to pelt after a quick check? it would really be
>> better to not have to switch skin now and then again in 0.7 if
>> possible.
>
> So will we leave the "crust" skin in the distribution
> and note that it is going away, or remove it now?
Good question.
The only major difference between the crust skin and a complete pelt
should basically be only the internals (table or div driven).
In some moments I really feel that it's time to get rid of the
table-based design and just use pelt... tigris can be used for a table
based design if users want that.
Note that this would even mean that we _remove_ the crust skin from the
distro and just ship pelt.
> If the latter then we need to be sure that all of its
> capabilities are implemented in "pelt".
Yes, we can do so only if this is the case.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
>
> 2 - Should we switch to pelt after a quick check? it would really be
> better to not have to switch skin now and then again in 0.7 if
> possible.
So will we leave the "crust" skin in the distribution
and note that it is going away, or remove it now?
If the latter then we need to be sure that all of its
capabilities are implemented in "pelt".
--
David Crossley
Re: [Proposal] Release plan for 0.6
Posted by David Crossley <cr...@apache.org>.
If people can identify existing patches that we have
missed, then i will apply them this evening (away today).
Then we go into code freeze.
I see some recent obvious ones from Sean which can go in.
For others, please add a comment to each Jira issue
that you want to apply its patch. That will send the
reminder to forrest-dev.
--
David Crossley
Re: [Proposal] Release plan for 0.6
Posted by Antonio Gallardo <ag...@agssa.net>.
David Crossley dijo:
> Antonio Gallardo wrote:
>> David Crossley dijo:
>> > So here is the start of a plan. Please refine.
>>
>> +1
>
> Antonio, you are an expert at upgrading jars.
lol. ;-)
> Would you be able to upgrade our Xalan.
> At Forrest we decided that we don't need to
> wait for official releases. We have the nasty
> Xalan bug with the bad document type declaration.
> http://issues.cocoondev.org/browse/FOR-238
Yep. I will try to do that. I am also checking the problem with
commons-jxpath 1.2
Best Regards,
Antonio Gallardo
Re: [Proposal] Release plan for 0.6
Posted by David Crossley <cr...@apache.org>.
Antonio Gallardo wrote:
> David Crossley dijo:
> > So here is the start of a plan. Please refine.
>
> +1
Antonio, you are an expert at upgrading jars.
Would you be able to upgrade our Xalan.
At Forrest we decided that we don't need to
wait for official releases. We have the nasty
Xalan bug with the bad document type declaration.
http://issues.cocoondev.org/browse/FOR-238
--
David Crossley
Re: [Proposal] Release plan for 0.6
Posted by Antonio Gallardo <ag...@agssa.net>.
David Crossley dijo:
> So here is the start of a plan. Please refine.
>
> 2004-10-08
> Code freeze. Specify an SVN revision number to work with.
> Still can change any documentation.
> Send the Vote email (Apache Forrest PMC needs to approve).
> Testing period lasts for 7 days.
>
> 2004-10-14
> The Vote finishes today. Start preparing the release.
> Total freeze. Tag. Branch.
>
> 2004-10-15
> Release. Send announcement email when mirrors are up-to-date.
+1
Best Regards,
Antonio Gallardo
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Quoting Nicola Ken Barozzi <ni...@apache.org>:
> David Crossley wrote:
> > Please test the release candidate.
>
> +1 to
>
+1
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Quoting Nicola Ken Barozzi <ni...@apache.org>:
> David Crossley wrote:
> > Were we supposed to do the "Tag and Branch" of SVN
> > before we created the release candidate or after?
>
> Branch before IMHO and tag if the vote is ok (IOW copy to the branches
> subdir first and after move to the tags subdir).
>
> This way development on the main branch can continue; the only ting to
> take care is to patch both the branch and the trunk in case of bugs that
> have surfanced in the RC.
>
I agree. Although since it takes a few tries to get the RC right, I'd suggest
branching about now, rather than after the first RC.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> > Were we supposed to do the "Tag and Branch" of SVN
> > before we created the release candidate or after?
>
> Branch before IMHO and tag if the vote is ok (IOW copy to the branches
> subdir first and after move to the tags subdir).
>
> This way development on the main branch can continue; the only ting to
> take care is to patch both the branch and the trunk in case of bugs that
> have surfanced in the RC.
Ah thanks, you answered both parts of my question.
* How to let development continue while the vote is happening.
* When to tag.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> Were we supposed to do the "Tag and Branch" of SVN
> before we created the release candidate or after?
Branch before IMHO and tag if the vote is ok (IOW copy to the branches
subdir first and after move to the tags subdir).
This way development on the main branch can continue; the only ting to
take care is to patch both the branch and the trunk in case of bugs that
have surfanced in the RC.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Were we supposed to do the "Tag and Branch" of SVN
before we created the release candidate or after?
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> Please test the release candidate.
+1 to
http://cvs.apache.org/~brondsem/forrest/0.6-rc5/apache-forrest-0.6.zip
MD5(apache-forrest-0.6.zip)= 33d8de744ce6150aac0c18c85a65e803
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
>
> Don't we need to change the versions in a few places (according to
> etc/RELEASE_PROCESS.txt) and commit those before we build?
I did that locally but didn't commit. I was confused by
this and thought that i should do as you now confirm.
Our release process notes need amendment.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> David Crossley escribió:
> > Juan Jose Pablos wrote:
> >
> >>+1
> >>I have signed both files, could you verify that both asc files are good?
> >
> > Your *.asc cannot be downloaded because you have made them
> > readable only by you.
>
> Sorry, it is the default configuration on the server.
It sounds like you have not configured your workspace
properly. You need to set the 'umask'. Look at the
~/.cshrc for various people.
Anyway, yes, i just verified your *.asc and they are fine.
While i was logged in, i combined your *.asc with the others.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Juan Jose Pablos <ch...@apache.org>.
David Crossley escribió:
> Juan Jose Pablos wrote:
>
>>+1
>>I have signed both files, could you verify that both asc files are good?
>
>
> Your *.asc cannot be downloaded because you have made them
> readable only by you.
Sorry, it is the default configuration on the server.
You need to ssh to the server
> cd ~brondsem/public_html/forrest/0.6-rc5
> chmod 664 cheche*.asc
> chgrp forrest cheche*.asc
>
chmod g+rw cheche-apache-forrest-0.6.* did the trick
> Also what is the purpose of the *.sig file that you
> have placed there?
>
I was using the pgp command, and I made a mistake with the options, I
have alredy deleted it.
Thanks
Cheche
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> >
> +1
> I have signed both files, could you verify that both asc files are good?
Your *.asc cannot be downloaded because you have made them
readable only by you. You need to ssh to the server
cd ~brondsem/public_html/forrest/0.6-rc5
chmod 664 cheche*.asc
chgrp forrest cheche*.asc
Also what is the purpose of the *.sig file that you
have placed there?
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Juan Jose Pablos <ch...@apache.org>.
>
> If you're a PMC member with a key in KEYS and you vote +1, please sign
> both files (e.g., gpg --detach-sig --armor apache-forrest-0.6.zip) and
> reply with the .asc files attached.
>
+1
I have signed both files, could you verify that both asc files are good?
Cheers,
Cheche
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> David Crossley wrote:
> >
> > I can verify your .asc signature for the *.tar.gz
> > However, not for the *.zip
>
> I fixed mine; yours are good.
Okay, i just cat our keys together on the server
then downloaded the combined *.asc and verified again.
So should we remove the individual *.asc now?
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Oct 12, 2004, at 5:41 PM, David Crossley wrote:
> Clay Leeds wrote:
>> I got it to work. It looks like the version of ant
>> I have installed (1.6.0) was causing problems.
>
> This is a worry. What was the symptom?
I think it gave some kind of error to the effect of:
/Users/Shared/_WebDLs/_repos/apache-forest-0.6/src/core/bin/../tools/ant
I forget what exactly, but it had a 'relative "go up from here"'
somewhere in the path...
>> Also...
>>
>>> David Crossley wrote:
>>>> Why? The user instructions make it very clear how to
>>>> set $FORREST_HOME.
>>
>> There are two places where it indicates how to set FORREST_HOME (and
>> they both do it differently):
>>
>> [1]
>> http://forrest.apache.org/build.html#building
>>
>> [2]
>> http://forrest.apache.org/docs/your-project.html#installing
>>
>> It's entirely possible (and maybe even logical ;-)) that both should
>> be
>> retained, but it is a little confusing.
>
> Argh, how did we miss that. The second one is wrong.
> If people start with forrest/README.txt and forrest/index.html
> then we should be safe.
>
> Lots of changes mounting up for when the code freeze ends.
>
> --
> David Crossley
Glad I could find it. I remembered seeing both ways, but forgot for a
while... Glad I could help!
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: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> I got it to work. It looks like the version of ant
> I have installed (1.6.0) was causing problems.
This is a worry. What was the symptom?
> Also...
>
> > David Crossley wrote:
> >> Why? The user instructions make it very clear how to
> >> set $FORREST_HOME.
>
> There are two places where it indicates how to set FORREST_HOME (and
> they both do it differently):
>
> [1]
> http://forrest.apache.org/build.html#building
>
> [2]
> http://forrest.apache.org/docs/your-project.html#installing
>
> It's entirely possible (and maybe even logical ;-)) that both should be
> retained, but it is a little confusing.
Argh, how did we miss that. The second one is wrong.
If people start with forrest/README.txt and forrest/index.html
then we should be safe.
Lots of changes mounting up for when the code freeze ends.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Oct 13, 2004, at 5:42 AM, Dave Brondsema wrote:
> Clay Leeds wrote:
>> I got it to work. It looks like the version of ant I have installed
>> (1.6.0) was causing problems.
>
> That's not good.. forrest is supposed to use it's own version of ant
> and not care what else is installed on the system.
I've got 'Fink' installed (a package manager for Mac OS X), and it
decided to install /sw/lib/ant, and set it as ANT_HOME. It sets it
after my ~/.bashrc is called (which sets
ANT_HOME=/path/to/my/ant_1.6.2-bin/). In order to get /forrest/ to
work, I have to
%set ANT_HOME=/path/to/my/ant_1.6.2-bin/
%export ANT_HOME
%forrest
I discovered where fink appears to override and I'm thinking of fixing
the ANT_HOME problem, but I haven't done that yet.
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: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Clay Leeds wrote:
> I got it to work. It looks like the version of ant I have installed
> (1.6.0) was causing problems.
>
That's not good.. forrest is supposed to use it's own version of ant and
not care what else is installed on the system.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
I got it to work. It looks like the version of ant I have installed
(1.6.0) was causing problems.
Also...
On Oct 12, 2004, at 9:06 AM, Clay Leeds wrote:
> On Oct 11, 2004, at 5:11 PM, David Crossley wrote:
>> Dave Brondsema wrote:
<snip>
>>> FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
>>>
>>> (It'd be handy if in the future the shell scripts were smart enough
>>> to
>>> accept either)
>>
>> Why? The user instructions make it very clear how to
>> set $FORREST_HOME.
There are two places where it indicates how to set FORREST_HOME (and
they both do it differently):
[1]
http://forrest.apache.org/build.html#building
[2]
http://forrest.apache.org/docs/your-project.html#installing
It's entirely possible (and maybe even logical ;-)) that both should be
retained, but it is a little confusing.
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: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Oct 11, 2004, at 5:11 PM, David Crossley wrote:
> Dave Brondsema wrote:
>> Clay Leeds wrote:
>>> Some important details:
>>>
>>> (from ~/.bashrc)
>>> FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6
>>
>> FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
>>
>> (It'd be handy if in the future the shell scripts were smart enough to
>> accept either)
>
> Why? The user instructions make it very clear how to
> set $FORREST_HOME.
I guess I should be a little more clear, and also clarify a couple of
other items.
Before I wrote my previous message, I'd already tried (as could be seen
commented out in my follow-up[1]):
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core/
bin
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/build
(I also tried a few others before posting, thinking I was just doing
something silly...). To quote one or two famous people: "Nothing
works!"
I don't recall where it indicates the following as the most appropriate:
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
...but it's not on this page[2]
>>> (btw, should I even be 'helping' with testing? ;-))
>>
>> Yes, please!
>
> Another, Yes, please! We need everybody to help with
> testing on different operating systems.
>
> --
> David Crossley
Glad I could 'help' ;-)
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=14413
[2]
http://forrest.apache.org/docs/your-project.html#installing
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 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
[Important] please test the release candidate
Posted by David Crossley <cr...@apache.org>.
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: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
To clarify our release plan from the Proposal thread ...
> 2004-10-08
> Code freeze. Tag. Branch. Upload the dists to a user space dir.
> Send the Vote email (Apache Forrest PMC needs to approve).
> Testing+voting period lasts for 7 days.
>
> 2004-10-14
> The Vote finishes today. Upload the dists.
> Release. Send announcement email when mirrors are up-to-date.
So the testing/vote finishes at midnight UTC on 2004-10-14.
I will then continue with the release during our morning.
The web pages are ready in my SVN working copy.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Oct 11, 2004, at 5:16 PM, Dave Brondsema wrote:
> David Crossley wrote:
>> Dave Brondsema wrote:
>>> FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
>>>
>>> (It'd be handy if in the future the shell scripts were smart enough
>>> to accept either)
>> Why? The user instructions make it very clear how to
>> set $FORREST_HOME.
>
> So we can be more like a "normal" application, where _HOME is the base
> directory. Thinking about it more now, the bin/ directory has to be
> in PATH and it would still be in src/core, so users would still have
> to set that properly.
I would concur with Dave. I like the idea of following a 'standard'
even if it's a de facto one. IMO, _HOME should be the top-level of the
app dir, and bin/ should be beneath that. In addition, if one is
build'g the app from source, I guess the build/ dir should also be in
the PATH.
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: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Dave Brondsema wrote:
>
>>Clay Leeds wrote:
>>
>>
>>>Some important details:
>>>
>>>(from ~/.bashrc)
>>>FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6
>>
>>FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
>>
>>(It'd be handy if in the future the shell scripts were smart enough to
>>accept either)
>
>
> Why? The user instructions make it very clear how to
> set $FORREST_HOME.
>
So we can be more like a "normal" application, where _HOME is the base
directory. Thinking about it more now, the bin/ directory has to be in
PATH and it would still be in src/core, so users would still have to set
that properly.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Important] please test the release candidate
Posted by David Crossley <cr...@apache.org>.
Stephen Schaub wrote:
>
> Looks good on my JDK1.4.2 and JDK 1.5.0, XP machine.
> Built a site without difficulty.
Thanks for testing Stephen. That is good news, especially the JDK 1.5
--
David Crossley
Re: [Important] please test the release candidate
Posted by Stephen Schaub <ss...@bju.edu>.
> 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.2 and JDK 1.5.0, XP machine. Built a site without
difficulty.
Stephen
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> Clay Leeds wrote:
>
> > Some important details:
> >
> > (from ~/.bashrc)
> > FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6
>
> FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
>
> (It'd be handy if in the future the shell scripts were smart enough to
> accept either)
Why? The user instructions make it very clear how to
set $FORREST_HOME.
> > (btw, should I even be 'helping' with testing? ;-))
>
> Yes, please!
Another, Yes, please! We need everybody to help with
testing on different operating systems.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Clay Leeds wrote:
> On Oct 11, 2004, at 4:24 PM, Dave Brondsema wrote:
>
>> David Crossley wrote:
>>
>>> Dave Brondsema wrote:
>>>
>>>> apache.org /~brondsem/forrest/0.6-rc5/
>>>>
>>>> Compiled with 1.3
>>>>
>>>> .zip md5sum 33d8de744ce6150aac0c18c85a65e803
>>>> .tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
>>>
>>> I have verified your md5sums ... both okay.
>>> My *.asc are now scp to /~brondsem/forrest/0.6-rc5/
>>> I can verify your .asc signature for the *.tar.gz
>>> However, not for the *.zip
>>
>>
>> I fixed mine; yours are good.
>
>
> I tried downloading and running both 0.6-rc5 files (0.6.tar.gz &
> 0.6.zip) onto my system, and I'm not getting very far. No matter what I
> try, I get problems like:
> ===
> [clay@Clay-Computer myProj]$ forrest
> Apache Forrest. Run 'forrest -projecthelp' to list options
>
> /Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core/bin/forrest:
> line 95:
> /Users/Shared/_WebDLs/_repos/apache-forrest-0.6/../../tools/ant/bin/
> ant: No such file or directory
> ===
>
> Some important details:
>
> (from ~/.bashrc)
> FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core
(It'd be handy if in the future the shell scripts were smart enough to
accept either)
> PATH=$PATH:$FORREST_HOME/bin:$ANT_HOME/bin:$FOP_HOME/build:$FOP_HOME/lib
> export CLASSPATH JAVA_HOME CVSROOT FORREST_HOME FOP_HOME ANT_HOME
> CVS_RSH='ssh'
>
> [clay@Clay-Computer myProj]$ java -version
> 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)
>
> (btw, should I even be 'helping' with testing? ;-))
>
Yes, please!
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
For completeness sake, here's the rest of my ~/.bashrc:
CLASSPATH=$CLASSPATH:/Users/Shared/_WebDLs/fop-0.20.5/lib:/Users/
Shared/_WebDLs/fop-0.20.5/bin:/Users/Shared/_WebDLs/javamake:/Users/
Shared/_WebDLs/_repos/barcode4j/build/barcode4j.jar:/Users/Shared/
_WebDLs/_repos/barcode4j/build/barcode4j-fop-ext-post-0.20.5.jar:/
Users/Shared/_WebDLs/_repos/junit3.8.1/junit.jar
JAVA_HOME=/Library/Java/Home
CVSROOT=/Users/Shared/_WebDLs/_repos/
ANT_HOME=/Users/Shared/_WebDLs/_repos/apache-ant-1.6.2_bin
#FORREST_HOME=/Users/Shared/_WebDLs/apache-forrest-0.5.1-bin
#FORREST_HOME=/Users/Shared/_WebDLs/cvs_stuff/forrest/src/core
#FORREST_HOME=/Users/Shared/_WebDLs/_repos/forrest/src/core
#FORREST_HOME=/Users/Shared/_WebDLs/_repos/forrest/build
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6
FOP_HOME=/Users/Shared/_WebDLs/fop-0.20.5
PATH=$PATH:$FORREST_HOME/bin:$ANT_HOME/bin:$FOP_HOME/build:$FOP_HOME/lib
export CLASSPATH JAVA_HOME CVSROOT FORREST_HOME FOP_HOME ANT_HOME
CVS_RSH='ssh'
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: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Oct 11, 2004, at 4:24 PM, Dave Brondsema wrote:
> David Crossley wrote:
>> Dave Brondsema wrote:
>>> apache.org /~brondsem/forrest/0.6-rc5/
>>>
>>> Compiled with 1.3
>>>
>>> .zip md5sum 33d8de744ce6150aac0c18c85a65e803
>>> .tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
>> I have verified your md5sums ... both okay.
>> My *.asc are now scp to /~brondsem/forrest/0.6-rc5/
>> I can verify your .asc signature for the *.tar.gz
>> However, not for the *.zip
>
> I fixed mine; yours are good.
I tried downloading and running both 0.6-rc5 files (0.6.tar.gz &
0.6.zip) onto my system, and I'm not getting very far. No matter what I
try, I get problems like:
===
[clay@Clay-Computer myProj]$ forrest
Apache Forrest. Run 'forrest -projecthelp' to list options
/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core/bin/forrest:
line 95:
/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/../../tools/ant/bin/
ant: No such file or directory
===
Some important details:
(from ~/.bashrc)
FORREST_HOME=/Users/Shared/_WebDLs/_repos/apache-forrest-0.6
PATH=$PATH:$FORREST_HOME/bin:$ANT_HOME/bin:$FOP_HOME/build:$FOP_HOME/lib
export CLASSPATH JAVA_HOME CVSROOT FORREST_HOME FOP_HOME ANT_HOME
CVS_RSH='ssh'
[clay@Clay-Computer myProj]$ java -version
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)
(btw, should I even be 'helping' with testing? ;-))
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: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Dave Brondsema wrote:
>
>>apache.org /~brondsem/forrest/0.6-rc5/
>>
>>Compiled with 1.3
>>
>>.zip md5sum 33d8de744ce6150aac0c18c85a65e803
>>.tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
>
>
> I have verified your md5sums ... both okay.
>
> My *.asc are now scp to /~brondsem/forrest/0.6-rc5/
>
> I can verify your .asc signature for the *.tar.gz
> However, not for the *.zip
>
I fixed mine; yours are good.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
>
> apache.org /~brondsem/forrest/0.6-rc5/
>
> Compiled with 1.3
>
> .zip md5sum 33d8de744ce6150aac0c18c85a65e803
> .tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
I have verified your md5sums ... both okay.
My *.asc are now scp to /~brondsem/forrest/0.6-rc5/
I can verify your .asc signature for the *.tar.gz
However, not for the *.zip
--
David Crossley
Re: [Announce] Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> Thanks for coordinating all of this, David.
I need a holiday now. It was a big effort.
Thanks for your help and that of others.
Next time should be easier.
> You forgot http://www.apache.org/dist/forrest/apache-forrest-0.6.tar.gz.asc, so
> I just copied it there now.
Yikes, i wonder how i missed that. Thanks for checking.
> It should be okay for me to delete my RC files now, right?
Now that you have ensured everything is present, yes.
--
David Crossley
Re: [Announce] Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Thanks for coordinating all of this, David.
You forgot http://www.apache.org/dist/forrest/apache-forrest-0.6.tar.gz.asc, so
I just copied it there now.
It should be okay for me to delete my RC files now, right?
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [Announce] Apache Forrest 0.6
Posted by Vincent Bray <v....@cobwebinfo.com>.
Congratulations and thanks :-)
noodl
On Fri, 2004-10-15 at 13:40, David Crossley wrote:
> Apache Forrest is pleased to release the new version: apache-forrest-0.6
> http://forrest.apache.org/mirrors.cgi
>
> Apache Forrest is an XML standards-oriented documentation framework
> based upon Apache Cocoon, providing XSLT stylesheets and schemas,
> images and other resources. Forrest uses these to render the source
> content into a website via command-line, robot, or dynamic application.
> http://forrest.apache.org/
>
> New features in this version include:
>
> * Uses all resources in-place. No more copying to a separate
> build space and so no need to back-copy your changes.
> * This provides workflow and productivity improvements.
> * Project sitemaps get first chance processing, then pass-through
> to core sitemaps. This simplifies management of project sitemaps.
> * Project sitemaps provide easy access to the power of Apache Cocoon.
> * New skins use CSS rather than tables. Old skins are deprecated.
> * Skins are configurable, e.g. with colours and optional features.
> * DTD improvements, especially addition of ubiquitous class attribute.
> * Forrestbot, robotic build and deploy, has been entirely re-written.
>
> Full list of changes: http://forrest.apache.org/changes.html
>
> Upgrade guide: http://forrest.apache.org/docs/upgrading_06.html
>
> Thanks for your interest, from the Apache Forrest community.
>
Re: [Announce] Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
On Oct 15, 2004, at 5:40 AM, David Crossley wrote:
> Apache Forrest is pleased to release the new version:
> apache-forrest-0.6
> http://forrest.apache.org/mirrors.cgi
<snip>
> Thanks for your interest, from the Apache Forrest community.
Congratulations and thanks! Great work!
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>
[Announce] Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Apache Forrest is pleased to release the new version: apache-forrest-0.6
http://forrest.apache.org/mirrors.cgi
Apache Forrest is an XML standards-oriented documentation framework
based upon Apache Cocoon, providing XSLT stylesheets and schemas,
images and other resources. Forrest uses these to render the source
content into a website via command-line, robot, or dynamic application.
http://forrest.apache.org/
New features in this version include:
* Uses all resources in-place. No more copying to a separate
build space and so no need to back-copy your changes.
* This provides workflow and productivity improvements.
* Project sitemaps get first chance processing, then pass-through
to core sitemaps. This simplifies management of project sitemaps.
* Project sitemaps provide easy access to the power of Apache Cocoon.
* New skins use CSS rather than tables. Old skins are deprecated.
* Skins are configurable, e.g. with colours and optional features.
* DTD improvements, especially addition of ubiquitous class attribute.
* Forrestbot, robotic build and deploy, has been entirely re-written.
Full list of changes: http://forrest.apache.org/changes.html
Upgrade guide: http://forrest.apache.org/docs/upgrading_06.html
Thanks for your interest, from the Apache Forrest community.
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
thorsten wrote:
> Nice.
>
> Sorry for not being a big help here.
>
> Good work everyone. :)
Well that is why we are a team. You guys helped in other areas.
Did you or Antonio mange to get PGP keys signed at the
Cocoon GetTogether? If so then it would be a big help
if you could sign the *.tar.gz and *.zip releases.
Put your *.asc signature files at your apache space
and i will verify them and append them.
This can be done at any time. There are three of us signed
so far, but the more the better. We a starting to form
a Forrest cluster at http://www.apache.org/~henkp/trust/apache.html
Hopefully our Cocoon connection will draw us into the mass.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by thorsten <th...@apache.org>.
David Crossley wrote:
> Okay, testing and vote has finished, with no negative votes.
>
> So doing the upload now. We need to wait about 12 hours
> before doing the announcement.
>
Nice.
Sorry for not being a big help here.
Good work everyone. :)
thorsten
[Announce] Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Apache Forrest is pleased to release the new version: apache-forrest-0.6
http://forrest.apache.org/mirrors.cgi
Apache Forrest is an XML standards-oriented documentation framework
based upon Apache Cocoon, providing XSLT stylesheets and schemas,
images and other resources. Forrest uses these to render the source
content into a website via command-line, robot, or dynamic application.
http://forrest.apache.org/
New features in this version include:
* Uses all resources in-place. No more copying to a separate
build space and so no need to back-copy your changes.
* This provides workflow and productivity improvements.
* Project sitemaps get first chance processing, then pass-through
to core sitemaps. This simplifies management of project sitemaps.
* Project sitemaps provide easy access to the power of Apache Cocoon.
* New skins use CSS rather than tables. Old skins are deprecated.
* Skins are configurable, e.g. with colours and optional features.
* DTD improvements, especially addition of ubiquitous class attribute.
* Forrestbot, robotic build and deploy, has been entirely re-written.
Full list of changes: http://forrest.apache.org/changes.html
Upgrade guide: http://forrest.apache.org/docs/upgrading_06.html
Thanks for your interest, from the Apache Forrest community.
[Announce] Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Apache Forrest is pleased to release the new version: apache-forrest-0.6
http://forrest.apache.org/mirrors.cgi
Apache Forrest is an XML standards-oriented documentation framework
based upon Apache Cocoon, providing XSLT stylesheets and schemas,
images and other resources. Forrest uses these to render the source
content into a website via command-line, robot, or dynamic application.
http://forrest.apache.org/
New features in this version include:
* Uses all resources in-place. No more copying to a separate
build space and so no need to back-copy your changes.
* This provides workflow and productivity improvements.
* Project sitemaps get first chance processing, then pass-through
to core sitemaps. This simplifies management of project sitemaps.
* Project sitemaps provide easy access to the power of Apache Cocoon.
* New skins use CSS rather than tables. Old skins are deprecated.
* Skins are configurable, e.g. with colours and optional features.
* DTD improvements, especially addition of ubiquitous class attribute.
* Forrestbot, robotic build and deploy, has been entirely re-written.
Full list of changes: http://forrest.apache.org/changes.html
Upgrade guide: http://forrest.apache.org/docs/upgrading_06.html
Thanks for your interest, from the Apache Forrest community.
[Announce] Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Apache Forrest is pleased to release the new version: apache-forrest-0.6
http://forrest.apache.org/mirrors.cgi
Apache Forrest is an XML standards-oriented documentation framework
based upon Apache Cocoon, providing XSLT stylesheets and schemas,
images and other resources. Forrest uses these to render the source
content into a website via command-line, robot, or dynamic application.
http://forrest.apache.org/
New features in this version include:
* Uses all resources in-place. No more copying to a separate
build space and so no need to back-copy your changes.
* This provides workflow and productivity improvements.
* Project sitemaps get first chance processing, then pass-through
to core sitemaps. This simplifies management of project sitemaps.
* Project sitemaps provide easy access to the power of Apache Cocoon.
* New skins use CSS rather than tables. Old skins are deprecated.
* Skins are configurable, e.g. with colours and optional features.
* DTD improvements, especially addition of ubiquitous class attribute.
* Forrestbot, robotic build and deploy, has been entirely re-written.
Full list of changes: http://forrest.apache.org/changes.html
Upgrade guide: http://forrest.apache.org/docs/upgrading_06.html
Thanks for your interest, from the Apache Forrest community.
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Okay, testing and vote has finished, with no negative votes.
So doing the upload now. We need to wait about 12 hours
before doing the announcement.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
>
> apache.org /~brondsem/forrest/0.6-rc5/
>
> tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
+1 from me for this release.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> David Crossley wrote:
> >
> > http://issues.cocoondev.org/browse/FOR-235
> > "Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3"
> > ... at least for me on Linux. Do others have this too?
> >
> > Our options:
> > A) Ignore it and tell 1.3 people to grapple with ps and kill.
> >
> > B) Raise our minimum Java level to 1.4 and tweak the docs.
>
> This doesn't seem to be a big issue. ps/kill and upgrading to java 1.4+
> are two decent workarounds,
I agree. However, there will be no FAQ about it in
their local docs, because we have already built the
release candidate. Never mind, we can add an FAQ after
the release and direct their questions to the website FAQ.
(That will tell us how many customers still use java 1.3 :-)
> and we can release a 0.6.1 if we figure out
> a better solution.
>
> my forrest/0.6-rc5/ is group-writable now
Thanks, i will upload my *.asc
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Dave Brondsema wrote:
>
>>apache.org /~brondsem/forrest/0.6-rc5/
>>
>>Compiled with 1.3
>>
>>.zip md5sum 33d8de744ce6150aac0c18c85a65e803
>>.tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
>
>
> Ouch ... the sound of me being bitten by a bug.
>
> http://issues.cocoondev.org/browse/FOR-235
> "Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3"
> ... at least for me on Linux. Do others have this too?
>
> Our options:
> A) Ignore it and tell 1.3 people to grapple with ps and kill.
>
> B) Raise our minimum Java level to 1.4 and tweak the docs.
>
> C) Try to find the reason for this. Is it our packaged Jetty config?
>
> However this does not prevent people from testing the current
> release candidate. Has anyone tried the "build war" on various
> servlet containers?
>
This doesn't seem to be a big issue. ps/kill and upgrading to java 1.4+
are two decent workarounds, and we can release a 0.6.1 if we figure out
a better solution.
my forrest/0.6-rc5/ is group-writable now
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> David Crossley said:
>
>>David Crossley wrote:
>>
>>>http://issues.cocoondev.org/browse/FOR-235
>>>"Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3"
>>>... at least for me on Linux. Do others have this too?
>>>
>>>Our options:
>>>A) Ignore it and tell 1.3 people to grapple with 'ps' and 'kill -9'.
>>>
>>>B) Raise our minimum Java level to 1.4 and tweak the docs.
>>>
>>>C) Try to find the reason for this. Is it our packaged Jetty config?
>>
>>I grepped the Internet and found a message from our Pier
>>about something similar:
>>
>>"Note, shutdown hooks don't get triggered on JDK-1.3
>>when CTRL-C is pressed on the console"
>>http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108972345629182
>>
>>So we can forget option C).
>>
>
>
> (pulling out the ol' 'lower requirements benefits most users unless
> there's a specific need' trumpet)
>
> I'd 'vote' for option A).
For the Eclipse plugin I need to change the way we are starting Forrest
as I need to be able to cleanly shutdown Jetty from an Eclipse action. I
am experimenting with different options at the moment, but how does this
sound for a fix in 0.6.1:
"forrest run" - starts the server using the jetty start.jar
"forrest stop" - stops the server using the jetty stop.jar
Ross
Re: [Vote] Release Apache Forrest 0.6
Posted by Clay Leeds <cl...@medata.com>.
David Crossley said:
> David Crossley wrote:
>> http://issues.cocoondev.org/browse/FOR-235
>> "Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3"
>> ... at least for me on Linux. Do others have this too?
>>
>> Our options:
>> A) Ignore it and tell 1.3 people to grapple with 'ps' and 'kill -9'.
>>
>> B) Raise our minimum Java level to 1.4 and tweak the docs.
>>
>> C) Try to find the reason for this. Is it our packaged Jetty config?
>
> I grepped the Internet and found a message from our Pier
> about something similar:
>
> "Note, shutdown hooks don't get triggered on JDK-1.3
> when CTRL-C is pressed on the console"
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108972345629182
>
> So we can forget option C).
>
> Note that Cocoon's 'cocoon.sh servlet' has the same issue.
>
> --
> David Crossley
(pulling out the ol' 'lower requirements benefits most users unless
there's a specific need' trumpet)
I'd 'vote' for option A).
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> http://issues.cocoondev.org/browse/FOR-235
> "Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3"
> ... at least for me on Linux. Do others have this too?
>
> Our options:
> A) Ignore it and tell 1.3 people to grapple with 'ps' and 'kill -9'.
>
> B) Raise our minimum Java level to 1.4 and tweak the docs.
>
> C) Try to find the reason for this. Is it our packaged Jetty config?
I grepped the Internet and found a message from our Pier
about something similar:
"Note, shutdown hooks don't get triggered on JDK-1.3
when CTRL-C is pressed on the console"
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108972345629182
So we can forget option C).
Note that Cocoon's 'cocoon.sh servlet' has the same issue.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
>
> apache.org /~brondsem/forrest/0.6-rc5/
>
> Compiled with 1.3
>
> .zip md5sum 33d8de744ce6150aac0c18c85a65e803
> .tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
Ouch ... the sound of me being bitten by a bug.
http://issues.cocoondev.org/browse/FOR-235
"Cannot use Ctrl-C to shutdown demo forrest run with jdk1.3"
... at least for me on Linux. Do others have this too?
Our options:
A) Ignore it and tell 1.3 people to grapple with ps and kill.
B) Raise our minimum Java level to 1.4 and tweak the docs.
C) Try to find the reason for this. Is it our packaged Jetty config?
However this does not prevent people from testing the current
release candidate. Has anyone tried the "build war" on various
servlet containers?
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> Dave Brondsema wrote:
> > David Crossley wrote:
> >> in your release candidate, but has proper UNIX line-endings for me.
> >> src/forrestbot/webapp/src/java/org/apache/forrest/forrestbot/webapp/util/Project.java
> >>
> >> It does have svn:eol-style=native so i don't know why the difference.
> >> I presume that is what causes a difference in xml-forrest.jar.
> >>
> >> Anyway does that matter?
> >
> > Shouldn't matter... I'll look into it.
>
> Fixed.
Do you have any idea how it happened. It seems a very strange glitch.
> apache.org /~brondsem/forrest/0.6-rc5/
>
> Compiled with 1.3
>
> .zip md5sum 33d8de744ce6150aac0c18c85a65e803
> .tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
Please make your forrest/0.6-rc5/ group writable
so that i can add my *.asc
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Dave Brondsema wrote:
> David Crossley wrote:
>> in your release candidate, but has proper UNIX line-endings for me.
>> src/forrestbot/webapp/src/java/org/apache/forrest/forrestbot/webapp/util/Project.java
>>
>> It does have svn:eol-style=native so i don't know why the difference.
>> I presume that is what causes a difference in xml-forrest.jar.
>>
>> Anyway does that matter?
>
> Shouldn't matter... I'll look into it.
>
Fixed.
>>
>> I downloaded and verified your tar package. Your *.asc
>> and *.md5 are fine for me.
>>
>> I notice that your xml-forrest.jar is built with Java 1.4
>> Is that correct? Isn't it meant to be 1.3 ?
>>
>
> I forgot about that... I guess I'll have to do it again...
>
apache.org /~brondsem/forrest/0.6-rc5/
Compiled with 1.3
.zip md5sum 33d8de744ce6150aac0c18c85a65e803
.tar.gz md5sum c1a9ee2e6c604c62933a39234ba8dabe
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Dave Brondsema wrote:
>
>>When extracting the .tar.gz. I get "tar: A lone zero block at 67904" but
>>everything works fine.
>
>
> A bit worrisome.
>
> I recall reading about that or something similar on Google.
> It said using recent versions of tar to unpack, the tar
> files that are created by Ant cause that message.
> Evidently it is "just a warning" and all is well.
>
> I don't get any messages with "tar (GNU tar) 1.13.25"
> and all seems well.
>
>
>>That directory is forrest-writable, so add your .asc files there.
>
>
> Okay, added mine.
>
> Then i did 'build release-dist' here on r54198
>
> I get a different md5sum. A bit of investigation
> revealed the reasons. The following file has DOS line-endings
> in your release candidate, but has proper UNIX line-endings for me.
> src/forrestbot/webapp/src/java/org/apache/forrest/forrestbot/webapp/util/Project.java
> It does have svn:eol-style=native so i don't know why the difference.
> I presume that is what causes a difference in xml-forrest.jar.
>
> Anyway does that matter?
Shouldn't matter... I'll look into it.
>
> I downloaded and verified your tar package. Your *.asc
> and *.md5 are fine for me.
>
> I notice that your xml-forrest.jar is built with Java 1.4
> Is that correct? Isn't it meant to be 1.3 ?
>
I forgot about that... I guess I'll have to do it again...
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
>
> When extracting the .tar.gz. I get "tar: A lone zero block at 67904" but
> everything works fine.
A bit worrisome.
I recall reading about that or something similar on Google.
It said using recent versions of tar to unpack, the tar
files that are created by Ant cause that message.
Evidently it is "just a warning" and all is well.
I don't get any messages with "tar (GNU tar) 1.13.25"
and all seems well.
> That directory is forrest-writable, so add your .asc files there.
Okay, added mine.
Then i did 'build release-dist' here on r54198
I get a different md5sum. A bit of investigation
revealed the reasons. The following file has DOS line-endings
in your release candidate, but has proper UNIX line-endings for me.
src/forrestbot/webapp/src/java/org/apache/forrest/forrestbot/webapp/util/Project.java
It does have svn:eol-style=native so i don't know why the difference.
I presume that is what causes a difference in xml-forrest.jar.
Anyway does that matter?
I downloaded and verified your tar package. Your *.asc
and *.md5 are fine for me.
I notice that your xml-forrest.jar is built with Java 1.4
Is that correct? Isn't it meant to be 1.3 ?
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Dave Brondsema wrote:
> David Crossley wrote:
>
>> Dave Brondsema wrote:
>>
>>> David Crossley wrote:
>>>
>>>> If so, then we will make these the official files
>>>> for testing and voting. (I just removed mine.)
>>
>>
>>
>> Then Dave's candidates are the ones.
>>
>
> Crap. The .zip has the "etc" duplicated. I need to change build.xml so
> I will produce both versions again.
>
Let's try this again....
r54198
apache.org /~brondsem/forrest/0.6-rc4
.tar.gz md5sum: 8d738cd98a14fb5774221b3ef2f28222
.zip md5sum: e9de045bd548f3010a123eafe295be63
When extracting the .tar.gz. I get "tar: A lone zero block at 67904" but
everything works fine.
That directory is forrest-writable, so add your .asc files there.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> David Crossley wrote:
> > Then Dave's candidates are the ones.
>
> Crap. The .zip has the "etc" duplicated.
> I need to change build.xml so
> I will produce both versions again.
:-) twice for me, twice for you.
It is good that we allow once week to test and refine.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Dave Brondsema wrote:
>
>>David Crossley wrote:
>>>If so, then we will make these the official files
>>>for testing and voting. (I just removed mine.)
>
>
> Then Dave's candidates are the ones.
>
Crap. The .zip has the "etc" duplicated. I need to change build.xml so
I will produce both versions again.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> David Crossley wrote:
> > Dave Brondsema wrote:
> >>.tar.gz m5sum b54f5ebf00f883b1106f919306ead91b
> >>.zip md5sum 4d9f5eb87036248b1a62fbb6038ebc8d
> >
> > Is the tar archive built on UNIX and the zip on Win?
>
> Yes.
Great, i did think so but it needed to be stated.
> > If so, then we will make these the official files
> > for testing and voting. (I just removed mine.)
Then Dave's candidates are the ones.
> >>If you want to build it yourself locally, use the md5sum to verify that
> >>it's exactly the same (run 'svn st --no-ignore' to make sure you have a
> >>clean source tree).
> >
> > Our etc/RELEASE_PROCESS.txt says to checkout a new working copy.
> >
> > We would prefer that people test the actual release tar and zip
> > that we are voting about.
>
> I was just thinking people might want to save the bandwith, but 20mb
> isn't too bad. Downloading is definitely the safest too.
The process that you suggested is still needed for someone
else to repeat the process and compare the md5 sums i suppose.
I will do that later today.
> >>If you're a PMC member with a key in KEYS and you vote +1, please sign
> >>both files (e.g., gpg --detach-sig --armor apache-forrest-0.6.zip) and
> >>reply with the .asc files attached.
> >
> > Yes. However, i am not sure what you mean by the last part.
> > Attached to the email?
> >
> > I want to add my *.asc early in the week. Then i will vote
> > toward the very end of the week when i am satisfied.
>
> I'm not sure what the best process is here. Somehow the "releasor"
> needs to get all the .asc signatures and concatenate them,
> and put that file alongside the release.
We do have a "dist" repository where i have been putting
the html templates that enable the www.apache.org distribution
area at /dist/forrest/ to be adorned. It would be best to append
our *.asc there. At the moment that is not an 'svn co' on the server.
They are manually put there with 'scp'.
If your ~brondsem/forrest/ directory is writable by
our forrest group, then we can just update your *.asc
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Dave Brondsema wrote:
>
>>I updated the forrest version number and rebuilt the releases (from r54181).
>>
>>Windows & linux dists are at http://apache.org/~brondsem/forrest/
>
>
> (Aside: I tried not to expose my URL to Google like that.
> Dunno if it is a problem or not.)
>
>
>>.tar.gz m5sum b54f5ebf00f883b1106f919306ead91b
>>.zip md5sum 4d9f5eb87036248b1a62fbb6038ebc8d
>
>
> Is the tar archive built on UNIX and the zip on Win?
>
Yes.
> If so, then we will make these the official files
> for testing and voting. (I just removed mine.)
>
>
>>If you want to build it yourself locally, use the md5sum to verify that
>>it's exactly the same (run 'svn st --no-ignore' to make sure you have a
>>clean source tree).
>
>
> Our etc/RELEASE_PROCESS.txt says to checkout a new working copy.
>
> We would prefer that people test the actual release tar and zip
> that we are voting about.
>
I was just thinking people might want to save the bandwith, but 20mb
isn't too bad. Downloading is definitely the safest too.
>
>>If you're a PMC member with a key in KEYS and you vote +1, please sign
>>both files (e.g., gpg --detach-sig --armor apache-forrest-0.6.zip) and
>>reply with the .asc files attached.
>
>
> Yes. However, i am not sure what you mean by the last part.
> Attached to the email?
>
> I want to add my *.asc early in the week. Then i will vote
> toward the very end of the week when i am satisfied.
>
I'm not sure what the best process is here. Somehow the "releasor"
needs to get all the .asc signatures and concatenate them, and put that
file alongside the release.
> Thanks for rebuilding stuff. This is a good process.
>
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
>
> I updated the forrest version number and rebuilt the releases (from r54181).
>
> Windows & linux dists are at http://apache.org/~brondsem/forrest/
(Aside: I tried not to expose my URL to Google like that.
Dunno if it is a problem or not.)
> .tar.gz m5sum b54f5ebf00f883b1106f919306ead91b
> .zip md5sum 4d9f5eb87036248b1a62fbb6038ebc8d
Is the tar archive built on UNIX and the zip on Win?
If so, then we will make these the official files
for testing and voting. (I just removed mine.)
> If you want to build it yourself locally, use the md5sum to verify that
> it's exactly the same (run 'svn st --no-ignore' to make sure you have a
> clean source tree).
Our etc/RELEASE_PROCESS.txt says to checkout a new working copy.
We would prefer that people test the actual release tar and zip
that we are voting about.
> If you're a PMC member with a key in KEYS and you vote +1, please sign
> both files (e.g., gpg --detach-sig --armor apache-forrest-0.6.zip) and
> reply with the .asc files attached.
Yes. However, i am not sure what you mean by the last part.
Attached to the email?
I want to add my *.asc early in the week. Then i will vote
toward the very end of the week when i am satisfied.
Thanks for rebuilding stuff. This is a good process.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> Sorry, I inadvertently left the old md5 checksums in the copied mail. I
> checked against rc4, but I see there is an rc5 now. Still the issues
> with pelt will still be present.
There are other issues too, that we have deliberately overlooked
in order to get the release out. Issues will need to be major
to halt the release. Please add those new issues to the issue tracker.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Ross Gardler wrote:
>
>>Dave Brondsema wrote:
>>
>>>Dave Brondsema wrote:
>>>
>>>
>>>>Don't we need to change the versions in a few places (according to
>>>>etc/RELEASE_PROCESS.txt) and commit those before we build?
>>>>
>>>>
>>>>>The testing and vote period concludes on 2004-10-15.
>>>>>Anyone can test and vote, not just PMC members.
>>>>>However the PMC votes are binding.
>>>
>>>I updated the forrest version number and rebuilt the releases (from
>>>r54181).
>>>
>>>Windows & linux dists are at http://apache.org/~brondsem/forrest/
>>>
>>>.tar.gz m5sum b54f5ebf00f883b1106f919306ead91b
>>>.zip md5sum 4d9f5eb87036248b1a62fbb6038ebc8d
>>
>>I verified the windows zip running under both cygwin and dos.
>
>
> Great, thanks for the report. However that is the wrong version
> for testing. See the subsequent messages in this thread.
> It is essentially the same, but we all need to be voting on the
> identical release candidate.
>
Sorry, I inadvertently left the old md5 checksums in the copied mail. I
checked against rc4, but I see there is an rc5 now. Still the issues
with pelt will still be present.
Ross
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> Dave Brondsema wrote:
> > Dave Brondsema wrote:
> >
> >> Don't we need to change the versions in a few places (according to
> >> etc/RELEASE_PROCESS.txt) and commit those before we build?
> >>
> >>> The testing and vote period concludes on 2004-10-15.
> >>> Anyone can test and vote, not just PMC members.
> >>> However the PMC votes are binding.
> >
> > I updated the forrest version number and rebuilt the releases (from
> > r54181).
> >
> > Windows & linux dists are at http://apache.org/~brondsem/forrest/
> >
> > .tar.gz m5sum b54f5ebf00f883b1106f919306ead91b
> > .zip md5sum 4d9f5eb87036248b1a62fbb6038ebc8d
>
> I verified the windows zip running under both cygwin and dos.
Great, thanks for the report. However that is the wrong version
for testing. See the subsequent messages in this thread.
It is essentially the same, but we all need to be voting on the
identical release candidate.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Ross Gardler <rg...@apache.org>.
Dave Brondsema wrote:
> Dave Brondsema wrote:
>
>> Don't we need to change the versions in a few places (according to
>> etc/RELEASE_PROCESS.txt) and commit those before we build?
>>
>>> The testing and vote period concludes on 2004-10-15.
>>> Anyone can test and vote, not just PMC members.
>>> However the PMC votes are binding.
>>>
>
> I updated the forrest version number and rebuilt the releases (from
> r54181).
>
> Windows & linux dists are at http://apache.org/~brondsem/forrest/
>
> .tar.gz m5sum b54f5ebf00f883b1106f919306ead91b
> .zip md5sum 4d9f5eb87036248b1a62fbb6038ebc8d
I verified the windows zip running under both cygwin and dos. Following
tasks worked just fine:
forrest seed
forrest run
forrest site
forrest run (on existing project using custom skin and lots of xmap
overrides)
forrest site (on existing project using same custom skin)
I did notice a few minor problems with PELT on the seed site though
(same behaviour in both Firefox 0.10.1 and IE 6):
When no sub tabs are used there is a large gap between the tab and the
the left naivgation menu. This removes the connection between the tab
and navigation, to my eye this doesn't look right (could be personal
though).
When there is a second level of tabs they are both selected, and again,
there is a separation beteen the tabs and the nav menu.
I also tested the tar.gz on LTSP version of RedHat 9. Same environment
as above, same results.
Ross
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Dave Brondsema wrote:
> Don't we need to change the versions in a few places (according to
> etc/RELEASE_PROCESS.txt) and commit those before we build?
>
>
>>The testing and vote period concludes on 2004-10-15.
>>Anyone can test and vote, not just PMC members.
>>However the PMC votes are binding.
>>
I updated the forrest version number and rebuilt the releases (from r54181).
Windows & linux dists are at http://apache.org/~brondsem/forrest/
.tar.gz m5sum b54f5ebf00f883b1106f919306ead91b
.zip md5sum 4d9f5eb87036248b1a62fbb6038ebc8d
If you want to build it yourself locally, use the md5sum to verify that
it's exactly the same (run 'svn st --no-ignore' to make sure you have a
clean source tree).
If you're a PMC member with a key in KEYS and you vote +1, please sign
both files (e.g., gpg --detach-sig --armor apache-forrest-0.6.zip) and
reply with the .asc files attached.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Vote] Release Apache Forrest 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
Quoting David Crossley <cr...@apache.org>:
> Please test the release candidate RC2.
> It is at http://www.apache.org/ in my home directory
> ~crossley/forrest-06/
>
> Built from SVN revision 54161.
>
> Note: This is the UNIX version. Would somebody else
> please build the *.zip version for Windows, so as to
> have the proper line endings for text files.
>
Yes I will do this.
Don't we need to change the versions in a few places (according to
etc/RELEASE_PROCESS.txt) and commit those before we build?
> The testing and vote period concludes on 2004-10-15.
> Anyone can test and vote, not just PMC members.
> However the PMC votes are binding.
>
> --
> David Crossley
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Please test the release candidate RC2.
It is at http://www.apache.org/ in my home directory
~crossley/forrest-06/
Built from SVN revision 54161.
Note: This is the UNIX version. Would somebody else
please build the *.zip version for Windows, so as to
have the proper line endings for text files.
The testing and vote period concludes on 2004-10-15.
Anyone can test and vote, not just PMC members.
However the PMC votes are binding.
--
David Crossley
Re: [Vote] Release Apache Forrest 0.6
Posted by Antonio Gallardo <ag...@agssa.net>.
David Crossley dijo:
> David Crossley wrote:
> This delay will also give Antonio some more time to upgrade
> the Xalan jar.
I already builded xalan and committed xalan. Please cross check. :-D
Best Regards,
Antonio Gallardo
Re: [Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Please test the release candidate.
Well that was a practice run. There is a minor bug
which appears like a blocker. It presents as "build failed"
which is not a good look. As we all know, that only means
that a page or a link has failed.
The link called "site:dtd-docs" or "ext:dtd-docs" has
mysterious failure. Using a different name "site:foo-bar"
still fails.
I will look for a workaround, such as a hard-coded link
rather that using site.xml
This delay will also give Antonio some more time to upgrade
the Xalan jar.
Another release candidate will be uploaded soon.
--
David Crossley
[Vote] Release Apache Forrest 0.6
Posted by David Crossley <cr...@apache.org>.
Please test the release candidate.
It is at http://www.apache.org/ in my home directory
~crossley/forrest-06/
Built from SVN revision 54147.
Note: This is the UNIX version. Would somebody else
please build the *.zip version for Windows, so as to
have the proper line endings for text files.
The testing and vote period concludes on 2004-10-15.
Anyone can test and vote, not just PMC members.
However the PMC votes are binding.
--
David Crossley
Re: [Proposal] Release plan for 0.6
Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
>
> IMO we must test and vote on the actual zips and tars. Cocoon has
> already has problems because the actual files were not what others were
> testing.
The trouble with this approach is that we cannot add
and tweak documentation over that week. I suppose that
that is not so bad. We can do it, but the changes will not
be in the release, just be on the website.
> I'd do:
>
> 2004-10-08
> Code freeze. Tag. Branch. Upload the dists to a user space dir.
> Send the Vote email (Apache Forrest PMC needs to approve).
> Testing+voting period lasts for 7 days.
>
> 2004-10-14
> The Vote finishes today. Upload the dists.
> Release. Send announcement email when mirrors are up-to-date.
Okay that is better. I will prepare the release tomorrow
morning our time (about 10 hours away). The actual release
is on 2004-10-15.
--
David Crossley
Re: [Proposal] Release plan for 0.6
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
...
> So here is the start of a plan. Please refine.
>
> 2004-10-08
> Code freeze. Specify an SVN revision number to work with.
> Still can change any documentation.
> Send the Vote email (Apache Forrest PMC needs to approve).
> Testing period lasts for 7 days.
>
> 2004-10-14
> The Vote finishes today. Start preparing the release.
> Total freeze. Tag. Branch.
>
> 2004-10-15
> Release. Send announcement email when mirrors are up-to-date.
IMO we must test and vote on the actual zips and tars. Cocoon has
already has problems because the actual files were not what others were
testing.
I'd do:
2004-10-08
Code freeze. Tag. Branch. Upload the dists to a user space dir.
Send the Vote email (Apache Forrest PMC needs to approve).
Testing+voting period lasts for 7 days.
2004-10-14
The Vote finishes today. Upload the dists.
Release. Send announcement email when mirrors are up-to-date.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [Proposal] Release plan for 0.6
Posted by Ross Gardler <rg...@apache.org>.
Dave Brondsema wrote:
> David Crossley wrote:
> Things work fine now, let's stay as-is. We can make a 0.6.1 release
> with a new cocoon version if necessary.
+1, 0.6 needs to get out the door.
> Or, if we each make one, we should compare md5sums to make sure that
> we're dealing with exactly the same stuff. This actually is probably
> better so we don't have to upload & download the whole thing.
+1 from a bandwidth point of view
>> So here is the start of a plan. Please refine.
All sounds great to me.
Ross
Re: [Proposal] Release plan for 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> David Crossley wrote:
<snip/>
>
> > * How should we test the release tarballs? Each person
> > can do 'build dist' on their own machine and make sure
> > that it unpacks correctly and then test. For example
> > the *.zip on my machine reports problems.
>
> We should all test from the same .zip and .tar.gz files. E.g. I
> generate the .zip on my windows box and upload it somewhere and have
> everyone test that. Then that one would be the one we use for the release.
>
> Or, if we each make one, we should compare md5sums to make sure that
> we're dealing with exactly the same stuff. This actually is probably
> better so we don't have to upload & download the whole thing.
The latter sounds like the way to go. I am reluctant to
place the re-releases into our committer Apache webspace
and ask devs to download from there to test.
<snip/>
>
> Each dev should sign the .tar.gz and .zip files. Concatenate all the
> signatures together into the .asc files used in the release.
Okay.
--
David Crossley
Re: [Proposal] Release plan for 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Well the current trunk is looking good, so it
> it is time to get ready for release. Let us develop
> a simple release plan. We already have the procedure
> well-documented at etc/RELEASE_PROCESS.txt
>
> Some items for discussion ...
>
> * We do not need to have separate "binary" and "source"
> because 'build dist' packages all the source and adds the
> 'xml-forrest.jar'. So the release tarballs would be
> called apache-forrest-0.6.tar.gz and apache-forrest-0.6.zip
>
+1
A mention of this in readme.txt or index.html would be good.
> * The version of Cocoon-2.2 that we have in our current
> trunk is working fine. We could wait until after the
> Cocoon GetTogether because they will fix stacks of
> things at the Hackathon. However, it is my view that
> this could delay our release as we would need to do
> more testing at Forrest.
>
Things work fine now, let's stay as-is. We can make a 0.6.1 release
with a new cocoon version if necessary.
> * We discussed a few months ago that we do not need
> to go through the process of "release candidates"
> -RC1 -RC2 etc. We can always make a 0.6.1 release.
>
yep
> * How should we test the release tarballs? Each person
> can do 'build dist' on their own machine and make sure
> that it unpacks correctly and then test. For example
> the *.zip on my machine reports problems.
We should all test from the same .zip and .tar.gz files. E.g. I
generate the .zip on my windows box and upload it somewhere and have
everyone test that. Then that one would be the one we use for the release.
Or, if we each make one, we should compare md5sums to make sure that
we're dealing with exactly the same stuff. This actually is probably
better so we don't have to upload & download the whole thing.
>
> ----0----
> So here is the start of a plan. Please refine.
>
> 2004-10-08
> Code freeze. Specify an SVN revision number to work with.
> Still can change any documentation.
> Send the Vote email (Apache Forrest PMC needs to approve).
> Testing period lasts for 7 days.
>
> 2004-10-14
> The Vote finishes today. Start preparing the release.
> Total freeze. Tag. Branch.
>
Each dev should sign the .tar.gz and .zip files. Concatenate all the
signatures together into the .asc files used in the release.
> 2004-10-15
> Release. Send announcement email when mirrors are up-to-date.
>
Sounds good.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [Proposal] Release plan for 0.6
Posted by David Crossley <cr...@apache.org>.
Well the current trunk is looking good, so it
it is time to get ready for release. Let us develop
a simple release plan. We already have the procedure
well-documented at etc/RELEASE_PROCESS.txt
Some items for discussion ...
* We do not need to have separate "binary" and "source"
because 'build dist' packages all the source and adds the
'xml-forrest.jar'. So the release tarballs would be
called apache-forrest-0.6.tar.gz and apache-forrest-0.6.zip
* The version of Cocoon-2.2 that we have in our current
trunk is working fine. We could wait until after the
Cocoon GetTogether because they will fix stacks of
things at the Hackathon. However, it is my view that
this could delay our release as we would need to do
more testing at Forrest.
* We discussed a few months ago that we do not need
to go through the process of "release candidates"
-RC1 -RC2 etc. We can always make a 0.6.1 release.
* How should we test the release tarballs? Each person
can do 'build dist' on their own machine and make sure
that it unpacks correctly and then test. For example
the *.zip on my machine reports problems.
----0----
So here is the start of a plan. Please refine.
2004-10-08
Code freeze. Specify an SVN revision number to work with.
Still can change any documentation.
Send the Vote email (Apache Forrest PMC needs to approve).
Testing period lasts for 7 days.
2004-10-14
The Vote finishes today. Start preparing the release.
Total freeze. Tag. Branch.
2004-10-15
Release. Send announcement email when mirrors are up-to-date.
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> David Crossley wrote:
> >
> > Would other PMC members please add their PGP keys to "KEYS".
> > We only have one active member at the moment - not sufficient.
>
> I'll add mine soon.
Great ;-)
> Another thing to do is make sure all the docs are in order. I think
> we're pretty good but there are some FIXMEs in etc/docs-review.txt
Yeah, needs a bit more tweaking - almost good enough.
> and I
> think we need some complete documentation on skins because it is very
> frequently asked about by newcomers.
That would not be absolutely necessary for 0.6 release.
It can follow on, because the website is generated from
the trunk.
> It should include:
> * screenshots
> * color changes via CSS
> * how to make a small customization to a skin
> ** html changes
> ** CSS changes
> * why not to write your own skin (better to make it configurable)
> * how to write your own skin if you really really want to
The last two points we are always emphasising, and i for one
want to keep them at the top of the list. Perhaps an FAQ.
http://forrest.apache.org/docs/your-project.html#new_skin
needs tweaks to be in line with that.
--
David Crossley
Re: [STATUS] Things remaining for 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> David Crossley wrote:
>
>>According to http://forrest.apache.org/forrest-issues.html
>>we are ready for release. Yes we know that there are other
>>issues, but it seems that none block us from release.
>>
>>The next tasks are ...
>>
>>* Update some libraries, e.g. Xalan and Cocoon blocks and Ant.
>
>
> Antonio has done a few other libraries, thanks.
> Still more to do.
>
>
>>* Decide if we will go with the unreleased Cocoon-2.2
>>or wait and try to fix Cocoon-2.1.X branch.
>>
>>* Practise the release procedure etc/RELEASE_PROCESS.txt
>
>
> I have done it a few times and refined the notes. Looking good.
>
> Would other PMC members please add their PGP keys to "KEYS".
> We only have one active member at the moment - not sufficient.
>
I'll add mine soon.
Another thing to do is make sure all the docs are in order. I think
we're pretty good but there are some FIXMEs in etc/docs-review.txt and I
think we need some complete documentation on skins because it is very
frequently asked about by newcomers. It should include:
* screenshots
* color changes via CSS
* how to make a small customization to a skin
** html changes
** CSS changes
* why not to write your own skin (better to make it configurable)
* how to write your own skin if you really really want to
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> According to http://forrest.apache.org/forrest-issues.html
> we are ready for release. Yes we know that there are other
> issues, but it seems that none block us from release.
>
> The next tasks are ...
>
> * Update some libraries, e.g. Xalan and Cocoon blocks and Ant.
Antonio has done a few other libraries, thanks.
Still more to do.
> * Decide if we will go with the unreleased Cocoon-2.2
> or wait and try to fix Cocoon-2.1.X branch.
>
> * Practise the release procedure etc/RELEASE_PROCESS.txt
I have done it a few times and refined the notes. Looking good.
Would other PMC members please add their PGP keys to "KEYS".
We only have one active member at the moment - not sufficient.
--David
> * Freeze everything.
>
> * Test the actual distributions on various platforms.
>
> * Prepare the release notes.
>
> * Vote on the release.
>
> * Do it.
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
According to http://forrest.apache.org/forrest-issues.html
we are ready for release. Yes we know that there are other
issues, but it seems that none block us from release.
The next tasks are ...
* Update some libraries, e.g. Xalan and Cocoon blocks and Ant.
* Decide if we will go with the unreleased Cocoon-2.2
or wait and try to fix Cocoon-2.1.X branch.
* Practise the release procedure etc/RELEASE_PROCESS.txt
* Freeze everything.
* Test the actual distributions on various platforms.
* Prepare the release notes.
* Vote on the release.
* Do it.
--
David Crossley
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> > I see two other important issues:
> >
> > ----
> > 6 - FOR-255 catalog entity-resolver fails and gets skinconf DTD from
> > website when using document()
> >
> > We can comment-out the document type declaration as a workaround.
>
> And remove validation? Cheche would not be happy about it 8-)
I am not happy either. I have been trying to reduce the use
of that XSLT document() function, but still got some way to go.
Really the DTD does not do much validation anyway, as everything
is optional. The only benefit that i see is that the DTD enables
some editors to give hints about what other elements can be added.
This is just a workaround to get the release out.
It would not be good to have users complain because they
need network access just to run Forrest locally. Also not
a good look for us (supposed xml experts) to hammer the
Apache website for a DTD.
> > ----
> > 7 - FOR-198 local stylesheets for a user project not found
> >
> > There was a workaround, but it might contravene "copyless".
>
> This should be fixed contextually with copyless, as the user project
> extensions are currently under redevelopment with a new Cocoon pipeline
> mount feature.
Good to hear. I thought that they were separate issues.
--
David Crossley
Re: [STATUS] Things remaining for 0.6
Posted by Dave Brondsema <da...@brondsema.net>.
On Wed, 1 Sep 2004, Nicola Ken Barozzi wrote:
> David Crossley wrote:
> > I see two other important issues:
> >
> > ----
> > 6 - FOR-255 catalog entity-resolver fails and gets skinconf DTD from
> > website when using document()
> >
> > We can comment-out the document type declaration as a workaround.
>
> And remove validation? Cheche would not be happy about it 8-)
>
On the topic of validation, FOR-254 should be addressed before 0.6
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [STATUS] Things remaining for 0.6
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> I see two other important issues:
>
> ----
> 6 - FOR-255 catalog entity-resolver fails and gets skinconf DTD from
> website when using document()
>
> We can comment-out the document type declaration as a workaround.
And remove validation? Cheche would not be happy about it 8-)
> ----
> 7 - FOR-198 local stylesheets for a user project not found
>
> There was a workaround, but it might contravene "copyless".
This should be fixed contextually with copyless, as the user project
extensions are currently under redevelopment with a new Cocoon pipeline
mount feature.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [STATUS] Things remaining for 0.6
Posted by David Crossley <cr...@apache.org>.
I see two other important issues:
----
6 - FOR-255 catalog entity-resolver fails and gets skinconf DTD from
website when using document()
We can comment-out the document type declaration as a workaround.
----
7 - FOR-198 local stylesheets for a user project not found
There was a workaround, but it might contravene "copyless".
--
David Crossley