I think you have outlined this pretty well. Adding new architecture isn't much different than adding a new component: the set of requirements is the same. Ideally, not only _some_ smokes tests should work, but the test matrix should be the same as with other platforms, already supported in the stack.
Please keep these discussions on the list to give the rest of the community a chance to participate. (crossposting to dev@ as well) Cheers, Cos On Mon, Jan 18, 2016 at 04:36PM, Olaf Flebbe wrote: > hi > > yep, since nobody else jumped in: > a few mails bouncing back and forth. > > - in order to get a new arch in officially, not only compilation but at least > the smoke tests must work. > - I encouraged to upstream and submit further contributions > - i adressed the problem where to store the binary artifacts of non x86 archs > > roman, perhaps we can discuss at fosdem how to handle this kind of requests > in future > > olaf > > > > > > Am 17.01.2016 um 23:19 schrieb Roman Shaposhnik <[email protected]>: > > > >> On Fri, Jan 1, 2016 at 4:47 PM, MrAsanjar . <[email protected]> wrote: > >> Hi Olaf, > >> Without your help this would not have been possible Bravo :) > >> We (IBM) are planing to expand our collaboration with BigTop community for > >> 2016. > >> I will be out hiking in Costa Rica for the next two weeks, but planing to > >> setup > >> a meeting with BigTop community leaders to further discuss our > >> collaboration, whom should I invite to the meeting? > > > > I am curious -- has that conversation happened yet? > > > > Thanks, > > Roman.
signature.asc
Description: Digital signature
