[yast-devel] how to submit to CaaSP2.0
Hi, I just would like to share the best practive for CaaSP2.0 package submission. 1. We would like to prevent mess with CaaSP1.0 in git, so we do development in SLE12-SP3 branch 2. changes for CaaSP2.0 is not reason to create maintenance request so do *not* use osc:sr 3. instead use `rake osc:commit` to submit to our SP3 devel and then osc -A https://api.suse.de/ sr Devel:YaST:SLE-12-SP3 <yast2-country> SUSE:SLE-12-SP3:Update:Products:CASP20 where yast2-country replace with module you want to submit. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11.09.2017 09:24, Josef Reidinger wrote:
Hi, I just would like to share the best practive for CaaSP2.0 package submission.
1. We would like to prevent mess with CaaSP1.0 in git, so we do development in SLE12-SP3 branch
Is this really a good idea? This will mean that we will develop that new product in the branch of an already released and supported product. Yes, of course we always hope that we don't break anything when we develop the new product, but I fear that this is just wishful thinking; there will be bugs. Do we really want all those bugs to hit the paying customers of SLE-12 SP3, too?
2. changes for CaaSP2.0 is not reason to create maintenance request so do *not* use osc:sr
But what if there really is a maintenance request while we are still developing CaaSP 2.0 ? If we work in the same branch, how can we keep that ongoing (and UNTESTED!) stuff from CaaSP 2.0 development and the SP3 maintenance request apart? I think this is an accident (more likely, a major train wreck) waiting to happen. IMHO we should create a new branch for CaaSP 2.0 and merge the changes once that product is shipped. Kind regards -- Stefan Hundhammer <shundhammer@suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
V Mon, 11 Sep 2017 14:37:31 +0200 Stefan Hundhammer <shundhammer@suse.de> napsáno:
On 11.09.2017 09:24, Josef Reidinger wrote:
Hi, I just would like to share the best practive for CaaSP2.0 package submission.
1. We would like to prevent mess with CaaSP1.0 in git, so we do development in SLE12-SP3 branch
Is this really a good idea?
This will mean that we will develop that new product in the branch of an already released and supported product. Yes, of course we always hope that we don't break anything when we develop the new product, but I fear that this is just wishful thinking; there will be bugs. Do we really want all those bugs to hit the paying customers of SLE-12 SP3, too?
Well, short answer it was decided this way. In the end it also should end up there, same as for caasp1.0. Another point is that there is minimum changes and we also have maintenance QA which is what customers pay for having certain quality.
2. changes for CaaSP2.0 is not reason to create maintenance request so do *not* use osc:sr
But what if there really is a maintenance request while we are still developing CaaSP 2.0 ? If we work in the same branch, how can we keep that ongoing (and UNTESTED!) stuff from CaaSP 2.0 development and the SP3 maintenance request apart?
It will be included in that change. And if needed it will be tested by maintenance QA, but as I write changes for caasp is currently minimal and majority is in yast2-caasp package and only minimal backward compatible change in yast2-country.
I think this is an accident (more likely, a major train wreck) waiting to happen. IMHO we should create a new branch for CaaSP 2.0 and merge the changes once that product is shipped.
That was extreme pain last time. I know that you just did storage, but I do merge for rest of packages and it also complicates any fix that have to go to another branch so instead of e.g. SP2 -> SP3 -> master you have additional git branch, which you have to update, submit and so on.
Kind regards
Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
Josef Reidinger -
Stefan Hundhammer