Two different Ignite-Versions?
Locked
 
|
Hi guys,
I recently noticed that there are two versions of Apache Ignite around: . v1.0.0: https://ignite.incubator.apache.org/download.html . v1.0.2: http://www.gridgain.com/download/editions/ Any clarification? ;) Thanks Markus |
Re: Two different Ignite-Versions?
|
We are currently resolving this confusion. The 1.0.2 version is for the
GridGain Community Edition powered by Apache Ignite, which can be found here: http://www.gridgain.com/download/editions/ D. On Mon, Apr 27, 2015 at 12:01 AM, Markus Wiesenbacher < [hidden email]> wrote: > Hi guys, > > > > I recently noticed that there are two versions of Apache Ignite around: > > > > . v1.0.0: https://ignite.incubator.apache.org/download.html > > . v1.0.2: http://www.gridgain.com/download/editions/ > > > > Any clarification? ;) > > > > Thanks > > Markus > > |
AW: Two different Ignite-Versions?
|
|
You write on your site that GridGain Community Edition powered by Apache Ignite will have additional bug fixes ... will this version be free? Why another version and why not bringing those fixes into the general Ignite?
-----Ursprüngliche Nachricht----- Von: Dmitriy Setrakyan [mailto:[hidden email]] Gesendet: Montag, 27. April 2015 09:24 An: [hidden email] Betreff: Re: Two different Ignite-Versions? We are currently resolving this confusion. The 1.0.2 version is for the GridGain Community Edition powered by Apache Ignite, which can be found here: http://www.gridgain.com/download/editions/ D. On Mon, Apr 27, 2015 at 12:01 AM, Markus Wiesenbacher < [hidden email]> wrote: > Hi guys, > > > > I recently noticed that there are two versions of Apache Ignite around: > > > > . v1.0.0: https://ignite.incubator.apache.org/download.html > > . v1.0.2: http://www.gridgain.com/download/editions/ > > > > Any clarification? ;) > > > > Thanks > > Markus > > |
Re: Two different Ignite-Versions?
|
|
On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher <
[hidden email]> wrote: > You write on your site that GridGain Community Edition powered by Apache > Ignite will have additional bug fixes ... will this version be free? Why > another version and why not bringing those fixes into the general Ignite? > Community Edition is free and all the fixes in community edition will be available in Apache Ignite. The benefit of the community edition is that it can be released more often than the official Apache Ignite release endorsed by ASF, so the community can get the bug fixes faster. > -----Ursprüngliche Nachricht----- > Von: Dmitriy Setrakyan [mailto:[hidden email]] > Gesendet: Montag, 27. April 2015 09:24 > An: [hidden email] > Betreff: Re: Two different Ignite-Versions? > > We are currently resolving this confusion. The 1.0.2 version is for the > GridGain Community Edition powered by Apache Ignite, which can be found > here: http://www.gridgain.com/download/editions/ > > D. > > On Mon, Apr 27, 2015 at 12:01 AM, Markus Wiesenbacher < > [hidden email]> wrote: > > > Hi guys, > > > > > > > > I recently noticed that there are two versions of Apache Ignite around: > > > > > > > > . v1.0.0: https://ignite.incubator.apache.org/download.html > > > > . v1.0.2: http://www.gridgain.com/download/editions/ > > > > > > > > Any clarification? ;) > > > > > > > > Thanks > > > > Markus > > > > > > |
Re: Two different Ignite-Versions?
|
|
On 29.04.2015 18:42, Dmitriy Setrakyan wrote:
> On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher < > [hidden email]> wrote: > >> You write on your site that GridGain Community Edition powered by Apache >> Ignite will have additional bug fixes ... will this version be free? Why >> another version and why not bringing those fixes into the general Ignite? >> > Community Edition is free and all the fixes in community edition will be > available in Apache Ignite. The benefit of the community edition is that it > can be released more often than the official Apache Ignite release endorsed > by ASF, so the community can get the bug fixes faster. I'm having real trouble understanding this argument. Any bugs would first be fixed in Ignite code, yes? Ignite can have an official release every hour if you guys are prepared to spend time on that. :) If I were a downstream user, I'd interpret "can be released more often" as either "bug fixes are not pushed upstream to Ignite" or "these releases are less rigorously tested". Neither interpretation sounds very palatable. -- Brane |
Re: Two different Ignite-Versions?
|
|
On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej <[hidden email]> wrote:
> On 29.04.2015 18:42, Dmitriy Setrakyan wrote: > > On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher < > > [hidden email]> wrote: > > > >> You write on your site that GridGain Community Edition powered by Apache > >> Ignite will have additional bug fixes ... will this version be free? Why > >> another version and why not bringing those fixes into the general > Ignite? > >> > > Community Edition is free and all the fixes in community edition will be > > available in Apache Ignite. The benefit of the community edition is that > it > > can be released more often than the official Apache Ignite release > endorsed > > by ASF, so the community can get the bug fixes faster. > > I'm having real trouble understanding this argument. Any bugs would > first be fixed in Ignite code, yes? Ignite can have an official release > every hour if you guys are prepared to spend time on that. :) > All bugs are fixed in Ignite first, of course. GridGain community edition just takes the sprint branch of Ignite and can produce a release at any point, if there are important bug fixes there. Official ASF release, as we all know, can take up to 2 weeks for voting and, if there are any rejections, even longer. There are also many other factors that may delay the official Apache release. The only motivation for the community edition is to provide the Ignite user base with bug fixes much sooner than within 2 weeks. > If I were a downstream user, I'd interpret "can be released more often" > as either "bug fixes are not pushed upstream to Ignite" or "these > releases are less rigorously tested". Neither interpretation sounds very > palatable. > > -- Brane > |
Re: Two different Ignite-Versions?
|
|
On 29.04.2015 23:13, Dmitriy Setrakyan wrote:
> On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej <[hidden email]> wrote: > >> On 29.04.2015 18:42, Dmitriy Setrakyan wrote: >>> On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher < >>> [hidden email]> wrote: >>> >>>> You write on your site that GridGain Community Edition powered by Apache >>>> Ignite will have additional bug fixes ... will this version be free? Why >>>> another version and why not bringing those fixes into the general >> Ignite? >>> Community Edition is free and all the fixes in community edition will be >>> available in Apache Ignite. The benefit of the community edition is that >> it >>> can be released more often than the official Apache Ignite release >> endorsed >>> by ASF, so the community can get the bug fixes faster. >> I'm having real trouble understanding this argument. Any bugs would >> first be fixed in Ignite code, yes? Ignite can have an official release >> every hour if you guys are prepared to spend time on that. :) >> > All bugs are fixed in Ignite first, of course. GridGain community edition > just takes the sprint branch of Ignite and can produce a release at any > point, if there are important bug fixes there. Official ASF release, as we > all know, can take up to 2 weeks for voting and, if there are any > rejections, even longer. There are also many other factors that may delay > the official Apache release. > > The only motivation for the community edition is to provide the Ignite user > base with bug fixes much sooner than within 2 weeks. You're assuming that Ignite will be an incubating podling forever. Is that a self-fulfilling prophecy? :D -- Brane |
Re: Two different Ignite-Versions?
|
|
On Wed, Apr 29, 2015 at 4:23 PM, Branko Čibej <[hidden email]> wrote:
> On 29.04.2015 23:13, Dmitriy Setrakyan wrote: > > On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej <[hidden email]> wrote: > > > >> On 29.04.2015 18:42, Dmitriy Setrakyan wrote: > >>> On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher < > >>> [hidden email]> wrote: > >>> > >>>> You write on your site that GridGain Community Edition powered by > Apache > >>>> Ignite will have additional bug fixes ... will this version be free? > Why > >>>> another version and why not bringing those fixes into the general > >> Ignite? > >>> Community Edition is free and all the fixes in community edition will > be > >>> available in Apache Ignite. The benefit of the community edition is > that > >> it > >>> can be released more often than the official Apache Ignite release > >> endorsed > >>> by ASF, so the community can get the bug fixes faster. > >> I'm having real trouble understanding this argument. Any bugs would > >> first be fixed in Ignite code, yes? Ignite can have an official release > >> every hour if you guys are prepared to spend time on that. :) > >> > > All bugs are fixed in Ignite first, of course. GridGain community edition > > just takes the sprint branch of Ignite and can produce a release at any > > point, if there are important bug fixes there. Official ASF release, as > we > > all know, can take up to 2 weeks for voting and, if there are any > > rejections, even longer. There are also many other factors that may delay > > the official Apache release. > > > > The only motivation for the community edition is to provide the Ignite > user > > base with bug fixes much sooner than within 2 weeks. > > You're assuming that Ignite will be an incubating podling forever. Is > that a self-fulfilling prophecy? :D > Haha. You are right, this is temporary. Once official apache releases start coming out sooner, or after Ignite graduates, we probably won't need the community edition at all. > -- Brane > |
Re: Two different Ignite-Versions?
|
|
On Wed, Apr 29, 2015 at 04:42PM, Dmitriy Setrakyan wrote:
> On Wed, Apr 29, 2015 at 4:23 PM, Branko Čibej <[hidden email]> wrote: > > > On 29.04.2015 23:13, Dmitriy Setrakyan wrote: > > > On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej <[hidden email]> wrote: > > > > > >> On 29.04.2015 18:42, Dmitriy Setrakyan wrote: > > >>> On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher < > > >>> [hidden email]> wrote: > > >>> > > >>>> You write on your site that GridGain Community Edition powered by > > Apache > > >>>> Ignite will have additional bug fixes ... will this version be free? > > Why > > >>>> another version and why not bringing those fixes into the general > > >> Ignite? > > >>> Community Edition is free and all the fixes in community edition will > > be > > >>> available in Apache Ignite. The benefit of the community edition is > > that > > >> it > > >>> can be released more often than the official Apache Ignite release > > >> endorsed > > >>> by ASF, so the community can get the bug fixes faster. > > >> I'm having real trouble understanding this argument. Any bugs would > > >> first be fixed in Ignite code, yes? Ignite can have an official release > > >> every hour if you guys are prepared to spend time on that. :) > > >> > > > All bugs are fixed in Ignite first, of course. GridGain community edition > > > just takes the sprint branch of Ignite and can produce a release at any > > > point, if there are important bug fixes there. Official ASF release, as > > we > > > all know, can take up to 2 weeks for voting and, if there are any > > > rejections, even longer. There are also many other factors that may delay > > > the official Apache release. > > > > > > The only motivation for the community edition is to provide the Ignite > > user > > > base with bug fixes much sooner than within 2 weeks. > > > > You're assuming that Ignite will be an incubating podling forever. Is > > that a self-fulfilling prophecy? :D > > > > Haha. > > You are right, this is temporary. Once official apache releases start > coming out sooner, or after Ignite graduates, we probably won't need the > community edition at all. Another venue to follow here is to make nightly or weekly builds of Ignite and publish them on our website. These can be called development snapshots or whatever and can be pushed out there without the voting process, as they aren't official releases. This should take care about the 'two-versions question' I believe. Thoughts? Cos |
Re: Two different Ignite-Versions?
|
|
On 29.04.2015 23:56, Konstantin Boudnik wrote:
> On Wed, Apr 29, 2015 at 04:42PM, Dmitriy Setrakyan wrote: >> On Wed, Apr 29, 2015 at 4:23 PM, Branko Čibej <[hidden email]> wrote: >> >>> On 29.04.2015 23:13, Dmitriy Setrakyan wrote: >>>> On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej <[hidden email]> wrote: >>>> >>>>> On 29.04.2015 18:42, Dmitriy Setrakyan wrote: >>>>>> On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher < >>>>>> [hidden email]> wrote: >>>>>> >>>>>>> You write on your site that GridGain Community Edition powered by >>> Apache >>>>>>> Ignite will have additional bug fixes ... will this version be free? >>> Why >>>>>>> another version and why not bringing those fixes into the general >>>>> Ignite? >>>>>> Community Edition is free and all the fixes in community edition will >>> be >>>>>> available in Apache Ignite. The benefit of the community edition is >>> that >>>>> it >>>>>> can be released more often than the official Apache Ignite release >>>>> endorsed >>>>>> by ASF, so the community can get the bug fixes faster. >>>>> I'm having real trouble understanding this argument. Any bugs would >>>>> first be fixed in Ignite code, yes? Ignite can have an official release >>>>> every hour if you guys are prepared to spend time on that. :) >>>>> >>>> All bugs are fixed in Ignite first, of course. GridGain community edition >>>> just takes the sprint branch of Ignite and can produce a release at any >>>> point, if there are important bug fixes there. Official ASF release, as >>> we >>>> all know, can take up to 2 weeks for voting and, if there are any >>>> rejections, even longer. There are also many other factors that may delay >>>> the official Apache release. >>>> >>>> The only motivation for the community edition is to provide the Ignite >>> user >>>> base with bug fixes much sooner than within 2 weeks. >>> You're assuming that Ignite will be an incubating podling forever. Is >>> that a self-fulfilling prophecy? :D >>> >> Haha. >> >> You are right, this is temporary. Once official apache releases start >> coming out sooner, or after Ignite graduates, we probably won't need the >> community edition at all. > Another venue to follow here is to make nightly or weekly builds of Ignite and > publish them on our website. These can be called development snapshots or > whatever and can be pushed out there without the voting process, as they > aren't official releases. > > This should take care about the 'two-versions question' I believe. Thoughts? Certainly. Nothing's stopping you from doing that. IIUC there are already nightly builds, having slightly better scrutinized development snapshots is some extra effort but not that much. Although, do note: if you have version update notifications, you really should take care to highlight the difference between the availability of a new release (officially stamped) and a new development snapshot (not as stable). -- Brane |
Re: Two different Ignite-Versions?
|
|
On Thu, Apr 30, 2015 at 12:08AM, Branko Čibej wrote:
> On 29.04.2015 23:56, Konstantin Boudnik wrote: > > On Wed, Apr 29, 2015 at 04:42PM, Dmitriy Setrakyan wrote: > >> On Wed, Apr 29, 2015 at 4:23 PM, Branko Čibej <[hidden email]> wrote: > >> > >>> On 29.04.2015 23:13, Dmitriy Setrakyan wrote: > >>>> On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej <[hidden email]> wrote: > >>>> > >>>>> On 29.04.2015 18:42, Dmitriy Setrakyan wrote: > >>>>>> On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher < > >>>>>> [hidden email]> wrote: > >>>>>> > >>>>>>> You write on your site that GridGain Community Edition powered by > >>> Apache > >>>>>>> Ignite will have additional bug fixes ... will this version be free? > >>> Why > >>>>>>> another version and why not bringing those fixes into the general > >>>>> Ignite? > >>>>>> Community Edition is free and all the fixes in community edition will > >>> be > >>>>>> available in Apache Ignite. The benefit of the community edition is > >>> that > >>>>> it > >>>>>> can be released more often than the official Apache Ignite release > >>>>> endorsed > >>>>>> by ASF, so the community can get the bug fixes faster. > >>>>> I'm having real trouble understanding this argument. Any bugs would > >>>>> first be fixed in Ignite code, yes? Ignite can have an official release > >>>>> every hour if you guys are prepared to spend time on that. :) > >>>>> > >>>> All bugs are fixed in Ignite first, of course. GridGain community edition > >>>> just takes the sprint branch of Ignite and can produce a release at any > >>>> point, if there are important bug fixes there. Official ASF release, as > >>> we > >>>> all know, can take up to 2 weeks for voting and, if there are any > >>>> rejections, even longer. There are also many other factors that may delay > >>>> the official Apache release. > >>>> > >>>> The only motivation for the community edition is to provide the Ignite > >>> user > >>>> base with bug fixes much sooner than within 2 weeks. > >>> You're assuming that Ignite will be an incubating podling forever. Is > >>> that a self-fulfilling prophecy? :D > >>> > >> Haha. > >> > >> You are right, this is temporary. Once official apache releases start > >> coming out sooner, or after Ignite graduates, we probably won't need the > >> community edition at all. > > Another venue to follow here is to make nightly or weekly builds of Ignite and > > publish them on our website. These can be called development snapshots or > > whatever and can be pushed out there without the voting process, as they > > aren't official releases. > > > > This should take care about the 'two-versions question' I believe. Thoughts? > > Certainly. Nothing's stopping you from doing that. IIUC there are > already nightly builds, having slightly better scrutinized development > snapshots is some extra effort but not that much. > > Although, do note: if you have version update notifications, you really > should take care to highlight the difference between the availability of > a new release (officially stamped) and a new development snapshot (not > as stable). Very good point - I missed that! |
«
Return to Apache Ignite Developers - Legacy Mail Archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |