David Crossley wrote:
Addi wrote:
Also, in this patch I "versioned" the ForrestBar extension to version
0.7. I was thinking that we could match the ForrestBar version to the
current version of Forrest. I have two reasons for this thinking: 1) I
have a link in the toolbar that links to Current Docs so the ForrestBar
version number will tell you which version of the Docs it is pointing to
and this would lead to 2) every release of Forrest we should revisit
ForrestBar to update the Docs link but also to verify continuing
compatibility with browsers so we don't let it fall behind again. Does
this seem reasonable?
Yes. We need to add a note to etc/RELEASE_PROCESS.txt
The version number needs to be incremented as part of
the lead-up to release.
I don't know how to ensure that we update it for
each release. Perhaps add an ongoing Jira issue for it.
I can do these later this weekend if noone else has by then.
I am also looking at getting ForrestBar on the
official Mozilla extensions site so that updates will be automatic for
users. Is there any problem with this that I'm not aware of?
I don't know anything about it so cannot say.
Is there a URL that explains what is involved?
Well, I haven't found tons of detailed info. Here is the link from
Mozilla Update - https://addons.mozilla.org/developers/
The basic idea is that you can get an account and upload and maintain an
extension at the Mozilla Update site. Firefox will look for updates to
extensions there, so if we make changes to our extension and then upload
it, users just need to let Firefox update it for them. One thing I am
not sure of, is that your account login is your email address (and this
is where the account confirmation email is sent) so I would need to know
what email we would use if we do it. I'll see if I can get more
substantive info on how it all really works.
I am also continuing to play with it to try and get it to work in
Netscape 8. I tried to put stuff that I thought would be most useful to
us but if something needs to be added, it is really simple to do by
looking at the chrome/content/forrestbarOverlay.xul file (or just ask on
the list and I'll add it).
Thanks for giving it some attention.
Our Zone could be added to the Forrest section.
forrest.zones.apache.org
The Forrest/JIRA link would be better to go via our
http://forrest.apache.org/issues.html
We will gradually enhance this page to lead
them into JIRA and provide ready-to-go searches etc.
The References section is a good idea for
some high-level references. The Cocoon links will
change soon as they re-arrange their documentation.
At some stage the Projects/Browse All CVS
will be removed. All projects will be
migrated to SVN by 2006-01-01
The Projects section could also link to
http://www.apache.org/foundation/projects.html
Will tweak your suggestions this weekend. The projects all listed out
is pretty much the same as it was in the original, just with some
corrected links. If we just have a link to the apache projects page
rather than actually listing them in the bar (which I'm fine with) I
guess it would make sense to get rid of Projects from the bar and just
move that to be a link under Apache.
- Addi
More below ...
Addison Berry (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-180?page=all ]
Addison Berry updated FOR-180:
------------------------------
Attachment: forrestbar.diff
forrestbar.xpi
forrestbar.xml.diff
This new extension will work with Mozilla 1.x and Firefox 0.9 - 1.5 versions.
The .xpi file attached is the one built running the forrestbar target. I'm not
sure how we get the .xpi file that is on the web site - if it is built or just
put on the server in it's final form - so I included it here.
It is manually generated after any occasional
change.
It gets added to our "site-author" tree.
Everything that is generated from there gets
onto the server, e.g. mirrors.cgi and .htaccess
site-author/content/xdocs/tools/forrestbar.xpi
I just updated the website for forrestbar.html
and forrestbar.xpi
-David
