> >> 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%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. This approach looks more straightforward and logical from my point of view. To avoid overloading our build farm we can start processing changes from one profile or from the list of developers and see how it goes. We can also introduce some keyword to add to commit messages if developer wants to build the change on the farm. > may we push a RFC in dev list now ? Let's discuss above proposal first, ok? 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
