+1 from me:
[mattmann-0420740:~/tmp/apache-ocw-1.0.0-rc1] mattmann%
$HOME/bin/stage_apache_rc climate 1.0.0-rc1
https://dist.apache.org/repos/dist/dev/climate/1.0.0_rc1/
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload
[
https://issues.apache.org/jira/browse/CLIMATE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huikyo Lee updated CLIMATE-671:
---
Fix Version/s: 1.0.0
> Inappropriate spatial subset for datasets on curvilinear grids
> -
[
https://issues.apache.org/jira/browse/CLIMATE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huikyo Lee updated CLIMATE-673:
---
Fix Version/s: 1.0.0
> Update the module to load multiple netcdf files
>
[
https://issues.apache.org/jira/browse/CLIMATE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huikyo Lee updated CLIMATE-672:
---
Fix Version/s: 1.0.0
> Update the input validation function for OCW datasets
> --
[
https://issues.apache.org/jira/browse/CLIMATE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huikyo Lee updated CLIMATE-674:
---
Fix Version/s: 1.0.0
> Update the spatial_regrid module to handle data on curvilinear grids or
> irr
[
https://issues.apache.org/jira/browse/CLIMATE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huikyo Lee updated CLIMATE-668:
---
Fix Version/s: 1.0.0
> ocw.dataset_spatial_resolution needs to be fixed
> ---
[
https://issues.apache.org/jira/browse/CLIMATE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huikyo Lee updated CLIMATE-666:
---
Fix Version/s: 1.0.0
> Replace examples with the RCMES script and yaml files
> --
Hi Kyo,
On Wed, Sep 23, 2015 at 9:49 AM, wrote:
>
> -1 Do not release the package because there are many important pull
> requests under pending now.
>I just wonder if there are any reasons to expedite the release.
>
> Thanks,
> Kyo
>
>
Thanks for taking the time to VOTE.
I would urge you to
[
https://issues.apache.org/jira/browse/CLIMATE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maziyar Boustani closed CLIMATE-663.
Resolution: Fixed
https://github.com/apache/climate/pull/226
> ocw-config-runner need to b
Maziyar Boustani created CLIMATE-675:
Summary: Latitude and longitude resolution on CLI should not be
always equal
Key: CLIMATE-675
URL: https://issues.apache.org/jira/browse/CLIMATE-675
Project:
Hi Lewis,
I think OCW has some critical bugs to be fixed.
I am not sure who else is testing OCW libraries with all the datasets
mentioned on http://rcmes.jpl.nasa.gov
At least, the RCMES based on OCW is about to reach a milestone. To achieve
this, several people have worked hard during the summer.
So why can't we roll a release immediately after the open PRs are
eventually resolved? We gladly support RCMES but the state of a product
there shouldn't be hindering an OCW release, especially not given how easy
it is to roll another release if we want to include some useful features
that come alo
Kyo,
Do you have a specific pull request(s) that you think need to be in the
1.0.0 release and couldn't wait until the next release? That might help us
get started moving in the direction to getting everything resolved!
-- Jimmy
On Wed, Sep 23, 2015 at 10:39 AM, Michael Joyce wrote:
> So why
GitHub user MBoustani opened a pull request:
https://github.com/apache/climate/pull/237
spatial resolution for lat and lon can be different now
@huikyole please try this PR and if it solved the issue then I can commit
to main repo.
Thanks
You can merge this pull request into a
Github user OCWJenkins commented on the pull request:
https://github.com/apache/climate/pull/237#issuecomment-142681456
Merged build triggered. Test Failed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user OCWJenkins commented on the pull request:
https://github.com/apache/climate/pull/237#issuecomment-142681485
Merged build started. Test Failed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project do
Github user OCWJenkins commented on the pull request:
https://github.com/apache/climate/pull/237#issuecomment-142682339
Merged build finished. Test Passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project d
Github user huikyole commented on the pull request:
https://github.com/apache/climate/pull/237#issuecomment-142684416
@MBoustani I reviewed the code and now it addresses 'one' of the issues
when loading datasets with two-dimensional longitudes and latitudes. #237 needs
to be merged AS
I play devil¹s advocate and argue that version 1.0.0 release is a good
chance to complete Pull Request 666, 672 and 674 and make the ocw-cli work
well with the datasets described on http://rcmes.jpl.nasa.gov
Thanks,
Kyo
On 9/23/15, 10:44 AM, "mltjo...@gmail.com on behalf of Michael Joyce"
wrote:
Those seem like great features Kyo! I still don't understand why that can't
be in 1.0.1 outside of an arbitrary decision that they should be in 1.0.0
though. The discuss thread for 1.0.0 was started Aug 31, the RC for 1.0.0
was posted Sep 3 with the VOTE thread. Seems a bit ridiculous to me to halt
I am so sorry that I was too busy to read all the discussion and VOTE
threads.
I am now raising issues on the decision made early September. I know that
I should have lead this discussion earlier.
Whenever we start voting for future releases, why don’t we make it sure
that all of those who have ma
Hi Folks,
Can everyone please have a look at the authoritative source on how the
VOTE'ing structure works.
http://apache.org/dev/release.html#approving-a-release
This is important for us as the result now stands at
[5] +1 release OCW 1.0.0
Michael Joyce*
Chris A. Mattmann*
Lewis McGibbney*
Daniel
Hi dev@,
As release manager I am closing off this VOTE thread as 72 has long passed.
VOTE's cast were as follows
[4] +1 release OCW 1.0.0
Michael Joyce*
Chris A. Mattmann*
Lewis McGibbney*
Daniel Gruno
[1] -1
Kyo Lee*
*OCW Project Management Committee binding VOTE
I am happy to say that the VO
It's not the PMC's job to force people to participate. That's why we can't
wait forever for people to comment. Look at how many people we have on the
PMC vs how many people we have participating in this vote thread. We would
never get a release out if we did that! As for what version increases mean
[
https://issues.apache.org/jira/browse/CLIMATE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved CLIMATE-419.
--
Resolution: Fixed
Assignee: Lewis John McGibbney
Fix Version/s:
Hi Folks,
I would like to kick off a very important and long overdue conversation
here on list, with anyone watching, monitoring and/or reading their OCW
mail, about how we can set more realistic, strategic roadmap's for
releasing the project software as official Apache releases.
Some thoughts on m
OK I sent too soon, sorry about that.
What I did notice is that both Shakeh Elisabeth Khudikyan and Kim
Whitehall's apache ID's are not correct on
http://climate.apache.org/community/people.html. I received bounced emails.
Anyway, back to the point
- OCW is under development by a small number
27 matches
Mail list logo
