[Pkg-octave-devel] Octave 3.4

[Jordi Gutiérrez Hermoso]

On 9 February 2011 14:45, Thomas Weber <tweber at debian.org> wrote:
> Okay, so here's a draft plan:
> 1) I will upload octave-forge packages to be built against the current
> 3.2 package.

This upload is without making the move to git+upstream yet, right?

> 2) We will switch the octave-forge packages over to
> git-with-upstream source.

Do you want to split them? Should we agree on who does which packages?
I think I am feeling ready to repeat the recipe I wrote down for
octave-symbolic for other packages.

> 3) Switching over other packages. This means all packages except
> Octave itself.

Okay, this seems pretty straightforward.

> 4) Switch to Octave 3.4. I haven't made up my mind about this yet,
> that's why I've put it at the end.

What about the soname and symbol versioning for the library? That's
part of the big change for Octave itself, right?

> - I want our patches to still appear at
> http://patch-tracker.debian.org. I'm not sure what this means for
> the workflow.

Those are just read from the quilt patches from the uploaded package.
Our VCS structure is irrelevant for those.

- Jordi G. H.