Hi folks!
It's been a while since our last release. We've had some nice stuff
land and we should get those contributions into releases so they are
more widely available.
Is there anything that I should consider a blocker on a 1.10.1 minor
release off of branch-1.10?
How about our next major rele
Hi folks!
Here's the report for the quarter I submitted. Let me know if there are any
last minute changes y'all would like to see.
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema driven serialized data.
Hi folks!
On behalf of the Apache Avro PMC I am pleased to announce that Ryan
Skraba has accepted our invitation to become a PMC member. We
appreciate Ryan stepping up to take more responsibility in the
project.
Please join me in welcoming Ryan to the Avro PMC!
As a reminder, if anyone would lik
Hi folks,
At the board meeting this morning a question was raised asking if our CPAN
published artifacts meet release guidance.
Can anyone point me to what, if any, stuff we have for pushing things out
to CPAN after a release? Like a guide or automated tooling or whatever?
Hi folks!
Here's the report for the quarter I submitted. Let me know if there are any
last minute changes y'all would like to see.
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema driven serialized data.
[
https://issues.apache.org/jira/browse/AVRO-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150611#comment-17150611
]
Sean Busbey commented on AVRO-2875:
---
looks like we don't have githu
+1 binding
I think the nexus link was wrong. It was just the avro:avro jar for
1.10. looking at nexus I believe the staged repo for just his RC is
this:
https://repository.apache.org/content/repositories/orgapacheavro-1028/
I based my voting on the provided dist RC and this staged repo.
* sign
>
> I'm happy to make PR clarifying this. I'm a little bit concerned that if
> validation doesn't exist in Java (and maybe other languages today) if we
> make the spec stricter it could break users. How has the community handled
> issues like this in the past?
Something similar happened for the
Sounds like a reasonable spec change. I think this would be our first
breaking spec change? does that mean this is the time for us to hash
out versioning the spec, or are we going to update all of our versions
to 2.x?
Can we get an idea on failure expectations for the SDKs we maintain?
On Wed, Ju
[
https://issues.apache.org/jira/browse/AVRO-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126323#comment-17126323
]
Sean Busbey commented on AVRO-2860:
---
It is not accurate to say jdk8 is EOL. Both
I'd like a issues@avro or notifications@avro that has the detailed
messages from Github and Jira. Great suggestion.
I would prefer PR and jira issue creation / closure still go to the dev
list, but I don't feel strongly about it since I will probably subscribe to
both lists.
On Thu, May 7, 2020
If we'd like an alternative to the dev@avro mailing list, there is a
growing amount of infra support for using slack. in particular there is a
bot for making sure you can send stuff to a mailing list for those who want
a record.
Andy, what kind of response would you see as proper? Is your concern
7;m new to Apache Avro project. Is there
> any guideline for how to become a member of Apache Avro?
>
> Thanks & be strong!
>
> On 2020/04/09 05:12:16, Sean Busbey wrote:
> > Hi folks!
> >
> > Here's the report for the quarter I submitted. Let me know
Hi folks!
Here's the report for the quarter I submitted. Let me know if there are any
last minute changes y'all would like to see.
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema driven serialized data. T
in favor of switching to 10.x (dropping the 1. in front of
> it). What's the added value in this? I'm just afraid of changing this,
> would confuse a lot of downstream users.
>
> Also, a similar discussion was on the Spark devlist, I think Michael has
> some valid points
g
> > >
> > >
> > >
> > > Op wo 11 sep. 2019 om 18:17 schreef Ryan Blue > >:
> > >
> > > > > What would it look like if we *did* have to make an incompatible data
> > > > format change after adopting "conventional"
unless the RM has an objection based on where they are in the RC
creation process, I say go for it. (and if there is such an issue then
let's get it ready for 1.9.3)
On Fri, Jan 31, 2020 at 10:29 AM Ryan Skraba wrote:
>
> Hello! There's a long standing PR[1][2] that provides an impressive
> perf
Hi folks!
Here's the report for the quarter I submitted. Let me know if there are any
last minute changes y'all would like to see.
## Description:
Apache Avro is a data serialization system with a compact binary format. It
is
used for storing and transporting schema driven serialized data. T
[
https://issues.apache.org/jira/browse/AVRO-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2604:
--
Fix Version/s: 1.9.1
Resolution: Fixed
Status: Resolved (was: Patch Available)
all
Yeah we should have a release; we are overdue.
On Mon, Jan 6, 2020, 06:32 Michael A. Smith wrote:
> I'd suggest that we do at least one release that has support for both
> python 2 and 3 in the same codebase. This may open doors for folks trying
> to transition from both avro-python3 (lang/py3)
[
https://issues.apache.org/jira/browse/AVRO-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969808#comment-16969808
]
Sean Busbey commented on AVRO-2602:
---
1.7.7 -> 1.8 is a major version change f
[
https://issues.apache.org/jira/browse/AVRO-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968015#comment-16968015
]
Sean Busbey commented on AVRO-2616:
---
I agree that it would be best to get any ne
[
https://issues.apache.org/jira/browse/AVRO-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2604:
--
Component/s: community
> Artifacts were signed with a key not in K
[
https://issues.apache.org/jira/browse/AVRO-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959414#comment-16959414
]
Sean Busbey commented on AVRO-2604:
---
thanks for catching this [~epibkr]!
Sounds
[
https://issues.apache.org/jira/browse/AVRO-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2604:
--
Priority: Critical (was: Major)
> Artifacts were signed with a key not in K
Hi folks!
I'm very pleased to announce that Michael Smith has accepted the PMC's
invitation to become a committer on the Apache Avro project.
Please join me in congratulating Michael on this recognition of their
great work thus far in our community.
I went ahead and posted the report, with one minor change noted below. I
can still edit it over the next few days if needed.
On Wed, Oct 9, 2019 at 12:00 AM Sean Busbey wrote:
>
> ## Activity:
> The Avro project slowly is improving on our gains from the last year.
>
> We've
Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- Sean Busbey became PMC Chair
- Brian Lachniet was added to the PMC on 2019-08-23
- Nándor Kollár was added to the PMC on 2019-08-29
- No new committers. Last addition was Tim Perkins on 2018-12-12.
Releases, past quarter:
-
[
https://issues.apache.org/jira/browse/AVRO-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945492#comment-16945492
]
Sean Busbey edited comment on AVRO-1891 at 10/7/19 12:4
[
https://issues.apache.org/jira/browse/AVRO-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945492#comment-16945492
]
Sean Busbey commented on AVRO-1891:
---
I don't think folks know. The changes i
ue, Sep 10, 2019 at 3:55 PM Ryan Blue wrote:
>
> +1 for changing the version strings to follow a more standard convention.
> We don't have any breaking format changes, so I think it is expected that
> the format compatibility version won't change.
>
> On Tue, Sep
[
https://issues.apache.org/jira/browse/AVRO-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2555:
--
Component/s: java
> Update IDL docs to remove mention of avroj.
[
https://issues.apache.org/jira/browse/AVRO-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reassigned AVRO-2555:
-
Assignee: Erik Tank
> Update IDL docs to remove mention of avroj.
[
https://issues.apache.org/jira/browse/AVRO-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926692#comment-16926692
]
Sean Busbey commented on AVRO-2555:
---
+1 change looks good. Can you please regene
Hi folks!
historically, Avro version numbers have had the form:
. .
That is, the first number says wether or not we expect data
serialization to be compatible, and the second to say wether we expect
some library will be backwards incompatible however that's defined for
the library's language.
[
https://issues.apache.org/jira/browse/AVRO-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925012#comment-16925012
]
Sean Busbey commented on AVRO-2550:
---
Yeah, if the artifact isn't on the liv
[
https://issues.apache.org/jira/browse/AVRO-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923927#comment-16923927
]
Sean Busbey commented on AVRO-2550:
---
If we want to avoid having to update when Y
[
https://issues.apache.org/jira/browse/AVRO-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved AVRO-2531.
---
Fix Version/s: 1.10.0
Resolution: Fixed
> Update commons-compress to version 1
[
https://issues.apache.org/jira/browse/AVRO-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920535#comment-16920535
]
Sean Busbey commented on AVRO-2522:
---
How close is this to landing? it's not ma
Hi folks!
On behalf of the Apache Avro PMC I am pleased to announce that Nándor
Kollár has accepted our invitation to become a PMC member. We
appreciate Nándor stepping up to take more responsibility in the
project.
Please join me in welcoming Nándor to the Avro PMC!
As a reminder, if anyone wou
[
https://issues.apache.org/jira/browse/AVRO-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916724#comment-16916724
]
Sean Busbey commented on AVRO-2527:
---
that sounds great. Thanks Kengo!
> Upgr
[
https://issues.apache.org/jira/browse/AVRO-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915956#comment-16915956
]
Sean Busbey commented on AVRO-2527:
---
Does this necessitate not working with PHP 5
Hi folks!
On behalf of the Apache Avro PMC I am pleased to announce that Brian
Lachniet has accepted our invitation to become a PMC member. We
appreciate Brian stepping up to take more responsibility in the
project.
Please join me in welcoming Brian to the Avro PMC!
As a reminder, if anyone woul
please pull those artifacts off of nuget. We can only make approved
releases available outside of the dev mailing list.
On Tue, Aug 20, 2019 at 9:17 PM Brian Lachniet wrote:
>
> It sounds like an rc2 is imminent, but I went ahead and ran some basic
> checks on the C# bindings. I didn't find any
Sean Busbey created AVRO-2451:
-
Summary: Releases should be tagged in git with "rel/" prefix
Key: AVRO-2451
URL: https://issues.apache.org/jira/browse/AVRO-2451
Project: Apache Avro
[
https://issues.apache.org/jira/browse/AVRO-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2450:
--
Status: Patch Available (was: In Progress)
> log message about failure to load SnappyCo
[
https://issues.apache.org/jira/browse/AVRO-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AVRO-2450 started by Sean Busbey.
-
> log message about failure to load SnappyCo
Sean Busbey created AVRO-2450:
-
Summary: log message about failure to load SnappyCodec
Key: AVRO-2450
URL: https://issues.apache.org/jira/browse/AVRO-2450
Project: Apache Avro
Issue Type: Bug
e, Jun 25, 2019 at 10:51 AM Sean Busbey wrote:
>
> What difficulties are folks running into when trying to move to 1.9.0 so far?
>
> --
> busbey
--
busbey
What difficulties are folks running into when trying to move to 1.9.0 so far?
--
busbey
Hi folks!
On behalf of the Apache Avro PMC I am pleased to announce that Ismaël
Mejía has accepted our invitation to become a PMC member. We
appreciate Ismaël stepping up to take more responsibility in the
project.
Please join me in welcoming Ismaël to the Avro PMC!
As a reminder, if anyone woul
; > > published
> > > > > > 5/8
> > > > > > (the same day as RC4 was announced but ~1week before vote passed).
> > > > > >
> > > > > > Is this the release build (presumably the same as RC4) or an earlier
> > > >
Hi folks!
On behalf of the Apache Avro PMC I am pleased to announce that Fokko
Driesprong has accepted our invitation to become a PMC member on the
Avro project. We appreciate Fokko stepping up to take more
responsibility in the project.
Please join me in welcoming Fokko to the Avro PMC!
As a
[
https://issues.apache.org/jira/browse/AVRO-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838596#comment-16838596
]
Sean Busbey commented on AVRO-2395:
---
here's a walkthrough for getting the 1
+1 (binding)
-- Good:
* signatures
* checksums
* tag/ref lines up with src artifact (except for one file mentioned below)
* LICENSE/NOTICE spot check
* apache rat says the license files for all the artifacts are fine (except it
couldn't understand the gem; using the gem cli confirms it's also cor
Sean Busbey created AVRO-2395:
-
Summary: Stop including bare jars as convenience binary for Java
Key: AVRO-2395
URL: https://issues.apache.org/jira/browse/AVRO-2395
Project: Apache Avro
Issue
[
https://issues.apache.org/jira/browse/AVRO-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2385:
--
Description:
Steps to reproduce:
Create an Avro schema with an uppercase field:
{code}
{
"
[
https://issues.apache.org/jira/browse/AVRO-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2385:
--
Description:
Steps to reproduce:
Create an Avro schema with an uppercase field:
{code}
{
"
[
https://issues.apache.org/jira/browse/AVRO-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2385:
--
Environment: Using Maven plugin with Java 8 (was: Using Maven plugin with
Java 8
[
https://issues.apache.org/jira/browse/AVRO-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761001#comment-16761001
]
Sean Busbey commented on AVRO-1989:
---
nope. somehow I totally missed that it got
Is this in a release or just project internal still?
On Tue, Jan 22, 2019 at 3:41 AM Ismaël Mejía wrote:
>
> Hello,
>
> I just wanted to announce that we merged today the last fix to support
> Java 11 in our build system. Notice that Avro is still Java 8
> compatible and will remain for long time
[
https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737323#comment-16737323
]
Sean Busbey edited comment on AVRO-1559 at 1/8/19 5:30 PM:
--
[
https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737323#comment-16737323
]
Sean Busbey commented on AVRO-1559:
---
I agree for 1.9.0+ we should bump to 2.3+.
[
https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737324#comment-16737324
]
Sean Busbey commented on AVRO-1559:
---
still worth a DISCUSS thread on dev@avro, s
Hi folks!
First, I want to give a big thanks to everyone who's been slogging through the
backlog of changes over the last few months. It's really exciting to see
progress again.
What are folks thinking about in terms of releases? I'm particularly interested
in what the currently active contrib
In the future please use "[DISCUSS]" at the start of your subject line
for these kinds of proposals. that'll get more folks to see the
discussion, e.g. when they filter this list.
as a point of clarification, 1.9.0 is a major version change for the
Avro project. the "1" is a file format version. t
[
https://issues.apache.org/jira/browse/AVRO-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709009#comment-16709009
]
Sean Busbey commented on AVRO-2273:
---
Reminder that in Avro the second number is a m
1.9 is a major version change, so long as we release note the
incompatible change this should be fine. Especially if the folks doing
hte day-to-day maintenance of the C++ code want a newer standard.
On Tue, Dec 4, 2018 at 11:04 AM Daniel Kulp wrote:
>
>
> I’ve updated and merged the PR for moving
[
https://issues.apache.org/jira/browse/AVRO-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702154#comment-16702154
]
Sean Busbey commented on AVRO-2250:
---
Avro's use of a shaded guava purposef
Hi Folks!
I'm very pleased to announce that Ismaël Mejía has accepted the PMC's
invitation to become a committer on the Apache Avro project.
Please join me in congratulating Ismaël on this recognition of their
great work thus far in our community!
Hi Folks!
I'm very pleased to announce that Daniel Kulp has accepted the PMC's
invitation to become a committer on the Apache Avro project.
Please join me in congratulating Daniel on this recognition of his
great work thus far in our community!
//github.com/apache/avro/pull/344> to configure the precommit task
> to run CI jobs, as Sean Busbey initially suggested. Initially I would like
> to go for a Travis CI, as we have with Apache Airflow, but I think the Jenkins
> of Apache itself <https://builds.apache.org/> might
On Fri, Oct 12, 2018 at 6:54 AM Niels Basjes wrote:
>
> > have a build matrix ... Java 10 and 11. ... easier to configure in, ...
> > Travis ... native support.
>
> This is exactly why I asked about the preference for Jenkins.
> Listening to these arguments I would tend to go to Travis as it
> i
[
https://issues.apache.org/jira/browse/AVRO-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639160#comment-16639160
]
Sean Busbey commented on AVRO-1705:
---
(for reference, the jira covering Y
[
https://issues.apache.org/jira/browse/AVRO-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639159#comment-16639159
]
Sean Busbey commented on AVRO-1705:
---
[~Fokko] you should start a discussion on the
speaking of precommit builds, if someone wants to pick up and drive
AVRO-1887 ("set up precommit checks via Apache Yetus") to
completion, that would greatly ease the burden of testing out
contributions.
AFAICT the PMC is open to big shifts here, we're just bandwidth
limited for things that aren't
losed PR #299 to reduce the confusion.
> > >
> > > I am willing to act as the lead, or help with maintenance/management,
> of
> > > the C# project. I've been making updates and releases of the C# part of
> > the
> > > project on my own for
[
https://issues.apache.org/jira/browse/AVRO-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493638#comment-16493638
]
Sean Busbey commented on AVRO-1126:
---
it looks blocked on AVRO-1605
> Upg
This guidance on PRs helps tremendously, thanks! Do Brian and Milkenko
agree that PR #307 supersedes PR #299 and PR #261? I ask because both are
still open.
I don't think there is currently someone acting as lead for C# / dotnet.
Would one more of y'all be interested in acting in that role?
I'm
Sean Busbey created AVRO-2175:
-
Summary: website refactor
Key: AVRO-2175
URL: https://issues.apache.org/jira/browse/AVRO-2175
Project: Avro
Issue Type: Task
Components: community
On Thu, May 3, 2018 at 4:18 PM, Doug Cutting wrote:
> Maybe we should loosen the permissions on Avro's Jira so that any user can
> assign an issue? That would make things a bit simpler. I doubt we'd see
> much if any abuse.
>
locking down issue assigning happened ASF jira wide due to spammer a
On Thu, Apr 26, 2018 at 1:43 PM, Doug Cutting wrote:
> So I guess this would be easier if we also said that contributions would
> only now be accepted via pull request. Is that too onerous? Instead of
> requiring everyone to have an Apache Jira account we require them to have a
> GitHub account
butors, as compared with Jira:
>
> https://s.apache.org/mgf9
>
> Thoughts?
>
> Doug
>
>
> On Thu, Apr 26, 2018 at 4:53 AM Sean Busbey wrote:
>
> > how about we create a PMC-controlled jira account to represent "pull
> > request from someone without
how about we create a PMC-controlled jira account to represent "pull
request from someone without a jira ID"? then we can follow your suggestion
of "encourage the contributor to create a jira id and assign to them" and
we have a clear way to mark "you need to look at git or github to find the
autho
Hi Folks!
Today I tried to work through some helpful contributions to our website[1], and
I ran smack into some pretty severe tech debt for our web presence.
For starters, none of our documentation talks about how to build / deploy or
contribute to the website. That's pretty bad. What's worse,
[
https://issues.apache.org/jira/browse/AVRO-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2171:
--
Status: In Progress (was: Patch Available)
this patch has the same issue as AVRO-2170: we're curr
[
https://issues.apache.org/jira/browse/AVRO-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446863#comment-16446863
]
Sean Busbey commented on AVRO-2170:
---
shoot. this won't work as-is, because aut
[
https://issues.apache.org/jira/browse/AVRO-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2170:
--
Status: In Progress (was: Patch Available)
> Update footer of website to use Apache Avro instead
ache.org/jira/browse/AVRO-2171
>
> 2018-04-17 21:26 GMT+01:00 Sean Busbey :
>
> > Hi Roy!
> >
> > Please provide a patch on a JIRA issue and we'll take a look.
> >
> > Thanks for your interest.
> >
> > On Tue, Apr 17, 2018 at 2:32 PM, Roy Lenfe
[
https://issues.apache.org/jira/browse/AVRO-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reassigned AVRO-2171:
-
Assignee: Roy Lenferink
> Add current-event banner to project webs
[
https://issues.apache.org/jira/browse/AVRO-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2170:
--
Status: Patch Available (was: Open)
> Update footer of website to use Apache Avro instead of Apa
[
https://issues.apache.org/jira/browse/AVRO-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2170:
--
Component/s: community
> Update footer of website to use Apache Avro instead of Apache Had
[
https://issues.apache.org/jira/browse/AVRO-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2171:
--
Component/s: community
> Add current-event banner to project webs
[
https://issues.apache.org/jira/browse/AVRO-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2171:
--
Status: Patch Available (was: Open)
> Add current-event banner to project webs
[
https://issues.apache.org/jira/browse/AVRO-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reassigned AVRO-2170:
-
Assignee: Roy Lenferink
> Update footer of website to use Apache Avro instead of Apache Had
Hi Roy!
Please provide a patch on a JIRA issue and we'll take a look.
Thanks for your interest.
On Tue, Apr 17, 2018 at 2:32 PM, Roy Lenferink
wrote:
> Hi all,
>
> I came to the Apache Avro project to update the website to add a banner for
> the latest apache events.
> This is as a follow up f
[
https://issues.apache.org/jira/browse/AVRO-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409699#comment-16409699
]
Sean Busbey commented on AVRO-2162:
---
this would be great!
> Add Zstandard comp
Hi Neal!
That looks great. I'd say the big steps will be:
1) start a thread with a merge discussion. the subject line should look
something like "[DISCUSS] code donation for php library"
you should make clear in that thread if you think we ought to merge in your
changes with the existing library
[
https://issues.apache.org/jira/browse/AVRO-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364168#comment-16364168
]
Sean Busbey commented on AVRO-2041:
---
thanks for taking this over Niels!
> set up
[
https://issues.apache.org/jira/browse/AVRO-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-2112:
--
Status: Patch Available (was: Open)
> c# (.net) port to .NET Standard 2.0 and nuget (pack
1 - 100 of 702 matches
Mail list logo
