Ed, While we use Oomph in the lab (thanks for the tool!), I can't use Oomph for SDK development, and also Oomph leads to problems where occasional change of some preference leads to the "automatically" wrong setup. Oomph can't fully resolve the "human" factor.
But also assuming all the preferences are set, Oomph still can't solve the problem of not properly reviewing patches or selecting the right API problem fix. So no, Oomph is not a silver bullet here. Kind regards, Andrey Loskutov Спасение утопающих - дело рук самих утопающих https://www.eclipse.org/user/aloskutov > Gesendet: Donnerstag, 09. Mai 2019 um 10:00 Uhr > Von: "Ed Merks" <ed.me...@gmail.com> > An: platform-dev@eclipse.org > Betreff: Re: [platform-dev] API changes in SDK > > Andrey, > > Perhaps folks should rather consider consistently using the same > automated setup so that everyone consistently see the same thing as > everyone else. That's the purpose of the Oomph setup: to avoid all the > manual steps you describe here. > > Regards, > Ed _______________________________________________ platform-dev mailing list platform-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
