Now that graduation is done (!!), we need to organize our next release. I
propose we focus on completing the transition to TLP and cleaning up
“incubating" references. The sequence would look something like this:
1) Transition the git repo, mailing lists, etc.
2) Update incubating references i
Anthony,
What are the actual implications of this transition to the tlp ?
Regards,
Dor
-Original Message-
From: Anthony Baker [mailto:aba...@pivotal.io]
Sent: יום ב 21 נובמבר 2016 19:26
To: dev@geode.apache.org
Subject: The next release (v1.1.0)
Now that graduation is done (!!), we
age-
> From: Anthony Baker [mailto:aba...@pivotal.io]
> Sent: יום ב 21 נובמבר 2016 19:26
> To: dev@geode.apache.org
> Subject: The next release (v1.1.0)
>
> Now that graduation is done (!!), we need to organize our next release. I
> propose we focus on completing t
To: geode
Subject: Re: The next release (v1.1.0)
Transitioning from an incubating project to a top-level project means we keep
doing exactly what we’ve been doing—except that now the project is responsible
for managing itself. We will be transitioning a few resources such as mailing
lists and
nuing to contribute?
> Regards,
> Dor
>
> -Original Message-
> From: Anthony Baker [mailto:aba...@pivotal.io]
> Sent: יום ג 22 נובמבר 2016 16:44
> To: geode
> Subject: Re: The next release (v1.1.0)
>
> Transitioning from an incubating project to a top-level projec
+1... We all want this project to be the best it can be.
On 11/23/16 09:07, Dan Smith wrote:
Dor - I don't think any of the active committers are planning on leaving.
We're working on this project because we want it to thrive, and graduation
is one more thing that will help it grow!
> Sent: יום ג 22 נובמבר 2016 16:44
> To: geode
> Subject: Re: The next release (v1.1.0)
>
> Transitioning from an incubating project to a top-level project means we keep
> doing exactly what we’ve been doing—except that now the project is
> responsible for managing its
Hi Anthony
Thanks for the answer.
Dor
Original Message
Subject: Re: The next release (v1.1.0)
From: Anthony Baker
Date: 25 בנוב' 2016, 16:44
To: dev@geode.apache.org
Hi Dor,
I want to stress that the transition was from an Apache Incubator subproject to
an Apach
e?
Thanks,
Nitin
[1]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning.nodetail
On Fri, Nov 25, 2016 at 12:45 PM, Dor Ben Dov
wrote:
> Hi Anthony
>
> Thanks for the answer.
>
> Dor
>
> Original Message ----
>
> Subjec
FYI, I started work on GEODE-2156 to remove references to “incubating”. Feel
free to jump in on the feature branch (feature/GEODE-2156).
I don’t plan to merge this to develop until the infrastructure changes are
ready (see INFRA-12937).
Anthony
> On Nov 25, 2016, at 7:44 PM, Nitin Lamba wro
Our last release was on October 25. I think we’re past due for another one!
We’ve had lots of great contributions since 1.0.0-incubating and now that we’re
are a top-level project we can drop the “-incubating” qualifier.
I reviewed our open JIRA issues and would like to include the following i
Updates:
1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0.
2) Any volunteers to look at GEODE-2031 or GEODE-1965?
3) Are there other open issues that should be included in the release?
4) Last call for a release manager… :-)
Thanks,
Anthony
> On Jan 6, 2017, at 10:1
Re: 2) I'll take a look at GEODE-2031, versioning the documentation.
On Mon, Jan 9, 2017 at 9:50 AM Anthony Baker wrote:
> Updates:
>
> 1) I did a first round of changes on GEODE-2142, should be enough for
> v1.1.0.
> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> 3) Are there other op
let me try it out this time. Any instruction to follow?
Thanks.HItesh
From: Anthony Baker
To: dev@geode.apache.org
Sent: Monday, January 9, 2017 9:49 AM
Subject: Re: The next release (v1.1.0)
Updates:
1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0.
2
> On Jan 9, 2017, at 10:53 AM, Hitesh Khamesra
> wrote:
>
> let me try it out this time. Any instruction to follow?
> Thanks.HItesh
>
>
> From: Anthony Baker
> To: dev@geode.apache.org
> Sent: Monday, January 9, 2017 9:49 AM
> Subject: Re: The next release
4. GEODE-1965 Create backward-compatibility unit test framework
Thanks.HItesh
From: Anthony Baker
To: dev@geode.apache.org
Sent: Monday, January 9, 2017 9:49 AM
Subject: Re: The next release (v1.1.0)
Updates:
1) I did a first round of changes on GEODE-2142, should be enough for
)
Thanks.HItesh
From: Hitesh Khamesra
To: "dev@geode.apache.org"
Sent: Monday, January 16, 2017 12:35 PM
Subject: Re: The next release (v1.1.0)
Update: We are waiting on following tickets for first release candidate.
1. GEODE-2296 GetFunctionAttribute command is throwing an
anks.HItesh
>
>
>
> From: Hitesh Khamesra
> To: "dev@geode.apache.org"
> Sent: Monday, January 16, 2017 12:35 PM
> Subject: Re: The next release (v1.1.0)
>
> Update: We are waiting on following tickets for first release candidate.
>
> 1. GEODE-229
command is throwing an Anonymouse
> User
> > Exception
> > 2. GEODE-2277 client cache fails to deserialize a PdxInstance due to
> > InternalGemFireError
> > 3. GEODE-2031 Host documentation for releases
> > 4. GEODE-1965 Create backward-compatibility unit test framew
ability to sort field while creating pdxType for jSON
>> > document(Need to document system property)
>> >
>> > Thanks.HItesh
>> >
>> >
>> >
>> > From: Hitesh Khamesra
>> > To: "dev@geode.apache.o
sort field while creating pdxType for jSON
>> document(Need to document system property)
>>
>> Thanks.HItesh
>>
>>
>>
>> From: Hitesh Khamesra
>> To: "dev@geode.apache.org"
>> Sent: Monday, January 16, 2017 12:35 PM
>>
Type for jSON
> >> document(Need to document system property)
> >>
> >> Thanks.HItesh
> >>
> >>
> >>
> >> From: Hitesh Khamesra
> >> To: "dev@geode.apache.org"
> >> Sent: Monday, January 16, 2017 12:35 PM
> >&
22 matches
Mail list logo
