Or hooks... nobody uses hooks and they could do with a) some testing and b) some thought about how they could be more useful.
On Mon, Oct 10, 2016 at 11:09:54PM +0100, Nicholas Marriott wrote: > On Mon, Oct 10, 2016 at 10:13:06PM +0100, Ethan Raynor wrote: > > On Mon, Oct 10, 2016 at 9:11 AM, Nicholas Marriott > > <[email protected]> wrote: > > > Hi > > > > > > Firstly, if you are volunteering to do some testing before releases, > > > that's great. Please drop me and Thomas a mail with the plan - I'll > > > probably be happy to just leave it in your hands and we do a release > > > when you say "go for it". There is a tmux-tests repository on GitHub > > > with some scripts, but it's now dead and needs someone else to pick it > > > up. Currently releases are around May and September but it doesn't have > > > to stay like that. > > > > I can try. But when I do this I think it would be a much better idea > > if I was to also take over complete control of the software releases. > > That way I can be sure there won't be the same mistakes as has > > happened in the past. How can I start to do this? Do I need to talk to > > yourself or Thomas? > > One thing at a time, it will be 6 months until the next release. > > I suggest you either look at the 2.3 release we have just done, or start > looking at how to test existing features, or new code since 2.3 (there > is not much yet, but there will be fairly soon). > > > > > > Secondly, OS X's locale implementation has some fundamental problems, > > > that these only came to light in releases shows only that OS X users > > > didn't report them, or that we weren't able to resolve them, during the > > > 6 months between each release. > > > > But this point is curious and valid - why do they tend to show their > > nasty head after release? > > Probably because few OS X users test the changes before we make a > release... and then they all do. -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
