Yes, helpful to re-enter, reopen, or just add new comments. And, no, don't just assume all will be well :)
For example, since 144022 was not "dupped" on 128041, and, I assume, you have
verified that it is indeed not working, then a reminder with all the relevent related bugs might be helpful. Similarly, occasionally bugs get fixed, and
we forget to update the bug. So, if you confirm it is now working, a comment in the bug to that effect is also very helpful.
Each team is a little different, but most keep the streams in synch on a daily basis, most of the time.
Thanks,
| "Todd Williams"
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 05/26/2006 11:44 PM
|
|
All,
I've begun to notice a number of bugs in WTP 1.5RC3 that are similar to some
that have been resolved as FIXED in the 1.0.x codebase. An example of one
such bug I've opened is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=144022, which is in 1.5RC3,
but was fixed as https://bugs.eclipse.org/bugs/show_bug.cgi?id=128041 in the
1.0.x codebase.
Is there a process and timeline for merging all fixes from the 1.0.x branch
into 1.5 during the RC timeline? Is it helpful to reenter bugs as they're
found against 1.5 if they haven't made it into the public builds yet, or
should I just assume that all fixes for 1.0.x will make it into 1.5
eventually? And, if that's the case when is "eventually" / how long should
I wait to confirm that? (for example "the first public RC after the PR is
FIXED in the 1.0.x codebase?).
Thanks,
Todd
________________________
Todd E. Williams
VP - Technology
Genuitec, LLC
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
