ons, 23 09 2009 kl. 17:32 +0200, skrev Paul Sundvall: > Speaking of releases, what does the process of releasing new package > versions look like?
Short answer: it's a mess! For details, see the 'admin/release.sh' script. > Should all packages be released at the same time? IMHO they shouldn't, but with the current system they are. > Is it the maintainer of each package that decides? At the moment, I basically decide when releases should happen. Each release requires quite a bit of (error-prone) work on my behalf. There is work going on (see the 'generate_html' package for details) on changing the release system, but work is going very slowly due to lack of time. > At which level should the changelog be? We autogenerate changelogs from SVN commit messages. > The specific reason I ask is that I think it would be nice to bump the > version number of octave-sockets as the documentation has been updated > and some bugs are removed. > Does anyone disagree if I do this for the octave-sockets package? I wouldn't mind this, just check that it haven't been bumped already first :-) > How and when are the documentation and download pages at > http://octave.sourceforge.net/packages.html updated? Does the update > happen automagically when the version number in the repository changes? Sadly no. The documentation is generated during the release process. See the 'admin/release.sh' script for the details. Søren ------------------------------------------------------------------------------ Come build with us! The BlackBerry® 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/devconf _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
