Hi all,
The Calcite community has voted on and approved a proposal to release
Apache Calcite 1.1.0-incubating.
Proposal:
http://mail-archives.apache.org/mod_mbox/calcite-dev/201503.mbox/%3ccamctmekcqb3bezn0q-1ug6tzxm1p6jzjvbun9jupsfnjc3r...@mail.gmail.com%3E
Vote result:
3 binding +1 votes
1 non
Thanks for the clarification, Ross. That's what I figured.
In terms of the source drop, it's been attached to the associated JIRA, and the
SHA1 is in the yet-to-be-submitted ip clearance XML, and should be in the grant
as well. My guess is that MIGHT suffice in terms of it being documented in
A
Hi,
We're scheduling the Jira migration for Maven projects on the week-end of
4/5/6 april.
If this schedule is fine for Groovy, I suppose it would be ok to add Groovy
Jira project to the actual list [1]
Just tell, and I'll avoid to remove Groovy from the full dump we'll have
during the migratio
1. CCLA is never used instead of an SGA, they serve different purposes. The SGA
is for a body of work that pre-exists entry into the foundation. The CCLA is an
optional document that says future work by named individuals can be contributed.
2. Yes (although secretary tries his best to CC the app
I’m working on filling out the necessary IP Clearance paperwork for code
donation and have a few questions (forgive me if they are stupid, this is my
first time through the process):
Based on the IP clearance template documentation [1]:
1. When should a CCLA be used as opposed to a grant [2]?
2
yes, I dropped every project we didn't want to import since some of them had
special configuration that were causing issues
The first dump we used contained everything
Regards,
Hervé
Le lundi 16 mars 2015 10:03:37 Stephen Connolly a écrit :
> On 16 March 2015 at 09:58, Mark Thomas wrote:
> >
Hello,
The IPMC vote to release Apache NiFi 0.0.2-incubating passes.
The IPMC vote thread is here:
http://s.apache.org/nifi-0.0.2-ipmc-voteresult
Summary:
4 (binding) [+1]
0 [<= 0]
The following binding +1 votes were received:
- Sergio Fernandez
- Justin Mclean
- Benson Margulies
- Billie R
On 16 March 2015 at 09:58, Mark Thomas wrote:
> On 16/03/2015 09:53, Stephen Connolly wrote:
> > Arg! hit send too soon.
> >
> > You should really check in with Hervé to confirm that Groovy was in the
> > export. I am 99% confident that your issues and comments are in the XML
> > dump, but you re
On 16/03/2015 09:53, Stephen Connolly wrote:
> Arg! hit send too soon.
>
> You should really check in with Hervé to confirm that Groovy was in the
> export. I am 99% confident that your issues and comments are in the XML
> dump, but you really should check with Hervé to be certain.
>
> Also you m
Arg! hit send too soon.
You should really check in with Hervé to confirm that Groovy was in the
export. I am 99% confident that your issues and comments are in the XML
dump, but you really should check with Hervé to be certain.
Also you may want to ask Mark Thomas what exactly is involved in prep
On 16 March 2015 at 09:19, Cédric Champeau
wrote:
> Thanks Stephen, sounds like a good news. For us the attachments do not
> matter much, there are not so many. However, keeping track of comments is
> very important, because some issues have a lot of discussions.
>
> 2015-03-16 10:08 GMT+01:00 St
Thanks Stephen, sounds like a good news. For us the attachments do not
matter much, there are not so many. However, keeping track of comments is
very important, because some issues have a lot of discussions.
2015-03-16 10:08 GMT+01:00 Stephen Connolly :
> On 16 March 2015 at 08:55, Jochen Theodor
On 16 March 2015 at 08:55, Jochen Theodorou wrote:
> Am 16.03.2015 09:25, schrieb Upayavira:
>
>> When Stephen Connolly says ”We @ Maven will have a full dump of the
>> Codehaus JIRA and we have a VM set
>> up to test migration…” isn’t he implying that the Groovy issues are
>> *included* in that?
You should check with Hervé, but as far as I am aware it is a dump of
everything as JIRA only provides for a full export.
Because there are bits of security information in the export, access to the
dump is restricted, but ASF INFRA also have access to the dump, or we can
probably give one of you a
Am 16.03.2015 09:25, schrieb Upayavira:
When Stephen Connolly says ”We @ Maven will have a full dump of the
Codehaus JIRA and we have a VM set
up to test migration…” isn’t he implying that the Groovy issues are
*included* in that? I.e. there’s not so much for you to worry about
here?
Even if St
When Stephen Connolly says ”We @ Maven will have a full dump of the
Codehaus JIRA and we have a VM set
up to test migration…” isn’t he implying that the Groovy issues are
*included* in that? I.e. there’s not so much for you to worry about
here?
Upayavira
On Sat, Mar 14, 2015, at 12:13 AM, Jochen
16 matches
Mail list logo
