[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dsdp-tm-dev] Backporting fixes to 3.0.2
|
Dear
Committers,
our list of bugs to
backport to 3.0.2 grows longer each day. May I encourage you
to think twice
whether you actually need something backported, since it's effort
for
everyone. For instance, the "Symbolic link shown twice in table view"
issue
doesn't seem all that critical to me (but then it's mostly your effort
so it should
also be your decision).
My query also shows
3 bugs still assigned to targetmilestone 3.0 -- Xuan and
Dave's, please
update as appropriate.
May I also remember
you that you actually need to *release* backported fixes
into the Mapfile on the branch in order to show up in any M-builds. Attached
are
(again) instructions for backporting.
Query: all open bugs assigned to 3.0.x target
milestones
12 bugs found.
| ID
|
Sev
|
Pri
|
Assignee
|
Status
|
Resolution
|
OS
|
TargetM
|
Summary
|
| 250139 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport [dnd] Remote to local overwrite copy does not work |
| 250140 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport [usability] Save conflict dialog appears when saving files in
the editor |
| 250458 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport [dstore] Remote search doesn't find the right result |
| 251163 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport Work Offline requires being selected twice to turn on Offline
Mode |
| 251268 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport Go Into on a filter then back brings up prompt of any
expanded promptable filter |
| 251397 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport Expand New Connections |
| 251551 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport [dstore] Pasting local folder to remote does not work in some
case |
| 251574 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport "Overwrite All" button text truncated in Korean and Chinese
versions |
| 251713 |
nor |
P3 |
dmcknigh@xxxxxxxxxx |
NEW |
|
All |
3.0.2 |
Backport [dstore] Multiple copies of symbolic link file show in Table
view |
| 224346 |
nor |
P3 |
dsdp.tm.rse-inbox@xxxxxxxxxxx |
NEW |
|
Wind |
3.0 |
BIDI3.4:HCG Wrong display for Filter string in a mirrored Eclipse
|
| 199276 |
min |
P4 |
xuanchen@xxxxxxxxxx |
NEW |
|
Wind |
3.0 |
[archives] Creating a folder with an archive extension causes errors.
|
| 214402 |
nor |
P3 |
xuanchen@xxxxxxxxxx |
ASSI |
|
Wind |
3.0 |
Remove Selected Matches in Remote Search view doesn't work on line
matches |
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
--- Begin Message ---
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Wed, 8 Oct 2008 18:50:56 +0200
- Thread-index: AckpYuFjdFskJyHDSce7MAEu2UFqpAAATFSA
- Thread-topic: putting fixes into 3.0.2
Hi Dave,
I'm not a big fan of a patch release since that adds
additional
overhead (creating a patch feature, modifying update
site etc),
but the question of how we release can be deferred anyways
since the process upto the release is the same:
-
For the
bug that needs to go into the 3.0.x release, make a clone of the corresponding
3.1 fixed defect in bugzilla, subject: "backport..." and target milestone
3.0.2
-
Be sure
to have a separate workspace for RSE 3.0.x work. Don't
try re-using your HEAD workspace. I recommend starting with a clean Eclipse
SDK 3.4.1, with the releng.tools plugin installed. Import
your Eclipse Preferences if you want (export from your main HEAD workspace,
then import into the 3.0.x workspace). Then, import the
"rse-all-committer.psf" project set. Then, pick the
org.eclipse.rse.build project and do Team > Switch to
another Branch > R3_0_maintenance. Then, select all your
projects and do Team > Replace with >
Released.
-
In your
3.0.x RSE workspace, perform the backport. Dont' forget that for any
plugin/feature which you modify, you will need to "Team > Branch" in order
to create its "R3_0_maintenance" maintenance branch.
Then, apply patch from the original 3.1 bug, or Compare with > HEAD to
get the changes in. Also, don't forget setting version numbers of plugins and
features to 3.0.2.qualifier where needed (all features which INCLUDE the
change -- typically "rse.sdk" + "rse" + "rse.core". Attach a patch with your
backport to the backport bug.
-
Have a
second committer review your backport patch.
-
If OK,
commit and release your backport. Given that you have a 3.0.x RSE workspace,
your mapfile project ("org.eclipse.rse.build") is associated with the
"R3_0_maintenance" branch already.
-
Mark
the "backport" bug fixed.
-
Once
your desired changes are released, we can fire an M-build at any time, which
your product teams can pick up for verification.
-
If we
are happy with the M-build we can think about if, when, and how we want to
release it.
I
believe that you should be able to walk through these steps on your
own,
but if you have any questions just let me know.
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
Hi Martin,
A couple of the IBM product teams expressed wanting to
put fixes for defects into earlier releases.
For the first one, the
team wants to make sure it gets into the 3.0.2 release.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=248922
How
we do we make sure that the fix goes into 3.0.2?
For the second one,
the team wants to make sure it gets into a release before the end of december
(an early 3.0.2 or a 3.0.1 patch?).
https://bugs.eclipse.org/bugs/show_bug.cgi?id=249544
What is the process for building a patch
release?
Thanks,
____________________________________
David
McKnight
Phone: 905-413-3902 , T/L: 969-3902
Internet:
dmcknigh@xxxxxxxxxx
Mail:
D1/YFY/8200/TOR
____________________________________
--- End Message ---
