On Tue, Dec 16, 2014 at 10:27 AM, Bartosh, Eduard <eduard.bart...@intel.com> wrote: > HI, > >> -----Original Message----- >> <eduard.bart...@intel.com> 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 > > I propose to trigger developer builds on the changes pushed for review.
Ok I am talking about upstream release tags (upstream/x.y.z or vX.Y.Z etc) not tizen tags >> As said before it can be hacked eventually by setting tag's revision in >> sanboxed .gbs.conf > > Now I don't follow you. see my above quoted message > We can talk on irc if you prefer or continue here. I am RzR on freenode ... later . _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
