On Tuesday, August 18, 2015 08:57:16 AM Josef Reidinger wrote: Hi,
I can do it on jenkins side. In general what is needed:
1) modify jenkins ( river to point to new branch for given packages ) 2a) create SP1 branch 2b) modify in SP1 branch Rakefile to use correct defaults targets
And it should be everything needed. To make your life even easier, I create in past script that do 2 even easier - https://github.com/yast/yast-devtools/blob/master/ytools/yast2/create_mainte nance_branch just modify constant on top of file to fit and then run it in git clone root
Frankly, I lost easily with IBS/OBS but I guess that maybe we could get into troubles here. Although we have a different branch for those packages, they're submitted to Devel:YaST:Head on IBS. Or do we have a different project for them? The problem could be that AutoYaST integration tests will broke in the near future as we use Devel:YaST:Head repository (and branched yast2-country, for example, is not intenteded to be included in SP1). Or will be those packages submitted to another project? Regards, Imo -- Imobach González Sosa YaST Team at SUSE LINUX GmbH