Hi - > On Oct 4, 2020, at 5:52 PM, Nikita Ivanov <[email protected]> wrote: > > NLPCraft-ers, > I've looked at the velocity of the development on the project and the > frequency of the releases and it appears to me that they don't sync up very > well. The project is still very young and the pace of > changes/fixes/improvements greatly outpaces the pace of official ASF > releases. However, it's unclear if master branch (or other branch) > is stable and can be used for play-around... > > As with many other ASF projects I propose to consider doing ASF-unofficial > nightly or (less frequent) community builds and make them available on the > website.
The project can make snapshots from CI available, but not from the website. http://www.apache.org/legal/release-policy.html#publication http://www.apache.org/legal/release-policy.html#host-rc The location may be given to community members on the mailing list when they ask. > This will allow many users to simply try some of the experimental > features or provide quick fixes/feedback when necessary without a need for > the NLPCraft team to cut an official ASF release and go through the process > every time for every small fix or feature iteration. We will, obviously, > continue to release official ASF releases once we accumulate enough "meat" > for such a release. > > At Apache Ignite we've decided to do Community Edition (built and hosted by > GridGain Systems) for pretty much exactly these reasons. These can be problematic. https://infra.apache.org/release-distribution.html#unreleased Community Editions that are called Apache NLPCraft (incubating) must be based on Released Source Code. GridGain community edition is not Apache Ignite, it’s not the same. I’m unclear what is going on here, but that is an issue for the Ignite PMC. https://www.gridgain.com/products/software/community-edition > > Thoughts, comments? Regards, Dave > -- > Nikita Ivanov
