On Fri, Dec 12, 2014 at 3:56 PM, Bartosh, Eduard <[email protected]> wrote: >> > My proposal so far was to start with what we have, look at how it works >> and then enhance if needed. Does it make sense for you?
>> 2/ It would be nice to have a cron job that fetch and upload git tags from >> upstream to avoid use to force/workaround theirs (from sandbox/) in their >> .gbs.conf (but we can work that way for now) > Can you elaborate a bit? I'm not sure I follow. 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%2Fconference2014%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 may we push a RFC in dev list 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
