Hello everyone, I smoke tested the alpha version of the CLI tool on ubuntu and windows. So I found the following issues: https://issues.apache.org/jira/browse/IGNITE-13914 https://issues.apache.org/jira/browse/IGNITE-13924 https://issues.apache.org/jira/browse/IGNITE-13921 https://issues.apache.org/jira/browse/IGNITE-13922 https://issues.apache.org/jira/browse/IGNITE-13920
On Sun, Dec 27, 2020 at 2:18 AM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Folks, > > I've created a version in Jira and a Wiki page for the alpha release: > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0.0-alpha1 > > Based on the scope described earlier, all code changes are completed - only > documentation is left. Code freeze starts now - only bug fixes are > permitted. > > I'm planning to start the vote next week, presumably on Tuesday. > > -Val > > On Tue, Dec 22, 2020 at 9:56 AM Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Ivan, > > > > Yes, you are correct - no tables, caches, compute or any other major > > features will be available. > > > > Alpha releases are generally produced in the middle of the development > > process for internal testing. In my view, that's exactly what the > upcoming > > release is, but let me know if you have a better naming in mind. > > > > -Val > > > > On Tue, Dec 22, 2020 at 1:56 AM Ivan Pavlukhin <vololo...@gmail.com> > > wrote: > > > >> Hi, > >> > >> Is it right that suggested Alpha will not be able to perform any > >> operations with data (tables, caches)? In that case Alpha naming > >> confuses me. Actually do not know how such kind of demo releases > >> should be attributed. > >> > >> 2020-12-21 20:42 GMT+03:00, Denis Magda <dma...@apache.org>: > >> > Certainly, the end of Jan is more realistic and reasonable. Let's talk > >> this > >> > out offline and then put a session on the virtual meetup's schedule. > >> > > >> > - > >> > Denis > >> > > >> > > >> > On Sun, Dec 20, 2020 at 4:35 PM Valentin Kulichenko < > >> > valentin.kuliche...@gmail.com> wrote: > >> > > >> >> Hi Denis, > >> >> > >> >> Sure, that's a great idea! I'm thinking, however, that it makes sense > >> to > >> >> take a pause after the release and let people try it out on their own > >> so > >> >> that the experience is as close to real-life as possible. How about > >> >> closer > >> >> to the end of January? > >> >> > >> >> -Val > >> >> > >> >> On Fri, Dec 18, 2020 at 8:53 PM Denis Magda <dma...@apache.org> > wrote: > >> >> > >> >> > Hi Val, > >> >> > > >> >> > That's the pace, I'll be happy to play with the alpha and share > >> >> > feedback. > >> >> > Also, what if we arrange a community gathering after the holidays > to > >> >> > demonstrate what alpha does and get more details from the involved > >> >> > contributors on what's coming next? > >> >> > > >> >> > As for the release process, yes, that needs to be a formal vote as > >> long > >> >> as > >> >> > you're publishing artifacts to Maven and updating the website with > >> >> > references to the binaries and documentation pages. > >> >> > > >> >> > > >> >> > - > >> >> > Denis > >> >> > > >> >> > > >> >> > On Fri, Dec 18, 2020 at 6:13 PM Valentin Kulichenko < > >> >> > valentin.kuliche...@gmail.com> wrote: > >> >> > > >> >> > > Igniters, > >> >> > > > >> >> > > The repository for Ignite 3.x [1] was created less than a month > >> ago, > >> >> and > >> >> > we > >> >> > > already have several merged pull requests. Many thanks to > everyone > >> >> > involved > >> >> > > for the contributions! > >> >> > > > >> >> > > Currently, we have the following functionality available in the > >> main > >> >> > > branch: > >> >> > > > >> >> > > - New configuration framework which is compatible with the > HOCON > >> >> > format. > >> >> > > - The “ignite-runner” module, which currently incorporates the > >> >> > > aforementioned configuration framework and REST endpoints to > >> >> interact > >> >> > > with > >> >> > > the framework. > >> >> > > - The first version of the unified CLI tool. > >> >> > > > >> >> > > This set of features does not include any actual Ignite APIs. > >> >> > > However, > >> >> it > >> >> > > clearly demonstrates the basic mechanics of how the product will > be > >> >> > > installed and upgraded, how the user will interact with it, etc. > I > >> >> would > >> >> > > like to use this to gather feedback from the community in the > early > >> >> > stages. > >> >> > > > >> >> > > To make sure the experience is as close to real life as > possible, I > >> >> want > >> >> > to > >> >> > > deliver what we have as an alpha release, meaning that all the > >> >> > > required > >> >> > > binaries will be deployed on the website and in Maven. There will > >> >> > > also > >> >> be > >> >> > > some basic documentation describing how to install and use the > >> >> > > product. > >> >> > > This way, anyone will be able to download the product and try it > >> out. > >> >> > > > >> >> > > My main question here -- do we need a formal vote for such a > build? > >> >> > > Or > >> >> it > >> >> > > can be treated as a release candidate? > >> >> > > > >> >> > > Any other thoughts? > >> >> > > > >> >> > > [1] https://github.com/apache/ignite-3 > >> >> > > > >> >> > > -Val > >> >> > > > >> >> > > >> >> > >> > > >> > >> > >> -- > >> > >> Best regards, > >> Ivan Pavlukhin > >> > > >
