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 <[email protected]>
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: [email protected]
To contact the owner, e-mail: [email protected]
