[Pkg-amule-devel] Task list for November

[Adrián Yanes]

HI Sandro. thanks for your fast response.

Thanks for the explanation of the branchs.

The phrase of new features was speaking about the aMule program not
package.  The correct expression it´s to update the version of package
( 2.2.5-1.1 ==> next upstream).

I going to start with the new upstream (2.2.6).

And we should consider  to update also amule-common no ?

Cheers, Adrian.


2009/11/1 Sandro Tosi <morph at debian.org>:
> On Sun, Nov 1, 2009 at 16:41, Adrián Yanes <devel at ayanes.com> wrote:
>> So my idea it´s create a new branch inside of the git repository ( we
>> can call "testing" branch)
>
> Why this branch? what's the purpose? Use 'master' for unstable
> release, 'stable'/'experimental' branch for uploads aimed at those
> suites, or so.
>
> 'testing' is recalling to much the 'testing' debian suite (aka
> 'squeeze'); call it 'experimental' is the upload is experimental or,
> 'first-pkg-things' or so
>
>> to update the new features of aMule Package.
>
> what new features are you talking about?
>
> The only big thing that needs to be done asap is the packaging of the
> new upstream release, 2.2.6; this can include also some packaging
> changes (debian/control fields, switch to dh7, etc) but not too many
> as to hold off the upload.
>
> After that, drastical package changes (like dh7, for example, if too
> big for the above point), and bug triaging.
>
> Regards,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>