> > (Henner:) > > Would you like to build the build.xml? > > > I can extend the ant tasks you have started to build a zip > file contining the new stuff as well as the sources etc. that > were always within dbforms release. Then you all might > complete this stuff.
That's nice!!!! > > > Would like to see the web page within the packages: > > > > dbforms-devel_20021104/doc/ > > > Yes, good idea to have the web pages available offline. As > you also suggested, we can put the pages within cvs. Maybe we should > rearrange the stuff within docs directory as you suggested: > one devgui, one taglib dir. Then it would not be neccessary > to change directory structure for a release file. > > However, I would not put everything into cvs or release that > is on the website: > > 1) big files like the new PDF userguide would blow up the release Right, do not blow up the CVS. The userguide should be in the release file and be avaible seperately on SF. > 2) I would like to suggest a 'contributed' area on the website for > contributions not needed by anyone or for extensions that will > be brought into the release, but are not yet. It might also be > a possibility to offer something the community does not > agree about. Could SF manage that? > 3) Wesite can be used to offer intermediate files to be reviewed > by the community. As an example, Shawn can (and will) put > preview releases > of the new manual there. > > Cvs does not forget, that is ok for a source tree, but who > wants to see the all time history of a web site? I think it > would be sufficient to have the html pages needed to navigate > between local docs for devgui, api docs, readmes and the > project homepage. > > Later we could also set up a cron job that nightly puts the > pages within cvs onto the website. > > Summary: Let's have the main part of the website within cvs > as well as within release, another part may still be manually > maintained. > I can bring a first verion into cvs... Fine!!! > > > [EMAIL PROTECTED] wrote: > > > > While we are at it, who controls the SF project settings.. > According > > to SourceForge, we are still at an Alpha release! > > > You are right, Eric, we should set it to Beta. Or do you think we > should set it to 'production quality'? I'd say no, although many of us > use it within production environment, but I'd say no.... Beta would be OK for me!!! Regards, Henner ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
