similar to: Opinions on Release Numbering

The Asterisk Development Team is pleased to announce the the second release candidate of 1.6.0.11, the release of 1.6.1.2, the first release candidate of 1.6.1.3, and the fourth beta of 1.6.2.0. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ . The release of 1.6.1.2 fixes a remote crash security vulnerability in the RTP stack. The

Hi, I would like to propose a few changes to the LLVM release process. The current process is documented here: https://llvm.org/docs/HowToReleaseLLVM.html There are two parts to this proposal. The first is a list of clarifications, which are things we are currently doing that aren't documented. The second is a list of changes which would actually modify how releases are currently managed.

http://www.asterisk.org/node/48327 I mean, really... you're kidding me, right? Lee.

I upgraded one of our servers to 1.4.19.1 last evening, but ended up having to drop back because of IAX calls failing at a near 50 % rate. Here is the message that we would receive on the console (multiple times), and then it would hangup the call. Avoiding IAX destroy deadlock Anyone else having similar problems? Thanks, Mike Clark

Does anyone know enough about the implementation of AstDB to know whether the data structure is a Hash function, a Balanced-Tree, a b-Tree, or a Linked List? I'm trying to estimate the lookup 'cost' of a AstDB with around 160,000 keys? Obviously I already know that it WILL WORK, but the question is whether the data structure is optimal in the Berkeley DB AS IMPLEMENTED in Asterisk.

1.2 is on the way, more regression spotting needed! Yes, it makes the numbers worse, but it means Wine will get better ;-) - d. ---------- Forwarded message ---------- From: Michael Stefaniuc <mstefani at redhat.com> Date: 13 June 2010 10:27 Subject: Re: Release plans To: wine-devel at winehq.org On 06/13/2010 10:39 AM, wylda at volny.cz wrote: > > Hi, another week and Sunday

Hi, I've fixed the version numbering and tagged 5.0.2-rc2. Testers can begin testing. -Tom

Dear testers, 7.0.0-rc2 was just tagged (from branch revision r340437). There have been a bunch of merges since rc1, and hopefully many of the issues with the previous candidate are fixed in this one. Please run the test script, share the results, and upload binaries. I will publish source tarballs, docs, and binaries on the web page once they're ready. Thanks, Hans

Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans

Dear testers, 7.0.0-rc3 was just tagged (from branch revision r341805). No further release candidates are currently planned, so this is a release candidate in the real sense: unless any serious issues surface, this is what the final release will look like. Please run the test script, share your results and upload binaries. Please also take a look at the release notes and other docs; small

Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom

Hi, I've tagged the 8.0.1-rc2 release, testers please begin testing and upload your binaries. There are still a few more bug fixes that I need to merge, so I'm planning to do one more release candidate before 8.0.1-final. -Tom

Hi, The number of stable patches has slowed down in the last few weeks, and we are approaching the halfway point between 3.3 and 3.4, so I think now is a good time to start planning for the 3.3.1 release. Here is the tentative schedule: September 3: 3.3.1-rc1 - This won't actually be a 'real' Release Candidate. The purpose of rc1 will be to update and test the release scripts

On 03/29/2018 08:09 PM, Tom Stellard via Release-testers wrote: > Hi, > > I've fixed the version numbering and tagged 5.0.2-rc2. Testers can > begin testing. > So far, I've only received 5.0.2-rc2 binaries from 2 testers. I am guessing this is due to the mix up with -rc1 and the fact that we don't normally do X.Y.2 releases. If you would like to test this release

Hello everyone! It has been a while since the 1.0.7 release, and I have fixed a lot of stuff since then. I think it's about time to make another release. I realize that there are still some outstanding issues, but it's nearly impossible to bring that down to zero. However, I'm open to discussion on anything that someone may feel is a "show-stopper". I am on IRC as

Hi, The 7.0.1-rc2 release has been tagged and is ready for testing. I forgot to bump the version number to 7.0.1 before I tagged -rc1, which is why we are now on -rc2. Remember, you can continue to submit merge requests up until Nov, 21, so keep testing and submitting fixes. Thanks, Tom

Hi, I would like to start a discussion about improvements to the stable release process, but first, here is a proposed schedule for the 4.0.1 release. May 1, 2017 -rc1 May 22, 2017 Deadline for submitting merge request May 29, 2017 Deadline for merging changes. June 3, 2017 -rc2 June 10, 2017 Final Release This is slightly different from previous stable releases in that we are doing an early

Hi Hans, I'm seeing one unexpected failure: libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp Test logs show: Standard Error: -- terminating with uncaught exception of type std::length_error: basic_string -- but only on my big endian MIPS machine. I have filed PR36373 for the above failure. I've looked at the failures

On Fri, Aug 23, 2013 at 04:17:02PM -0700, Tom Stellard wrote: > Hi, > > The number of stable patches has slowed down in the last few weeks, and > we are approaching the halfway point between 3.3 and 3.4, so I think now > is a good time to start planning for the 3.3.1 release. Here is the > tentative schedule: > > September 3: 3.3.1-rc1 > - This won't actually be

Does anyone know how to have an ad or announcement playing but in the background play a MP3 file? I think this would be done with the "s" extension and background application but not sure how? Any help would be appreciated!! -- Otis