On Thu, 2005-06-30 at 14:15 +1000, David Crossley wrote:
I have done the next step in setting up some services on our zone.
There is now a forrestbot running there to build the current seed site.
Just the cron side of forrestbot for the moment. The forrestbot web interface
is the next thing
David Crossley wrote:
Ross Gardler wrote:
Just before the release of 0.7 Forrest and Lenya agreed to collaborate
on Doco. It was suggested that we create a joint list for collaboration
(or a virtual list).
I'm not familiar with the processes for getting a list set up can
someone point me in
David Crossley wrote:
David Crossley wrote:
So i am going to remove activation.jar now and create an FAQ.
Okay that is done. Anil would you please check my instructions.
I did not follow them.
The document is started at:
site-author/content/xdocs/tools/eclipse.xml
Thanks David.
This
Update Plugins howto
Key: FOR-562
URL: http://issues.apache.org/jira/browse/FOR-562
Project: Forrest
Type: Improvement
Versions: 0.7
Reporter: Ross Gardler
Fix For: 0.7
The document at
Ross Gardler wrote:
Anil has sent me a revised schedule based on the feedback in this
thread, he has tried to prioritise things for the community. Anil
could you post it here to see if everyone agrees. We want to ensure
that we put initial effort into what is important for the community.
Anil Ramnanan wrote:
How do I go about submitting patches when they include new files and
packages ?
The process of submitting is the same, but the process of generating the
patch is slightly different (you probably know most of this, but I get
round to the point eventually - honest ;-)
Ross Gardler wrote:
Thanks David.
This makes the whole update site thing worthless because we will not
be able to distribute from the Forrest site.
Would it be acceptable to make the Forrest Eclipse Update site come
from another location? I'm not sure what the legal implications of
this
Now that the release is done, would people please speak up
if they see a patch sitting in our Jira Issue Tracker.
I cannot see any way to get Jira to show only those open issues
that have attachments. So we need the dev community to browse
and find them.
In future perhaps we should rename any
Now to the road-map I see for views and the lm-branch:
1) Fix all issues with the lm in the lm-branch (there are just minor
ones that I am aware of)
2) merge all lm related stuff with trunk (branch-trunk)
3) merge all view changes into whiteboard trunk (branch-trunk) That
step is and should
