Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox/Meeting Minutes/20110822"
< Equinox | Meeting Minutes
Line 1: | Line 1: | ||
== Attendees == | == Attendees == | ||
− | * | + | * DJ |
+ | * Ian | ||
+ | * Tom | ||
+ | * John | ||
+ | * Pascal | ||
== Agenda == | == Agenda == | ||
− | * 3.7.1 ramp down | + | * 3.7.1 ramp down RC2 |
* Ongoing Juno Plan | * Ongoing Juno Plan | ||
* Console | * Console | ||
+ | * Git repo branching strategy | ||
+ | |||
+ | == 3.7.1 ramp down == | ||
+ | * Most p2 bugs still open should be postponed | ||
+ | ** bug 349628 - Check for updates will not work if there is an invalid repo. Must have a perfect set of repos to have things work. | ||
+ | ** bug composite repo issue | ||
+ | |||
+ | == Juno Plan == | ||
+ | * Pascal, DJ and Ian to fill in the p2 plan. | ||
+ | |||
+ | == Console == | ||
+ | * Tom to review the console stuff and plans to integrate into M2, time permitting. | ||
+ | |||
+ | == Git repo branching strategy == | ||
+ | * committer branches. | ||
+ | ** We should use a branch naming convention for branches pushed upstream by committers. | ||
+ | ** Perhaps <committer.id>/<topic> can be used. | ||
+ | ** Basically want a way to quick determine what committer created the upstream branch and why. | ||
+ | ** Should bring up the topic to the AC and see what other projects are doing. |
Latest revision as of 16:00, 22 August 2011
Attendees
- DJ
- Ian
- Tom
- John
- Pascal
Agenda
- 3.7.1 ramp down RC2
- Ongoing Juno Plan
- Console
- Git repo branching strategy
3.7.1 ramp down
- Most p2 bugs still open should be postponed
- bug 349628 - Check for updates will not work if there is an invalid repo. Must have a perfect set of repos to have things work.
- bug composite repo issue
Juno Plan
- Pascal, DJ and Ian to fill in the p2 plan.
Console
- Tom to review the console stuff and plans to integrate into M2, time permitting.
Git repo branching strategy
- committer branches.
- We should use a branch naming convention for branches pushed upstream by committers.
- Perhaps <committer.id>/<topic> can be used.
- Basically want a way to quick determine what committer created the upstream branch and why.
- Should bring up the topic to the AC and see what other projects are doing.