Ports tree locked for 7.3

The ports tree is locked for the 7.3 release now. No more commits. -- Christian "naddy" Weisgerber na...@mips.inka.de

Ports tree locked

The ports tree is now locked for the 7.2 release. No more commits. -- Christian "naddy" Weisgerber na...@mips.inka.de

Ports tree locked

The ports tree is locked now. If you still have suggestions for important fixes, talk to sthen@ and me over the next few days. -- Christian "naddy" Weisgerber na...@mips.inka.de

Ports tree locked

The ports tree is locked for 6.7 now. -- Christian "naddy" Weisgerber na...@mips.inka.de

Ports tree locked for 6.6 release

The ports tree is now locked for the 6.6 release. No more commits. If something truly critical comes up, talk to sthen@ and me. -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: Ports tree locked for 6.5 release

> 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

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

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

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

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

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

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

>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

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

>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

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

>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

, 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

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

Re: Ports tree locked

On 2018-03-25, Christian Weisgerber wrote: > The ports tree is now locked for the 6.3 release. ... and unlocked again. -- Christian "naddy" Weisgerber na...@mips.inka.de

Ports tree locked

The ports tree is now locked for the 6.3 release. We still want to get in the latest Mozilla point releases. If anything else really important pops up, talk to sthen and me. -- Christian "naddy" Weisgerber na...@mips.inka.de

Ports tree locked for 5.9

The ports tree is now locked for the release. We may still trickle in a few important diffs, but talk to sthen@ and me first. No unapproved commits! -- Christian "naddy" Weisgerber na...@mips.inka.de

Ports tree locked for 5.8

The ports tree is locked now for the 5.8 release. -- Christian naddy Weisgerber na...@mips.inka.de

Ports tree locked for 5.6

The ports tree is now locked for 5.6. No more commits. If something supercritical turns up, talk to me. -- Christian naddy Weisgerber na...@mips.inka.de

Re: Firefox and the ports tree LOCKED

benefit i am complaining. I'm managing well (and I do not even run stable at home).  Original message From: Landry Breuil lan...@rhaalovely.net Date: 22/07/2013 08:49 (GMT+02:00) To: ports@openbsd.org Subject: Re: Firefox and the ports tree LOCKED On Mon, Jul 22, 2013

Re: Firefox and the ports tree LOCKED

[quoting reformatted. there are times when top-posting makes sense but this is not one of them] Original message From: Landry Breuil lan...@rhaalovely.net - gfx issues with pictures are known and have been discussed here, try   the various workarounds devised in the

Re: Firefox and the ports tree LOCKED

: Firefox and the ports tree LOCKED [quoting reformatted. there are times when top-posting makes sense but this is not one of them] Original message From: Landry Breuil lan...@rhaalovely.net - gfx issues with pictures are known and have been discussed here, try

Re: Firefox and the ports tree LOCKED

On 2013 Jul 22 (Mon) at 07:56:31 +0300 (+0300), Lars Engblom wrote: :I have several times seen reports about FF crashing. It might have :been here or then on #openbsd (I am not sure where). I thought this irc is not a place to report bugs. The only place where you could expect developers to view

Re: Firefox and the ports tree LOCKED

On 2013/07/22 10:32, Lars Engblom wrote: [Sorry for another top-posting. Already the last mail I intended to not top-post but my phone does not allow anything else and I can not reach any computer with decent client at the moment] Is there a chans this slow behavior is leading to crashes in

Re: Firefox and the ports tree LOCKED

On Mon, Jul 22, 2013 at 10:32:06AM +0300, Lars Engblom wrote: [Sorry for another top-posting. Already the last mail I intended to not top-post but my phone does not allow anything else and I can not reach any computer with decent client at the moment] Is there a chans this slow behavior is

Re: Firefox and the ports tree LOCKED

On Mon, Jul 22, 2013 at 10:32:06AM +0300, Lars Engblom wrote: [Sorry for another top-posting. Already the last mail I intended to not top-post but my phone does not allow anything else and I can not reach any computer with decent client at the moment] Is there a chans this slow behavior is

Re: Firefox and the ports tree LOCKED

On Mon, Jul 22, 2013 at 10:01:25AM +0300, Lars Engblom wrote: Then I was right regarding how well known the bugs are.  As you wrote, there are even known workarounds. We're talking about different issues here. And as marc stated, no trace/proper report/homework - the bug doesnt exist. That I

Re: Firefox and the ports tree LOCKED

).?? Original message From: Landry Breuil lan...@rhaalovely.net Date: 22/07/2013 08:49 (GMT+02:00) To: ports@openbsd.org Subject: Re: Firefox and the ports tree LOCKED On Mon, Jul 22, 2013 at 07:56:31AM +0300, Lars Engblom wrote: I have several times seen reports

Re: Firefox and the ports tree LOCKED

message From: Landry Breuil lan...@rhaalovely.net Date: 22/07/2013 08:49 (GMT+02:00) To: ports@openbsd.org Subject: Re: Firefox and the ports tree LOCKED On Mon, Jul 22, 2013 at 07:56:31AM +0300, Lars Engblom wrote: I have several times seen reports about FF crashing. It might have

Re: Firefox and the ports tree LOCKED

On Mon, Jul 22, 2013 at 09:24:47AM -0700, patrick keshishian wrote: Anybody new to OpenBSD will either not report bugs in which case we don't know about them or their problems, or be told in the gentle OpenBSD way to RTFML. Since you bring it up... /or/ when a problem gets reported, even

Re: Firefox and the ports tree LOCKED

On Mon, Jul 22, 2013 at 8:00 AM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Mon, Jul 22, 2013 at 10:01:25AM +0300, Lars Engblom wrote: Then I was right regarding how well known the bugs are. ??As you wrote, there are even known workarounds. There are steps to diagnose YOUR

Ports tree LOCKED

The ports tree is now LOCKED for the 5.4 release. -- Christian naddy Weisgerber na...@mips.inka.de

Firefox and the ports tree LOCKED

Something seriously needs to be done to Firefox before 5.4 release. It has been really buggy the latest months. It is almost completely unusable. It dumps core daily for me. Pictures are often distorted. Like it is now, if anyone new to OpenBSD would try it, they would never return as they

Re: Firefox and the ports tree LOCKED

On 7/22/2013 12:27 AM, Lars Engblom wrote: Something seriously needs to be done to Firefox before 5.4 release. It has been really buggy the latest months. It is almost completely unusable. It dumps core daily for me. Pictures are often distorted. Stellar bug report. Like it is now, if

Re: Firefox and the ports tree LOCKED

I have several times seen reports about FF crashing. It might have been here or then on #openbsd (I am not sure where). I thought this is something everybody knows. I made a misjudgement because I did not want to send a bug-report for something I thought everybody knew already. What I sent to

Re: Firefox and the ports tree LOCKED

On Mon, Jul 22, 2013 at 07:56:31AM +0300, Lars Engblom wrote: I have several times seen reports about FF crashing. It might have been here or then on #openbsd (I am not sure where). I thought this is something everybody knows. I made a misjudgement because I did not want to send a bug-report

Ports tree locked

The ports tree is locked now. Barring catastrophic failures, there will be no more changes for the release. I'm going to sync INDEX tomorrow. -- Christian naddy Weisgerber na...@mips.inka.de

Ports tree locked

The ports tree is now locked in preparation for the 4.6 release. There will be no ports commits for the duration of the lock. -- Christian naddy Weisgerber na...@mips.inka.de

Ports tree locked for 4.5

The ports tree is now locked for 4.5. No more commits. If there is anything critical, talk to me. (Critical as in omg, hundreds of ports are broken, not as in there's a bug in Joe Random port.) I'll kick off a test build to find and fix any straggling plist issues and the like, which may have

Re: ports tree locked

What's happening with m68k? No snapshot package update since 4.3. Are they halted until the linker/binutil issue is resolved? Is that likely to be fixed in 4.4? (Is that issue just mac68k?) Probably going to miss 4.4. Well, systems (including xenocara) will be built for 4.4, but is

Re: ports tree locked

On Thu, Aug 7, 2008 at 9:38 AM, Hugo Villeneuve [EMAIL PROTECTED] wrote: On Tue, Aug 05, 2008 at 08:27:44PM -0700, Peter Valchev wrote: With the python fixes just making it in, the tree is now locked for the 4.4 release. Thanks to everyone who tested! What's happening with m68k? No snapshot

ports tree locked

With the python fixes just making it in, the tree is now locked for the 4.4 release. Thanks to everyone who tested!

Ports tree locked

The ports tree is now locked for the upcoming 4.3 release. Please hold off on submitting new ports and regular updates. -- Christian naddy Weisgerber [EMAIL PROTECTED]

is the ports tree locked?

I have noticed that http://ports.openbsd.nu/ has not updated ports in about 2 weeks, I was wondering if this was normal for OpenBSD Sam Fourman Jr.

Re: is the ports tree locked?

Hi Sam, I was wondering if this was normal for OpenBSD http://marc.theaimsgroup.com/?l=openbsd-portsm=115704857123813w=2 Very, very normal... Nico P.S. Do test!

ports tree locked

The ports tree is now locked. What that means is that you should be very careful with the changes you propose and everything should be approved by me. However, you must discuss it with the usual suspects and other developers as well. Accept that we will ship with some bugs, but focus on fixing