Paul, I have kind of a related question.
asterisk-1.8.4-summary.txt does not always properly link specific patches to issues. For example, revision 307509 is associated with issue 18542, and it is not reflected in the summary. There may be more like this. I tried to report this inconsistency timely, issue #18933, but it is still listed as "new" What is the right way of reporting documentation issues? Thank you, Vladimir On 5/11/2011 9:46 AM, Paul Belanger wrote: > On 11-05-11 10:29 AM, Jeremy Kister wrote: >> I'm a bit confused about this release (and previous releases on the 1.8 >> track) so please bare with me. >> >> I viewed the ChangeLog, but I don't see any of the 'sample issues' >> listed. why is that ? I would expect to see the 'sample issues' listed >> after 1.8.4-rc3. >> >> Also, is there a reason/procedural error that patches such as: >> https://issues.asterisk.org/view.php?id=18382 >> https://issues.asterisk.org/view.php?id=18742 >> >> didnt make it into this 1.8.4 release ? >> >> > Correct, they will appear in 1.8.5-rc1 forward. When -rc1 is created, > it will be tagged from the HEAD of branches/1.8.. If 1.8.5-rc2 is > create, it is because of an issue / bug was found in 1.8.5-rc1, and > will include that fix only. > > If a new issue is reported after 1.8.5-rc1 and fixed in branches/1.8, > it will not be added into 1.8.5 release, but will wait until 1.8.6-rc1. > -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
