Re: Ports tree locked for 6.5 release

2019-04-06 Thread Ed Ahlsen-Girard
> From: Marc Espie > Date: 2019-04-06 13:24:35 > Message-ID: 20190406132435.GA7545 () lain ! home > [Download RAW message or body] > > On Fri, Apr 05, 2019 at 07:11:57AM -0500, Edward Lopez-Acosta wrote: > > You are correct its not my process, but I am still curious as to the > >

Re: Ports tree locked for 6.5 release

2019-04-06 Thread Marc Espie
On Fri, Apr 05, 2019 at 07:11:57AM -0500, Edward Lopez-Acosta wrote: > You are correct its not my process, but I am still curious as to the > rationale which is just a question that was not answered. Nowhere did I > suggest, or imply, that it should be changed. There's no rationale. Just

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Ian Darwin
On 4/5/19 7:44 AM, Edward Lopez-Acosta wrote: Is this due to an inefficient process, technical limitation, or other reason (lack of manpower doesn't qualify as that seems self inflicted by the project)? This wording is one of several things that led to accusations of disrespect. If I said

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Stuart Henderson
On 2019/04/05 06:44, Edward Lopez-Acosta wrote: > Could you please explain the logic behind this as I am confused. Is this due > to an inefficient process, technical limitation, or other reason (lack of > manpower doesn't qualify as that seems self inflicted by the project)? You seem to disagree

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Andreas Kusalananda Kähäri
u. Fedora has three stages of "milestone freezing". This is not an uncommon thing. See also: https://en.wikipedia.org/wiki/Freeze_(software_engineering) Cheers, > > > Date: Thu, 4 Apr 2019 15:58:06 +0200 > > From: Christian Weisgerber > > To: ports@openbsd.org >

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Peter N. M. Hansteen
Apr 05, 2019 at 07:20:49AM -0500, Edward Lopez-Acosta wrote: > Do you have documentation on this process? I would be happy to read it and > ask questions you feel may be better. As an open source project I am > surprised about the lack of transparency for various things. You will find several

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Solene Rapenne
gain, they may > exist I just don't know of any and find the process awkward and confusing. > > > Date: Thu, 4 Apr 2019 15:58:06 +0200 > > From: Christian Weisgerber > > To: ports@openbsd.org > > Subject: Ports tree locked for 6.5 release > > Message-ID: <

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Theo de Raadt
>Do you have documentation on this process? I would be happy to read it >and ask questions you feel may be better. As an open source project I am >surprised about the lack of transparency for various things. Such strong words! >I have opinions yes, but I also try to understand those of others

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Edward Lopez-Acosta
Do you have documentation on this process? I would be happy to read it and ask questions you feel may be better. As an open source project I am surprised about the lack of transparency for various things. I have opinions yes, but I also try to understand those of others which is what prompted

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Theo de Raadt
>You are correct its not my process, but I am still curious as to the >rationale which is just a question that was not answered. Nowhere did I >suggest, or imply, that it should be changed. > >And how do you define crappier releases? If something is stable enough >that the development team

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Edward Lopez-Acosta
You are correct its not my process, but I am still curious as to the rationale which is just a question that was not answered. Nowhere did I suggest, or imply, that it should be changed. And how do you define crappier releases? If something is stable enough that the development team decide to

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Theo de Raadt
>Could you please explain the logic behind this as I am confused. Is this >due to an inefficient process, technical limitation, or other reason >(lack of manpower doesn't qualify as that seems self inflicted by the >project)? Are you somehow tracking submissions to take care of when this

Re: Ports tree locked for 6.5 release

2019-04-05 Thread Edward Lopez-Acosta
, 4 Apr 2019 15:58:06 +0200 From: Christian Weisgerber To: ports@openbsd.org Subject: Ports tree locked for 6.5 release Message-ID: <20190404135806.gb29...@lorvorc.mips.inka.de> The t2k19 hackathon has concluded and the ports tree is now locked for the 6.5 release. Important(!) fixes are

Ports tree locked for 6.5 release

2019-04-04 Thread Christian Weisgerber
The t2k19 hackathon has concluded and the ports tree is now locked for the 6.5 release. Important(!) fixes are still possible for a brief period. Committers need to ask sthen@ or me for approval. -- Christian "naddy" Weisgerber na...@mips.inka.de