On 03/14/2018 09:57 AM, Ladislav Slezak wrote: > Dne 14.3.2018 v 09:45 Ancor Gonzalez Sosa napsal(a): >> On 03/03/2018 01:21 PM, Stefan Koch wrote: > [...] >> I may be wrong, but I guess the normal procedure would be: >> - you create a submit request from your project to YaST:Devel > > Well, we have disabled submit requests to YaST:Head, the contributors > should use pull requests in GitHub instead of OBS SR. > But that does not work for completely new packages...
That's fine for the packages maintained by the YaST team. We really want to do everything based on pull request with code reviews and to avoid people to mess everything up with patches submitted directly to OBS. And I would encourage the same rule/procedure for any yast2-xxx package created and maintained by others. But do we want to enforce that? (encourage < enforce) :-) > I can add it manually to YaST:Head, did somebody do the initial code review? Is the code review needed for packages not maintained or developed by the YaST team if the developer doesn't ask for it? I hope the fact that the package goes into TW via YaST:Devel doesn't imply the YaST team is responsible for it in any way. >> - once your package lives in YaST:Devel, create the SR to Factory > > I can configure the usual automation via Jenkins for that to use > the same process as for the other YaST packages. That would be nice... if Stefan agrees. Stefan, if that's the case and you want to stick to the YaST Team procedures there is a lot to read in http://yast.opensuse.org/guidelines (and I would say there is even more at http://yastgithubio.readthedocs.io/en/latest/README/ since I don't see any mention to Jenkins in the Guidelines page). Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
