On Sat, Dec 13, 2014 at 9:25 PM, Bartosh, Eduard <[email protected]> wrote: >> on version bumps I feel it's more convenient to base on git tag from >> upstream repos >> >> see page 32 >> >> https://duckduckgo.com/l/?kh=- >> 1&uddg=http%3A%2F%2Fdownload.tizen.org%2Fmisc%2Fmedia%2Fconfere >> nce2014%2Fslides%2Ftdc2014-tizen-upstream-coop.pdf >> >> >> Maintainer updates to new version >> >> No need for upstream/x.y.z edit “.gbs.conf [general] upstream_branch = >> upstream upstream_tag = libevdev-${upstreamversion} >> >> >> but developer wont be able to push it to git so he can workaround it by >> faking the tag to its branch >> >> ie: >> >> [general] >> upstream_branch = upstream >> upstream_tag = sandbox/$USER/upstream >> >> and when working with pristine tarballs is even worse since he cant push >> upstream/x.y.z tags >> >> but let keep this problem aside >> we can assume developers wont bump versions first >> > > BTW, what if we create developer projects based on changes pushed for review? > This way we won't depend on push rights for tags and all developers can use > this.
I dont follow you wont work on rebased changes (ie: version bump) so version jump and pushing tags Is a task only maintainer can do so far... As said before it can be hacked eventually by setting tag's revision in sanboxed .gbs.conf We can talk online too btw the obs is pretty loaded for now ... -- mailto:[email protected] -- gpg:0x467094BC xmpp:[email protected] https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/ . _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
