[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [uploaded] Re: RFS: cppcheck (4rd attempt)



On Sunday 09 November 2008 22:41:13 Reijo Tomperi wrote:
--cut--
> Few questions as I'm still new with all of this:
> - In mentors.debian.net I have set the "seeking for sponsor" option to
> "yes". Are you now my sponsor for the future updates also? Should I set
> the value to "I have found a sponsor"? Or is this sponsoring one time
> thing?
>
> - If you keep sponsoring me in the future releases also, how should I
> inform you about updates?

In my opinion it is always better to ask for sponsor via public mailing list 
like @deiban-mentors is, keeping need a sponsor `YES' in mentors webpage, 
simply because more that one sponsor could review and upload your package. I 
intend to sponsor cppcheck and I'm subscribed to that mailing list. Expect 
upstream wishlist bugs soon ;-) I'm still not sure if cppcheck could employ a 
formal grammar and parser generators (like bisonc++) to implement various 
checks, but that is a separate mail I intend to throw at you as upstream at 
some point.

> - Should I do something to the bug report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503730

This in fact is my fault, since I forgot to pass -v option to 
dpkg-buildpackage in order to include your previous changelog entries. could 
you please close it manually, otherwise I will close it when pakcage hits 
unstable.

> - Will the package now go to Debian testing? I don't see it yet on my
> mirror, but obviously it probably takes time to sync, but will it appear
> there after mirrors are updated?

Package is now hanging in Debian's NEW queue (since is new package which needs 
to be approved by ftpmasters /*these are humans*/) 
http://ftp-master.debian.org/new.html
then the package will be passed to autobuilders /*these are daemons*/ to be 
built on Debian's architectures.
http://buildd.debian.org/build.php
then comes installation to unstable (sid).

> - What will happen to the package now that it is in the testing
> (assuming it is there)? Obviously it needs to mature there for some
> time, but how does one tell when a package is mature enough and ready to
> move on?

Residing ten days in unstable without criticals bugs filed would lead to 
migration to testing, when testing is not frozen as it is now.

-- 
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>


Reply to: