[Pkg-octave-devel] octave3.0 entering testing today + octave-forge pkgs
rafael at debian.org
Sat Apr 12 18:52:51 UTC 2008
The octave3.0 package was caught in a complex library transition for
suitesparse, lam, and hdf5 and involving dozens of other packages. Thanks
to a hint by Mark 'HE' Brockschmidt, octave3.0 and other packages will enter
testing today. More details can be found in a thread in debian-release .
It is now time to speed up the work on other DOG packages. One obvious
thing to do is to finish the work on the octave-forge packages. I am
disappointed by the large number of copyright problems that we found  but
I think we should go ahead and release the packages. Those problems are not
serious and will be fixed in the future. I hope that the ftp-masters will
give us a hard time when checking the packages in NEW.
BTW, how should we proceed as regards upstream? Some of the copyright
problems have been already reported. Should we reported all the problems
that we found (and will find) at once in a message to octave-dev?
As regards uploading the packages, remember that according to the release
schedule  we are in the "very soft freeze" period, which the Release Team
defined like this:
Please start thinking about the release when uploading new major
upstream versions. Only upload to unstable if you are sure that
the software will be stable before we release. If you are not
convinced, use experimental as staging area.
I do not think that we should release first to experimental, since the
octave-forge pkgs are not likely to break anything. I would upload then
directly to unstable. What do you think?
Otherwise, although there is no real hush, since the full freeze is schedule
for the mid of July 2008, let us remember the words of the Release Team:
Please don't wait with uploads for the last day before the freeze,
More information about the Pkg-octave-devel