(replies inline) On Mon, 06 Aug 2018, Oleg Nenashev wrote:
> Hi all, > > Status update: By now Custom War Packager has been released in 1.0, and > there are also many updates in Evergreen. IMHO it is a good time to get > this story over the fence. Thanks for working to drive this to completion Oleg! Overall I think the document looks great, and as of last Friday I had actually gotten the implementation prepared for the Evergreen backend system (see: https://github.com/jenkins-infra/evergreen/pull/169) which processes the essentials.yaml and prepares the update records needed. I believe the only think which needs to be resolved which is likely just an obsolete part of the example YAML. The root `status` key in the YAML for a "realized" BOM I don't believe we've ever actually used and is worth removing. I wanted to sanity check that with you first though. If you remove that, I think overall this JEP looks good and is just about ready to go. Cheers -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180806224950.GC17800%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
