[Pkg-octave-devel] Octave 3.4
sebastien.villemot at ens.fr
Thu Feb 10 08:55:35 UTC 2011
Thomas Weber <tweber at debian.org> writes:
> Okay, so here's a draft plan:
> 1) I will upload octave-forge packages to be built against the current
> 3.2 package. This means either uploading newly released octave-forge
> packages are just the old ones. The aim of this is to get somewhat
> up-to-date octave-forge packages in and reduce our bug count (the
> majority of current bugs is just about removing Rafael from the
> Uploader's list -- but the QA team is probably happy to get those 20 or
> so bugs from its radar).
> 2) We will switch the octave-forge packages over to git-with-upstream
> source. In that process, we should also look at the relevance of the
> respective octave-forge package. I'm looking for small packages with no
> real upstream maintenance and I think we should drop them. This includes
> especially every package using a SWIG wrapper and packages without unit
> 3) Switching over other packages. This means all packages except Octave
> itself. We should have some experience by then, so I don't expext too
> many errors from our side.
> 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.
> Things to consider:
> - Sébastien, are you okay with this for Dynare or do you want to keep
> the current setup (i.e. keeping just the debian/ directory in git)?
I’m fine with the idea of putting everything in git.
As upstream already uses git, does it make sense to just clone the
upstream branch, and then create a debian-specific branch ?
CEPREMAP - Paris School of Economics
Landline phone: +33 1 40 77 49 90
SIP phone: 87902 at ekiga.net
PGP Key: 0xA6C029B9D06B2913D71C105EBE37E801FB6EFF8B (http://pgp.mit.edu/)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the Pkg-octave-devel