+1 although I thought this was already in a PR?
On Tuesday, April 5, 2016 6:23 PM, Manu Zhang
wrote:
Hi all,
I'd like to include https://github.com/gearpump/gearpump/issues/2013 (Refactor
DataSource API).
What do you think ?
On Wed, Apr 6, 2016 at 8:50 AM Kam
Sean Zhong created GEARPUMP-14:
--
Summary: Define and document process to make contributions, voting
rule, and make releases.
Key: GEARPUMP-14
URL: https://issues.apache.org/jira/browse/GEARPUMP-14
Dear Gearpump Podling,
Just a reminder about your board report, its due tomorrow.
John
Three most important issues to address in the move towards graduation:
1. Develop a tag line that describes gearpump. For example others
- Apache Flink is an open source platform for distributed stream and batch
data processing
- Apache Spark™ is a fast and general engine for
Three most important issues to address in the move towards graduation:
1. Develop a tag line that describes gearpump. For example others
- Apache Flink is an open source platform for distributed stream and batch
data processing
- Apache Spark™ is a fast and general engine for
@Andrew,
It seems I don't have permission to do operation like:
1. Everyone can report the issue and change the issue assignee.
2. Add a new field called “Issue Links” so that we can link the pull
request here. Like: https://issues.apache.org/jira/browse/SPARK-14359
The functions are locked.
+1.
在 16/4/5 下午2:55,“Sean Zhong” 写入:
>Jira customization allows us to add new "required field", "optional field"
>for new issue submission, and also allow us to define component list, and
>etc...
>
>Here are several customization that make sense to me, please contribute
Jira customization allows us to add new "required field", "optional field"
for new issue submission, and also allow us to define component list, and
etc...
Here are several customization that make sense to me, please contribute
your thoughts on this:
1. Add a field called “Issue Links” so that
@Andrew,
Thanks, we probably should only do manual migration, so that the text in
Jira is not messed up.
And I think we should only import issues that are still open.
On Sat, Apr 2, 2016 at 2:53 AM, Andrew Purtell wrote:
> We used the GitHub to JIRA import option when
Here is my thoughts about pre-condition for graduation:
1. We should setup the environment to reduce the challenges for new
contributors to make contribution. Currently, it is not very easy for new
developer to make contribution, we need a environment like this:
a. Document clearly on
10 matches
Mail list logo