Re: Ports tree locked for 6.5 release

On Fri, Apr 05, 2019 at 06:44:36AM -0500, 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)? Are
> you somehow tracking submissions to take care of when this unlocked so
> people don't waste their time needing to resubmit them?
>
> While they may exist I know of no other project, including OS, that halt
> development like this for long, if at all, to do a release. Again, 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 <naddy@mips.inka.de>
> > To: ports@openbsd.org
> > Subject: Ports tree locked for 6.5 release
> > Message-ID: <20190404135806.GB29025@lorvorc.mips.inka.de>
> >
> > 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 naddy@mips.inka.de
>
>
> --
> Edward Lopez-Acosta
>

People working on ports can still continue to work locally and will wait
the freeze to commit locally tested changes.