Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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

Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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

[jira] [Updated] (CLIMATE-668) ocw.dataset_spatial_resolution needs to be fixed

[ 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 >

[jira] [Updated] (CLIMATE-666) Replace examples with the RCMES script and yaml files

[ 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 >

[jira] [Created] (CLIMATE-675) Latitude and longitude resolution on CLI should not be always equal

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:

[jira] [Updated] (CLIMATE-671) Inappropriate spatial subset for datasets on curvilinear grids

[ 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 >

Re: [VOTE] Release Apache Open Climate Workbench 1.0.0

+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

[jira] [Closed] (CLIMATE-663) ocw-config-runner need to be ocw_config_runner

[ 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

Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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

Re: [DISCUSS] Setting Roadmaps for OCW Moving Forward

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

[GitHub] climate pull request: spatial resolution for lat and lon can be di...

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

[GitHub] climate pull request: spatial resolution for lat and lon can be di...

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

[GitHub] climate pull request: spatial resolution for lat and lon can be di...

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] climate pull request: spatial resolution for lat and lon can be di...

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

Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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

[GitHub] climate pull request: spatial resolution for lat and lon can be di...

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

Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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

Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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

Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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"

Re: [VOTE] Release Apache Open Climate Workbench 1.0.0

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

Re: dev Digest 23 Sep 2015 16:49:12 -0000 Issue 411

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

[jira] [Resolved] (CLIMATE-419) Add HUGE download button to main site

[ 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:

[DISCUSS] Setting Roadmaps for OCW Moving Forward

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