I also like the idea of a version 2.0 very much. Personally, I would be very happy to move bastion from katello to foreman so that it's possible to create modern, angular js components within foreman. One more reason to do this is, because I think foreman should be the structure, the base "framework" all other plugins like katello can live in. Just my thoughts...
Best regards, Bernhard Suttner ATIX - The Linux & Open Source Company https://www.atix.de -----Ursprüngliche Nachricht----- > Von:Lukas Zapletal <[email protected]> > Gesendet: Mittwoch 29 November 2017 14:18 > An: foreman-dev <[email protected]> > Betreff: Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0 > > > Bikeshedding about SemVer aside, I'm good with doing a 2.0 release in > > the near future, but *please* lets use it to deprecate / drop stuff we > > no longer want to maintain. Otherwise there's no real point to it. > > I agree we can take this "opportunity" to drop some deprecated things > like V1 API, but I don't see many other things. We are pretty good in > deprecating things using our "two releases" rule which should be > followed no matter if we bump major version or not. > > Let's not block 2.0 with any feature, I wrote the reasons, if we fit > in some deprecation work why not. But's let's agree on 2.0 timeframe > regardless of any planning. > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
