On 17 Oct 2009, at 23:58, Søren Hauberg wrote: > Hi All > > For waaay too long I've been working on changing the release system. > Well, "working" isn't really the right word as I haven't actually done > much work due to lack of time. > > To those that don't remember, the reason why we don't allow individual > package maintainers to release their packages when it suits them, is > that the HTML generation is from the old monolithic days. This means > that the current system needs to generate the HTML pages for _all_ > packages at once. > > Carlo and myself have been working on changing this, such that HTML > pages can be generated for individual packages. The code for this is > available in the 'generate_html' package. > > For a long time essential parts of this code has been incomplete, but > I've recently been taking a stab at this once more. You can check out > the results at > > http://octave.sf.net/test > > This test site is only showing three packages (the ones I happened to > have installed). It is also missing a bunch of stuff: > > * Doxygen documentation. > * The Octave manual. > * The help texts of all functions that come with core Octave. > > Do you have any comments on this page? I've made some changes here and > there to simplify the HTML generation; I hope I haven't changed > anything > that people cared about (if so, speak up). > > Søren
Søren, Sorry I didn't have time to contibute more, but it seems you have managed to do a really great job! I really love this! Now, what would be really needed to start thorough testing would be a description of the precise steps that a package maintainer would need to do to publish a new version of his/her package. Before you move the new design to the production website I'd like as many as possible of the package maintainers to try to update their packages and to hear thei impressions on the procedure required for doing that. If you want I can prepare a short description to add on the OF developers guide. If I understand correctly the steps to follow would be: 1) bump the version number in the package DESCRIPTION file 2) produce a tar.gz of the package and add it to the sf release system 3) generate the function reference HTML files with generate_package_html 4) delete the contents of the folder containing the package help on the www sever 5) upload the new help files Am I missing something? c. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
