[1.46.1] Release notes
Hi, As always, I'm preparing the release notes. I left it a bit late this time, and there's not that many changes, so I've tried to summarise the existing changes myself. But I've probably got it completely wrong. So please check at: http://beta.boost.org/users/news/version_1_46_1 Normal procedure applies; you can either email me your changes or edit the notes yourself at: https://svn.boost.org/svn/boost/website/public_html/beta/feed/history thanks, Daniel
On 08.03.2011 10:17, Daniel James wrote:
Hi,
As always, I'm preparing the release notes. I left it a bit late this time, and there's not that many changes, so I've tried to summarise the existing changes myself. But I've probably got it completely wrong. So please check at:
http://beta.boost.org/users/news/version_1_46_1 I guess it's too late to still merge a tiny patch? r68990 fixes a compile error in PTree's JSON parser, and without it, the parser is completely unusable. The patch is very low-risk, as it only touches a file that is broken already.
If I can still merge it, this would need to be added to the release notes: PropertyTree: fix compile error in JSON parser Sebastian
On 3/8/2011 1:17 AM, Daniel James wrote:
Hi,
As always, I'm preparing the release notes. I left it a bit late this time, and there's not that many changes, so I've tried to summarise the existing changes myself. But I've probably got it completely wrong. So please check at:
http://beta.boost.org/users/news/version_1_46_1
Normal procedure applies; you can either email me your changes or edit the notes yourself at:
https://svn.boost.org/svn/boost/website/public_html/beta/feed/history
Not sure if this is too late or not... There is a very small iostreams libarary release notes documentation change that would be very useful for iostreams end users. I created a ticket for this and added a patch for the proposed change. This pertains to documenting a bug fix that was merged in for 1.46 (There are also not mention of these changes in the http://beta.boost.org/users/news/version_1_46 page, but that is another story). The relevant ticket is: https://svn.boost.org/trac/boost/ticket/5258 Is it possible for someone to merge this minor doc change so end users of the iostreams library are aware of this bug fix.
On 8 March 2011 21:02, eg <egoots@gmail.com> wrote:
Not sure if this is too late or not...
There is a very small iostreams libarary release notes documentation change that would be very useful for iostreams end users.
I created a ticket for this and added a patch for the proposed change.
I really can't deal with undocumented changes, I've enough to deal with as it is. If you want a change documented, you probably need to contact the person who made it. If there was a library maintainer, you could contact them. I've documented the changes for 1.46.1, but that was a special case, and I'm really not sure if I've done a good job. I will make changes to the release notes after a release if appropriate (it's best to keep this to a minimum, as it's annoying for anyone who subscribes to the feeds). Daniel
On 3/8/2011 2:03 PM, Daniel James wrote:
On 8 March 2011 21:02, eg<egoots@gmail.com> wrote:
Not sure if this is too late or not...
There is a very small iostreams libarary release notes documentation change that would be very useful for iostreams end users.
I created a ticket for this and added a patch for the proposed change.
I really can't deal with undocumented changes, I've enough to deal with as it is. If you want a change documented, you probably need to contact the person who made it. If there was a library maintainer, you could contact them. I've documented the changes for 1.46.1, but that was a special case, and I'm really not sure if I've done a good job. I will make changes to the release notes after a release if appropriate (it's best to keep this to a minimum, as it's annoying for anyone who subscribes to the feeds).
Thanks. I think you hit the real crux of the issue... there seems to be no "official" maintainer for iostreams at present, but that is a side issue here. cc'ing this to Steven Watanabe, who was the person who did the fix I am referring to, and merged it to release for 1.46 Steven: Could you please look at https://svn.boost.org/trac/boost/ticket/5258 and review the documentation patch proposal that basically adds a one line entry to in the iostreams "Release notes" page, and tells people of the "flush" bug regression that you fixed for 1.46. Even if the web site top level libraries (news) release notes do not get updated, at least the iostreams library docs themselves will have this info.
On 8 March 2011 22:26, eg <egoots@gmail.com> wrote:
Could you please look at https://svn.boost.org/trac/boost/ticket/5258
and review the documentation patch proposal that basically adds a one line entry to in the iostreams "Release notes" page, and tells people of the "flush" bug regression that you fixed for 1.46.
Even if the web site top level libraries (news) release notes do not get updated, at least the iostreams library docs themselves will have this info.
I went ahead and added the patch to the release branch in time for the 1.46.1. It's vague enough that it's unlikely to be incorrect. But I'd really prefer it if this was dealt with by someone who understands the change and could probably be more informative and accurate. Daniel
participants (3)
-
Daniel James -
eg -
Sebastian Redl