"Development of Percona Server" mentions Bazaar
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.5 |
Triaged
|
Low
|
Borys Belinsky | |||
| 5.6 |
Triaged
|
Low
|
Borys Belinsky | |||
| 5.7 |
Triaged
|
Low
|
Borys Belinsky | |||
Bug Description
https:/
"At Percona we use Bazaar for source control"
"For Percona Server, we have two current bzr branches on which development occurs: 5.1 and 5.5. As Percona Server is not a traditional project, instead being a set of patches against an existing product, these two branches are not related. That is, we do not merge from one to the other. To have your changes in both, you must propose two branches: one for 5.1 version of patch and one for 5.5."
"Making a change to a project
In this case we’re going to use percona-xtrabackup as an example. workflow is similar for Percona Server, but patch will need to be modified both in 5.1 and 5.5 branches.
bzr branch lp:percona-xtrabackup featureX (where ‘featureX’ is a sensible name for the task at hand)
(developer makes changes in featureX, testing locally)
Developer pushes to lp:~username/percona-xtrabackup/featureX"
"Merging approved branches" section is probably not suitable for public docs anyway
"Resubmitting a merge request" is Launchpad-specific, we are on Github.
"Making a release" is bzr-specific.
"Jenkins" section has bzr mentions throughout.
| tags: | added: doc |
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/