On Jul 9, 11:39 pm, dormando <[email protected]> wrote:
> - 3 weeks after each new stable release, we release -rc1 for the next > release. > - New -rc's will be kicked out daily or bidaily if there are fixes. > - After 1 week in RC, unless there are still bug reports coming in, stable > is released. Sounds pretty good. It seems like that should have a bit of a roadmap attached. > Development should stay the way it is. All of us making code changes > should be cc'ing as much as possible to the mailing list. I've noticed > some of this has dropped off a little in recent days, but it's easy to > pick that back up again. I do realize it's "easier" for people to just > "follow" us on github, but lets stay open for the sake of discussion. Agreed. > Since OSCON is coming up, I'd like to give an extra week for the first > cycle. Tentative date for 1.4.1-rc1 will be july 30th, with the stable > release of 1.4.1 being on august 6th. So, I have the following proposed for 1.4.1: Definite (already pushed): eb18f0a Fixes for compilation on OpenBSD. c5f458a extra comma e4e5695 Fix a test-time warning. f7399f2 Test suite warning fix. Probably (small bug/warning fixes): 7ed47ea Disable UDP port binding on the issue_44 test (issue 65) 0e79a35 Use snprintf instead of sprintf in the test app. 25d969f Validate buffer limits when dumping cache. 6c89d75 Enforce limits of add_delta buffer size. 07cbaa5 Limit room with snprintf in append_ascii_stats. 6fd556a Do not use strcpy for copying strings to fixed-size buffers. Possibly (slightly better, but not essential): 7afc893 Use vperror for perror with context. 078e5dc vperror implementation Eligible (not necessary, but open bugs that are fixed): issue_59: 20088f2 Kill off redundant and incorrect sizing definition. 41ef9df Clean up slab boundary checking. Possibly some other bugs that have fixes already.
