[yast-devel] Modernizing AutoYaST blog post

2020-04-30 Thread Imobach Gonzalez Sosa
Hi all, We have just published a blog post summarizing some of the ideas related to the "modernizing AutoYaST" initiative. https://yast.opensuse.org/blog/2020-04-30/modernizing-autoyast Not all ideas are there and it is possible that some of them never get implemented. But it is a nice picture o

Re: [yast-devel] Meeting about changes to xml schema

2020-04-30 Thread Imobach Gonzalez Sosa
El jue, 30-04-2020 a las 13:39 +0200, josef Reidinger escribió: > Yes, it is good point. Question to imo how it is exported by autoyast > clone, as it is string and not disksize element. So unless storage > use some kind of hack, I think it is not possible to get such type > automatic. Of course u

Re: [yast-devel] Meeting about changes to xml schema

2020-04-30 Thread Imobach Gonzalez Sosa
El jue, 30-04-2020 a las 12:44 +0200, josef Reidinger escribió: > On Thu, 30 Apr 2020 12:40:39 +0200 > josef Reidinger wrote: > > > Hi, > > after modifying xml parser, it appears that our relax ng schema is > > too strict to allow having type for every xml element. So we should > > discuss possib

Re: [yast-devel] Protected branches at GitHub?

2016-09-16 Thread Imobach Gonzalez Sosa
On 16/09/16 09:12, Ladislav Slezak wrote: > Hi, Hi, > I have noticed a quite interesting GitHub feature which allows to protect > the specified branches. A short summary from [1]: > > A protected branch: > - Can't be force pushed > - Can't be deleted > - Can't have changes merged into it until requ

Re: [yast-devel] Versioning the SLE-12-SP2-CASP branch

2017-02-03 Thread Imobach Gonzalez Sosa
On 03/02/17 10:44, Ancor Gonzalez Sosa wrote: > Josef and me are discussing how to version stuff in CASP vs SP2 when > both branches are getting different subset of changes. Always taking > into account that, when CaaSP is released, the SP2 branch should contain > all the changes and the CASP bra

Re: [yast-devel] Wizard buttons mess

2017-02-08 Thread Imobach Gonzalez Sosa
On 08/02/17 09:24, Josef Reidinger wrote: > Hi developers, Hi Josef, > I was again hit by issue with enabling disabling buttons in wizard and > also its renaming and having six parameters to all wizard dialogs are > wrong from API POV. > > So what I proposing? > > Create configuration class tha

Re: [yast-devel] Feedback needed! Hack Week project to re-define storage-ng API

2017-02-24 Thread Imobach Gonzalez Sosa
On 02/23/2017 04:45 PM, Ancor Gonzalez Sosa wrote: So please, please, please, take a look to this and give your opinion. https://github.com/yast/yast-storage-ng/pull/169 Hi all, In general, it looks like a really nice improvement. I'll just only some small comments/remarks but LGTM :) = A

Re: [yast-devel] 2nd attempt: do we need a layer between libstorage-ng and (the rest) of YaST?

2017-02-27 Thread Imobach Gonzalez Sosa
On 02/27/2017 07:51 AM, Ancor Gonzalez Sosa wrote: Since the original thread is already ruined with discussions about concrete API design details that were not the main topic of my question, I will try once again from scratch. Do we need a layer between libstorage-ng and (the rest) of YaST? I t

Re: [yast-devel] YaST-related talks/workshops in oSC'17

2017-03-29 Thread Imobach Gonzalez Sosa
Hi all, I've submitted mine too. FORMAT: 30 min talk TITLE: Adding Salt to AutoYaST ABSTRACT: YaST2 Configuration Management is a brand new YaST module which offers integration between AutoYaST and Salt. It's no secret that

[yast-devel] Re: [yast-internal] Version numbers post-SP3 (Factory / SLE-15)

2017-08-09 Thread Imobach Gonzalez Sosa
On 08/09/2017 01:19 PM, Stefan Hundhammer wrote: > > The SP3 branch uses 3.2.x . > > When we keep using 3.2.x in master as well, we need to start using a > fourth digit in that branch: 3.2.x.1 etc. > > Since we are not targeting a new product, we might want to bump one of > the numbers in master

[yast-devel] Re: [yast-internal] Version numbers post-SP3 (Factory / SLE-15)

2017-08-09 Thread Imobach Gonzalez Sosa
Sorry, wrong list. On 08/09/2017 05:02 PM, Imobach Gonzalez Sosa wrote: > On 08/09/2017 01:19 PM, Stefan Hundhammer wrote: >> >> The SP3 branch uses 3.2.x . >> >> When we keep using 3.2.x in master as well, we need to start using a >> fourth digit in that branch