Hi Alex,
Comment below

On Fri, Jul 22, 2016 at 6:21 AM, <dev-digest-h...@climate.apache.org> wrote:

> From: "Goodman, Alexander (398K)" <alexander.good...@jpl.nasa.gov>
> To: "dev@climate.apache.org" <dev@climate.apache.org>
> Cc:
> Date: Thu, 21 Jul 2016 14:50:23 -0700
> Subject: [DISCUSS] new conda package installer and future releases
> Hi folks,
>
> I have finished creating a wiki page regarding the recently released OCW
> conda package here [1]. This includes installation information as well as a
> rough guide for maintaining the packages. Again, please test everything if
> you have not read my previous email already.
>

Nice!


>
> I would also like to raise some discussion regarding future releases. At
> this point, I think we are ready to release 1.1. The current codebase seems
> to be sufficiently stable and some big changes (the conda package and
> upcoming datasource loader) should necessitate getting this release out
> ASAP.
>

See several of my previous emails published to this list in recent weeks
and months regarding this. You are preaching to the choir. I've made
repeated attempts to define the roadmap for OCW. This can be seen at
https://issues.apache.org/jira/browse/CLIMATE/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
Very few people seem to use this roadmap as our guide for moving towards
release which is sad. However I am still trying my best to guide this
community towards more request releases based off of it. If a few of us
align on using this Roadmap feature of Jira, then we can make much more
driven development drives.


>
> Additionally, I think we should begin to schedule more frequent release
> cycles now that we have an easy to use package management system in place.
>

Again you are preaching to the choir here. I hear you entirely and I agree.
In all honesty, the main hang up has been certain people who are paranoid
about us NOT releasing due to certain features not complete or buggy. This
goes against the popular open source methodology of 'release early release
often'. The OCW project and community suffers greatly for infrequent
releases. You sum this up below... it is something we need to address.


> Frankly, close to 1 year is too long of a release cycle given the frequency
> of our commits. I think we should be making releases at least 2 or 3 times
> per year if possible.
>

Yes I agree. I am going to put a release candidate together once you commit
your code for the Conda package.

Thanks

Reply via email to