Hi Everyone, This is just a reminder that we are trying very hard to get to a release point. Aleksey has been making an incredible effort in managing this release, so please do everything in your power to be responsive to his requests. Being proactive is even better, so if you can, see if there are any regressions you can fix. Thanks, -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
"David Abrahams" <dave@boost-consulting.com> wrote in message news:u8yayplx9.fsf@boost-consulting.com... | | Hi Everyone, | | This is just a reminder that we are trying very hard to get to a | release point. Aleksey has been making an incredible effort in | managing this release, so please do everything in your power to be | responsive to his requests. Being proactive is even better, so if you | can, see if there are any regressions you can fix. I new to this procedure, so tell if we should mark all remaining failures as expected failures or just leave it? -Thorsten
"Thorsten Ottosen" <nesotto@cs.auc.dk> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:u8yayplx9.fsf@boost-consulting.com... | | Hi Everyone, | | This is just a reminder that we are trying very hard to get to a | release point. Aleksey has been making an incredible effort in | managing this release, so please do everything in your power to be | responsive to his requests. Being proactive is even better, so if you | can, see if there are any regressions you can fix.
I new to this procedure, so tell if we should mark all remaining failures as expected failures or just leave it?
I guess any failures that you don't think you're going to fix should be marked as expected. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams writes:
"Thorsten Ottosen" <nesotto@cs.auc.dk> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:u8yayplx9.fsf@boost-consulting.com... | | Hi Everyone, | | This is just a reminder that we are trying very hard to get to a | release point. Aleksey has been making an incredible effort in | managing this release, so please do everything in your power to be | responsive to his requests. Being proactive is even better, so if you | can, see if there are any regressions you can fix.
I new to this procedure, so tell if we should mark all remaining failures as expected failures or just leave it?
I guess any failures that you don't think you're going to fix should be marked as expected.
... with a note explaining the cause and, if applicable, user impact. -- Aleksey Gurtovoy MetaCommunications Engineering
participants (3)
-
Aleksey Gurtovoy -
David Abrahams -
Thorsten Ottosen