10511 2016-10-27 19:16:04 +0000 Patchwork production instance code base must point to git.yp.org repo 2017-12-06 17:13:25 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchwork 2.3 x86 Multiple RESOLVED FIXED High enhancement 2.3 M1 10509 1 leonardo.sandoval.gonzalez mhalstead bluelightning jose.a.lamego mhalstead --- --- No (bug/feature does not impact docs) oldest_to_newest 67662 0 leonardo.sandoval.gonzalez 2016-10-27 19:16:04 +0000 Currently, the main patchwork instance points to github (Damien's repo). Instead, the instance should point to the git.yp.org repo to be created by https://bugzilla.yoctoproject.org/show_bug.cgi?id=10509 68049 1 mhalstead 2016-11-07 22:00:13 +0000 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? 68055 2 leonardo.sandoval.gonzalez 2016-11-07 23:17:59 +0000 (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 68131 3 jose.a.lamego 2016-11-08 17:46:56 +0000 Michael, please update as per Leonardo's previous comment. 68144 4 mhalstead 2016-11-08 18:18:26 +0000 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. 68147 5 mhalstead 2016-11-08 18:29:58 +0000 Commit specified is deployed on https://patchwork.openembedded.org/ while waiting for tag. 68148 6 leonardo.sandoval.gonzalez 2016-11-08 18:39:52 +0000 (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 68149 7 mhalstead 2016-11-08 18:53:11 +0000 Deploy moved to release tag.