Mailinglist Archive: yast-devel (63 mails)

< Previous Next >
Re: [yast-devel] SLE12 GIT branch? - match contents
On 2.9.2014 10:47, Martin Vidner wrote:
On Thu, Aug 28, 2014 at 09:58:40AM +0200, Lukas Ocilka wrote:
- Should we create the branches globally or should we leave that on
the respective

globally. To guarantee that all repos are in same "shape"

How I see it, we should make sure that such a branch contains
everything that made it to SLE 12, but nothing more. I've seen in
the past, that branch did not contain everything or contained more
commits than got to a particular product.

Do you have examples of mismatches, to remind us of the pitfalls to
avoid? So far I interpret this as "remember to submit from the right
branch" which Jenkins should automate just fine.

No I don't have any. These were deep in the past and I don't remember the details anymore. This would need a real detective and lots of time, that we don't have right now.

A stronger requirement is "distinguish SLE12-GA from maintenance",
which would be implemented by tags. Automatict tagging is not
working now.

If I understand it correctly, the branch for SLE12-GA and maintenance will be the same. Then tagging is the only way.

PLS, also remember that I'd like to branch SLE12-SP1 maintenance from "master" to keep the development of master/openSUSE/SLE12-SP1 as close as possible - as long as possible.



Lukas Ocilka, Systems Management (Yast) Team Leader
Cloud & Systems Management Department, SUSE Linux
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups