Daniel James wrote:
2010/1/13 Tobias Schwinger <tschwinger@isonews2.com>:
Seems a "release procedure issue" to me; the trunk has apparently been copied over an old release where those files were still present and needed.
There's no consensus on the best way to merge. A lot of developers seem to be set in their ways so it's up to the individual libraries to decide how they want to manage merge. Although, life would be a lot easier if we all followed the same process.
Those files can be deleted from the release branch (gone from trunk since February 09, last changes on Fusion in June 09).
The C++ files can be left until the next release as it's too late to remove them without good reason. The documentation should be fixed though, the last merge seem to have gone wrong.
Not good. Another issue: Boost.Functional.Forward / Factory are missing from the release branch. Fusion docs/examples reference them and, as Forward has been factored out of Fusion, it is required for the full functionality of older versions. Last release having been messed is something I object repeating. So I suggest we either roll back the Functional module to ~1 year ago (including the documentation, of course) or get the missing files in, docs repaired, and while we're at it we might as well remove the outdated files. So, may I please get all this stuff straightened out? Joel, in case I get a "go" from the Review Managers, please let me know about recent trunk changes on the docs which are to be kept out of the release, if any. Here are my apologies for missing the changes in the release procedure and holding up the schedule, now. Will be more attentive, from now on. I never really got a notification like "Copy / merge your libs to the Boost instance rooted in branches/release, now" (should there be one, maybe?). Regards, Tobias