Hi,
I'm sure I have seen the answer to this newbie question years ago, but
google doesn't seem to be my friend anymore:
I have a package waiting in NEW and I have a new version ready for
upload because either:
1- I have found an issue in the version in NEW that I want to fix
or
2- There is a
2015-06-03 10:07 GMT+01:00 Thibaut Paumard :
> Hi,
>
> I'm sure I have seen the answer to this newbie question years ago, but
> google doesn't seem to be my friend anymore:
>
> I have a package waiting in NEW and I have a new version ready for
> upload because either:
> 1- I have found an issue i
Hi,
2015-06-03 11:07 GMT+02:00 Thibaut Paumard :
> I have a package waiting in NEW and I have a new version ready for
> upload because either:
> 1- I have found an issue in the version in NEW that I want to fix
Depending on the issue, you could want to upload a fixed version, or
ask to remove th
> c) upload immediately.
> i) use a new version?
Because NEW processing takes such a long time now, I don't wait for FTP
master to review my packages in NEW before working on them again.
When I have a new revision of the package ready I just upload it so that
the latest revision will get i
Thibaut Paumard writes:
> What is the most efficient procedure?
> a) wait until the package was accepted or rejected;
Unless there is a legal issue with the package, I normally just wait. The
reason is that often the first version of a package may have some more
or less trivial issues with some
Quoting Bill Blough :
Hi Bill,
As I worked before on soci already, here's a short, likely
incomplete, review:
(I won't be able to sponsor this due to time constraints at least
within the next few weeks;
however if you still looking for a sponsor then, please ping me)
-> repository
I sugge
6 matches
Mail list logo
