I think you have some strange idea of what the release process
involves. The release is easy. A small project like tmux does not need
more people with some sort of special release engineer hat.
What we could use is a more testing, formal or informal, in the time
between releases. If we come up to
That is not how it works and you must be aware of that. You don't just
walk into an open source project knowing nobody and offering nothing,
you need to get involved and do some work, then you get the
responsibility. The next release won't be for six months, you have ample
time to get going.
On
On Thu, Oct 13, 2016 at 4:32 PM, Nicholas Marriott
wrote:
> Ethan -
>
> You have made no code contributions to tmux and made no bug
> reports. Until that changes - even if there was a release engineering
> position going, you wouldn't be a candidate.
I don't have to make contributions to see wher
Ethan -
You have made no code contributions to tmux and made no bug
reports. Until that changes - even if there was a release engineering
position going, you wouldn't be a candidate.
In 10 years, nobody who has sent patches has complained about how they
are credited. If someone sends code and doe
On Wed, Oct 12, 2016 at 5:27 PM, Helmut K. C. Tessarek
wrote:
> One of the reasons why I haven't sent any patches is, because I don't
> want to write code, test it, send a patch file via git to a mailing list
> (which is another annyoance) and then my name does not even show up as
> the author. I
On 2016-10-12 15:35, Helmut K. C. Tessarek wrote:
> In any case, the way development is handled is very untypical to any
> project I've ever seen. That's why I'm so puzzled by it.
Never mind. Thomas explained the OpenBSD dev process. It makes sense now.
Cheers,
K. C.
--
regards Helmut K. C. Te
Hello Thomas,
On 2016-10-12 14:46, Thomas Adam wrote:
> This can't happen, and you're misunderstanding how the workflow happens.
Yes, this is certainly true. That's why I asked. :-)
> You're not the first one to either. Tmux is developed as part of OpenBSD.
> It's in the base system. OpenBSD u
On 2016-10-12 12:40, Nicholas Marriott wrote:
> I think you made a mistake here: --disable-debug works fine in Git, we
> only change the default.
I'll try again, but it did not work when I used it yesterday. Maybe I
have to delete the .cache dirs or start completely from scratch.
I'll check it ou
Hello,
Thank you for the reply.
On 2016-10-12 12:34, Nicholas Marriott wrote:
> People don't know when they've built from Git and when they haven't?
> I don't think this is a real problem.
It only works for people who build it themselves. But since there is
only 1 realease every year, a lot of p
On Wed, Oct 12, 2016 at 12:27:01PM -0400, Helmut K. C. Tessarek wrote:
> Other projects use versioning like:
>
> 2.4-dev
> 2.3--<7 character long git hash>
> (e.g.: 2.3-17-76a9e6f)
Whilst it's possible to easily include the output of git-describe into the
version string at build time (I do this w
On Wed, Oct 12, 2016 at 05:34:06PM +0100, Nicholas Marriott wrote:
> Hi
>
> On Wed, Oct 12, 2016 at 12:27:01PM -0400, Helmut K. C. Tessarek wrote:
> > Hello,
> >
> > I have a few questions/comments and I hope that Thomas or Nicholas find
> > the time to reply.
> >
> > I've noticed that as soon a
Hi
On Wed, Oct 12, 2016 at 12:27:01PM -0400, Helmut K. C. Tessarek wrote:
> Hello,
>
> I have a few questions/comments and I hope that Thomas or Nicholas find
> the time to reply.
>
> I've noticed that as soon as a release is made the version is bumped and
> debug is turned on. I was not even ab
Hello,
I have a few questions/comments and I hope that Thomas or Nicholas find
the time to reply.
I've noticed that as soon as a release is made the version is bumped and
debug is turned on. I was not even able to turn this off with the
configure option --disable-debug.
So a static binary compile
13 matches
Mail list logo
