- I'm happy to release the language packs with an Apache 2.0 license. - It looks like there's quite a bit of paperwork involved with the release. Is anyone available to help out with this or even head it up?
- We ran into a hitch building language packs, but have resumed and most of them are almost done. We should have over 60. - Meanwhile the world is changing and the neural approach is becoming more and more obviously the right thing to do. I have some ideas on how this fits in to Joshua which I'll send out in another email. matt > On Oct 16, 2016, at 4:40 PM, lewis john mcgibbney <lewi...@apache.org> wrote: > > Hi Matt, > I like the sound of this :) > > On Fri, Oct 14, 2016 at 9:25 AM, < > dev-digest-h...@joshua.incubator.apache.org> wrote: > >> >> From: Matt Post <p...@cs.jhu.edu> >> To: dev@joshua.incubator.apache.org >> Cc: >> Date: Thu, 13 Oct 2016 12:58:47 -0400 >> Subject: Joshua 6.1 >> Hi folks, >> >> I think I'm going to do the 6.1 release tomorrow. Any objections? >> > > No none at all! > > >> >> Along with the release will be about 60 language packs for a large range >> of languages. These will be released early next week and will be built on >> BerkeleyLM, so that there are no external dependencies. >> > > Sounds grand. As stated, it would be really cool if these could also be > ALv2.0 licensed. > > >> >> I'd like to push out the release quietly until the language packs are >> ready, uploaded, and linked. >> > > Cool. > > >> >> Is there anything I need to know to do an Apache release? >> >> > Yes a few things. You can see the incubator release checklist at > http://incubator.apache.org/guides/releasemanagement.html#check-list > There is also some more general documentation available at > http://incubator.apache.org/guides/graduation.html#releases, which will > eventually lead you to the release check list anyways. > If you have any issues then lets hash them out on this thread. Please note > that we need to review and VOTE prior to anything being pushed. We then > need to go to the Incubator PMC to get wider approval before shipping the > release. This 'can' be a bit painful... however from experience, if we 1) > document the release management procedure on our wiki, and 2) iron out any > issues within dev@joshua before we go to general@incubator then I am sure > we will not encounter too many issues. > Lewis
