| Summary: | Merge release branches before 0.6 | ||
|---|---|---|---|
| Product: | [Tools] Linux Tools | Reporter: | Andrew Overholt <overholt> |
| Component: | Project | Assignee: | Linux Distros Inbox <linux.distros-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | akurtakov |
| Version: | unspecified | ||
| Target Milestone: | 0.8.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Andrew Overholt
I've merged the 0.7 release branch in my test repository: https://github.com/overholt/org.eclipse.linuxtools I'll work backwards from 0.6 as time goes by but earlier versions get decreasingly important so they're not time-sensitive. As such, I'm not going to have this block our move to git. FWIW, the procedure I used for stable-0.7 was to git merge each R0_7_0 tag and branch but I may move to git cherry-pick for 0.6 and others as it looks like it may be easier. Should we close this bug now that we moved to git entirely? I've merged the 0.7, 0.6, and 0.5 branches. I was thinking of keeping this open in case someone cares about <= 0.4 but I guess we can allow bugs to be opened in that case. |