HI, > -----Original Message----- > <[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
I propose to trigger developer builds on the changes pushed for review. > wont work on rebased changes (ie: version bump) so version jump and > pushing tags Is a task only maintainer can do so far... > If we trigger builds the way I propose there will be not need in any kind of tagging. > As said before it can be hacked eventually by setting tag's revision in > sanboxed .gbs.conf Now I don't follow you. > We can talk online too btw the obs is pretty loaded for now ... Yes, gcc upgrade caused massive rebuild in all target and prerelease projects. The fact that there were more than 100 prerelease projects added to this load a lot. We can talk on irc if you prefer or continue here. Regards, Ed --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
