[Pkg-octave-devel] unstable snapshots
John W. Eaton
Tue, 15 Mar 2005 12:12:04 -0500
On 15-Mar-2005, Rafael Laboissiere <email@example.com> wrote:
| We can fill an RC (release critical) bug report against the package
| such that it is prevented from entering testing. We might also upload
| the packages to the experimental distribution, but this would defeat
| your goal, which is to reach a wide audience.
| Dirk has already made provisions for having concurrent octave<n>.<m>
| packages in Debian. I think that his approach can be extended to a new
| <n>.<m> version number.
| Instead of octave2.1.90, which is confusing, why not simply octave2.9?
OK, if that is easy, then I'll go with 2.9.x.
An RC bug (say, "not ready to replace octave2.1 yet") would be OK, but
if we actually introduce a new package name, then I suppose it is not
as important to keep it out of testing. In that case, we should keep
octave2.1 as the default version for now and allow people to install
both. If there are problems with octave2.9 we can always point them
to octave.2.1 until the problems can be fixed.