El lun, 11-07-2005 a las 20:57 +0200, Henrik Brix Andersen escribió:
> On Mon, 2005-07-11 at 15:10 +0200, José Alberto Suárez López wrote:
> > * this app will not broke anything in the system or userside if it
> > fails.
> > * i will go in vacations soon
> > * and i forget about 30 days sorry :P
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> a few :
>
> * this app will not broke anything in the system or userside if it
> fails.
But users will get angry if a package is not working and start filling bugs.
> * i will go in vacations soon
All the more reason _not_ to mark stable, since a
On Mon, 2005-07-11 at 15:10 +0200, José Alberto Suárez López wrote:
> * this app will not broke anything in the system or userside if it
> fails.
> * i will go in vacations soon
> * and i forget about 30 days sorry :P
Those are not really valid points for breaking the policy - but it's too
late no
El lun, 11-07-2005 a las 14:58 +0200, Henrik Brix Andersen escribió:
> On Mon, 2005-07-11 at 14:53 +0200, José Alberto Suárez López wrote:
> > after a week w/o bugs for ebookmerge i will unmask it and i will remove
> > all the ebook-*.ebuilds if nobody say the secret word ;)
>
> A week? Any pa
On Mon, 2005-07-11 at 14:53 +0200, José Alberto Suárez López wrote:
> after a week w/o bugs for ebookmerge i will unmask it and i will remove
> all the ebook-*.ebuilds if nobody say the secret word ;)
A week? Any particular reason not to follow policy and wait 30 days?
./Brix
--
Henrik Brix
Hola :)
after a week w/o bugs for ebookmerge i will unmask it and i will remove
all the ebook-*.ebuilds if nobody say the secret word ;)
regards
signature.asc
Description: This is a digitally signed message part
