> " " == Chris Lawrence <[EMAIL PROTECTED]> writes:
> Also, implementing the infrastructure for this proposal would
> take us 9/10 of the way to implementing package pools (and, in
> any event, the pools from what I've heard are just waiting on
> potato to release so we don
On Fri, Jun 09, 2000 at 04:15:42PM -0400, Franklin Belew wrote:
>
> 1> All completely new packages are required to go into experimental for no
>less than 30 days as a trial period.
>
> 2> All new maintainers must put their packages into experimental for no
>less than 30 days as a trial
On Sat, Jun 10, 2000 at 07:37:23AM +1000, Anand Kumria wrote:
> On Fri, Jun 09, 2000 at 04:15:42PM -0400, Franklin Belew wrote:
> > This is a proposal to reduce the number of bugs on the main archive and
> > to allow for a cleaner transition on package maintainership and version
> > control.
> The
On Fri, Jun 09, 2000 at 04:15:42PM -0400, Franklin Belew wrote:
> This is a proposal to reduce the number of bugs on the main archive and
> to allow for a cleaner transition on package maintainership and version
> control.
>
[ snip - reasons why experimental should be used. ]
> This tentative p
On Jun 09, Franklin Belew wrote:
> This is a proposal to reduce the number of bugs on the main archive and
> to allow for a cleaner transition on package maintainership and version
> control.
>
> 1> All completely new packages are required to go into experimental for no
>less than 30 days as
This is a proposal to reduce the number of bugs on the main archive and
to allow for a cleaner transition on package maintainership and version
control.
1> All completely new packages are required to go into experimental for no
less than 30 days as a trial period.
2> All new maintainers must
6 matches
Mail list logo
