| Summary: | Patchwork production instance code base must point to git.yp.org repo | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Component: | Patchwork | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | High | CC: | bluelightning, jose.a.lamego, mhalstead |
| Version: | 2.3 | ||
| Target Milestone: | 2.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 10509 | ||
| Bug Blocks: | |||
|
Description
Leonardo Sandoval Gonzalez
2016-10-27 19:16:04 UTC
Currently we are on commit fc3c66a1ac3e94ce26ca29b4296f1196b869cbac of the freedesktop.org fork. I can point at the new location. Is 855a5db4a2f8761fb12e705cf72cb61581bf95fd current the HEAD of master the correct commit to update to? If so could we tag that to keep track of versions running in production? Are there migrations to run after the code update? Any other work? (In reply to comment #1) > Currently we are on commit fc3c66a1ac3e94ce26ca29b4296f1196b869cbac of the > freedesktop.org fork. I can point at the new location. Is > 855a5db4a2f8761fb12e705cf72cb61581bf95fd current the HEAD of master the > correct commit to update to? No. please update it to c1cea7c880fb2babd36c6eaa2204ed92ef5da843, just push that commit. >If so could we tag that to keep track of > versions running in production? Agree, which tag name do you suggest? simple as 1.0? > > Are there migrations to run after the code update? Any other work? No Michael, please update as per Leonardo's previous comment. 1.0 works but may be confusing given that the parent project has a 1.0.0 (https://github.com/getpatchwork/patchwork/releases) but I don't know if we forked before or after that. Another option is version with the year and month of the release 2016-11 like uninative. Please tag with whatever makes sense to you and let me know when it's ready. Commit specified is deployed on https://patchwork.openembedded.org/ while waiting for tag. (In reply to comment #5) > Commit specified is deployed on https://patchwork.openembedded.org/ while > waiting for tag. Done. Followed your suggestion for naming the tag: http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/tag/?id=2016-11 Deploy moved to release tag. |