[Fusion] Permission to update release branch and roll in dependencies
Dear release team, we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread http://thread.gmane.org/gmane.comp.lib.boost.devel/198532/ before it's too late, again. Reportedly the outdated files do - other than hoped in that thread - NOT work anymore - and neither do the new and documented ones for the lack of dependencies. So, what I'd like to do is: o merge trunk changes into the Functional module of Fusion o add Forward o optionally add Factory Please check the new mini libraries for "release compliance" and give me a go on the fix. Would be too bad to go with a partially defunct Fusion in two releases for bureaucratic reasons. Please also note that rolling back to a proper previous version might involve more changes and will complicate future merges for us. Regards, Tobias
On Wed, Apr 14, 2010 at 5:16 PM, Tobias Schwinger <tschwinger@isonews2.com> wrote:
Dear release team,
we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread
http://thread.gmane.org/gmane.comp.lib.boost.devel/198532/
before it's too late, again. Reportedly the outdated files do - other than hoped in that thread - NOT work anymore - and neither do the new and documented ones for the lack of dependencies.
So, what I'd like to do is:
o merge trunk changes into the Functional module of Fusion o add Forward o optionally add Factory
Please check the new mini libraries for "release compliance" and give me a go on the fix. Would be too bad to go with a partially defunct Fusion in two releases for bureaucratic reasons. Please also note that rolling back to a proper previous version might involve more changes and will complicate future merges for us.
What's the status of this request? Did you get feedback from anyone? --Beman
Beman Dawes wrote:
On Wed, Apr 14, 2010 at 5:16 PM, Tobias Schwinger <tschwinger@isonews2.com> wrote:
Dear release team,
we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread
http://thread.gmane.org/gmane.comp.lib.boost.devel/198532/
before it's too late, again. Reportedly the outdated files do - other than hoped in that thread - NOT work anymore - and neither do the new and documented ones for the lack of dependencies.
So, what I'd like to do is:
o merge trunk changes into the Functional module of Fusion o add Forward o optionally add Factory
Please check the new mini libraries for "release compliance" and give me a go on the fix. Would be too bad to go with a partially defunct Fusion in two releases for bureaucratic reasons. Please also note that rolling back to a proper previous version might involve more changes and will complicate future merges for us.
What's the status of this request? Did you get feedback from anyone?
No, unfortunately not. Regards, Tobias
Hi Tobias, sorry for he delay. I missed this the first time. On 4/21/2010 2:49 AM, Tobias Schwinger wrote:
Beman Dawes wrote:
On Wed, Apr 14, 2010 at 5:16 PM, Tobias Schwinger <tschwinger@isonews2.com> wrote:
Dear release team,
we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread
http://thread.gmane.org/gmane.comp.lib.boost.devel/198532/
before it's too late, again. Reportedly the outdated files do - other than hoped in that thread - NOT work anymore - and neither do the new and documented ones for the lack of dependencies.
So, what I'd like to do is:
o merge trunk changes into the Functional module of Fusion o add Forward o optionally add Factory
Please check the new mini libraries for "release compliance" and give me a go on the fix.
We're in bug-fix mode for the next release. Are there test failures on the release branch this will fix? Which ones? Which tickets will this close? What revisions specifically are you asking to merge from trunk? Can you send links to them?
Would be too bad to go with a partially defunct Fusion in two releases for bureaucratic reasons.
Not for bureaucratic reasons. You had 3 months to merge your fixes from trunk to release. IIRC, this is the second time you've waited until the last minute to try to get these changes in. Don't blame the release procedures or the release managers, who are doing their job as best they can.
Please also note that rolling back to a proper previous version might involve more changes and will complicate future merges for us.
Roll back what? Did anybody suggest that? -- Eric Niebler BoostPro Computing http://www.boostpro.com
Eric Niebler wrote:
Hi Tobias, sorry for he delay. I missed this the first time.
On 4/21/2010 2:49 AM, Tobias Schwinger wrote:
Beman Dawes wrote:
On Wed, Apr 14, 2010 at 5:16 PM, Tobias Schwinger <tschwinger@isonews2.com> wrote:
Dear release team,
we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread
http://thread.gmane.org/gmane.comp.lib.boost.devel/198532/
before it's too late, again. Reportedly the outdated files do - other than hoped in that thread - NOT work anymore - and neither do the new and documented ones for the lack of dependencies.
So, what I'd like to do is:
o merge trunk changes into the Functional module of Fusion o add Forward o optionally add Factory
Please check the new mini libraries for "release compliance" and give me a go on the fix.
We're in bug-fix mode for the next release. Are there test failures on the release branch this will fix?
Tests are fine.
Which ones?
Two programs in the 'example' directory won't compile for missing dependencies, though.
Which tickets will this close?
None. Joel forwarded me some user requests complaining about missing, now factored-out (missing in release) functionality, though. I guess I can forward them to you, if necessary. The documentation also references the Forward and Factory utilities, as those are the factorizations. To make things worse there are some outdated and defunct files on the release branch. As they basically (though not working) implement the now-missing functionality have added to the confusion of users.
What revisions specifically are you asking to merge from trunk? Can you send links to them?
See the attachment for what I have done to my working copy of the release branch (trunk revision 61505, release revision 61506). All tests passed and the examples compiled and ran without further modification.
Would be too bad to go with a partially defunct Fusion in two releases for bureaucratic reasons.
Not for bureaucratic reasons. You had 3 months to merge your fixes from trunk to release. IIRC, this is the second time you've waited until the last minute to try to get these changes in. Don't blame the release procedures or the release managers, who are doing their job as best they can.
Not blaming anyone (except me, perhaps) - just kindly asking for an open-minded investigation rather than a categoric "no". Since, as you observed correctly, I had three months and it's the "last minute" again, most unfortunately :/. However, there is no potential for breakage, since we're talking about a) adding code that is not there yet and b) removing code that is old and already broken.
Please also note that rolling back to a proper previous version might involve more changes and will complicate future merges for us.
Roll back what? Did anybody suggest that?
It has been considered rolling back the docs (in that thread referenced in the OP). As we know now, this route would also require code changes because the old files in the release branch don't work as-is. Regards, Tobias # release Factory/Forward svn copy trunk/boost/functional/forward_adapter.hpp release/boost/functional svn copy trunk/boost/functional/lightweight_forward_adapter.hpp release/boost/functional svn copy trunk/boost/functional/factory.hpp release/boost/functional svn copy trunk/boost/functional/value_factory.hpp release/boost/functional svn copy trunk/libs/functional/forward release/libs/functional svn copy trunk/libs/functional/factory release/libs/functional # remove non-working files from previous versions svn del release/boost/fusion/functional/adapter/detail/pow2_explode.hpp svn del release/boost/fusion/functional/adapter/detail/pt_def.hpp svn del release/boost/fusion/functional/adapter/detail/pt_undef.hpp svn del release/boost/fusion/functional/adapter/unfused_generic.hpp svn del release/boost/fusion/functional/adapter/unfused_lvalue_args.hpp svn del release/boost/fusion/functional/adapter/unfused_rvalue_args.hpp svn del release/boost/fusion/functional/generation/make_unfused_generic.hpp svn del release/boost/fusion/functional/generation/make_unfused_lvalue_args.hpp svn del release/boost/fusion/functional/generation/make_unfused_rvalue_args.hpp
Hi Tobias, On Wednesday 14 April 2010 14:16:39 Tobias Schwinger wrote:
we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread
Is this done for 1.44? Or will this be too late once again? Regards, Ravi
On 7/5/10 7:15 AM, Ravi wrote:
Hi Tobias,
On Wednesday 14 April 2010 14:16:39 Tobias Schwinger wrote:
we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread
Is this done for 1.44? Or will this be too late once again?
I think it's done. Christopher Schmidt merged all outstanding Fusion-related changesets. Thanks Christopher! Regards, -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net
Joel de Guzman schrieb:
On 7/5/10 7:15 AM, Ravi wrote:
Hi Tobias,
On Wednesday 14 April 2010 14:16:39 Tobias Schwinger wrote:
we're about to freeze the next release. I'd like to kindly ask for your permission to address the issues discussed in this thread
Is this done for 1.44? Or will this be too late once again?
I think it's done. Christopher Schmidt merged all outstanding Fusion-related changesets. Thanks Christopher!
This particular issue was already fixed in 1.43 :) I just merged the recent changes which Steven Watanabe made during the bug sprint. See changesets 61596-61599 and 63560 for more information: https://svn.boost.org/trac/boost/changeset?reponame=&new=61599&old=61596 https://svn.boost.org/trac/boost/changeset/63560/branches/release/boost/fusi... -Christopher
On Monday 05 July 2010 11:36:54 Christopher Schmidt wrote:
Is this done for 1.44? Or will this be too late once again?
I think it's done. Christopher Schmidt merged all outstanding Fusion-related changesets. Thanks Christopher!
This particular issue was already fixed in 1.43 :) I just merged the recent changes which Steven Watanabe made during the bug sprint. See changesets 61596-61599 and 63560 for more information:
Thank you. Regards, Ravi
participants (6)
-
Beman Dawes -
Christopher Schmidt -
Eric Niebler -
Joel de Guzman -
Ravi -
Tobias Schwinger