Hi Alex, Responses inline On Wed, Oct 19, 2016 at 6:31 PM, <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: Wed, 19 Oct 2016 18:25:35 -0700 > Subject: Re: Preparatory work for 1.2.0 Release > Also, one thing I would like to add is that the dependency issues we are > seeing with the CI tests have been happening since this commit > > https://github.com/apache/climate/commit/98020c9fe7654267d03 > f8553f35af4ca9ed55952 > Good catch! > > Based on the raw logs from the CI tests, it seems like the dependencies are > being downloaded but setuptools can't find them. We could revert this > commit but that would be pointless anyway since we now also want to test > for Python 3.x. Yeah. I think that having CI 'unstable' for now is a reasonable temporary sacrifice for us actually fixing the issue. > Thus, solving this issue may be tied to CLIMATE-879 (put > the conda recipe on conda-forge) and CLIMATE -874 (Remove Easy OCW and > replace with a pure conda installation method). All have been remarked for 1.2.0. > Only thing to keep in mind > is that if we go down this route, we won't be able to have a fully > functional CI test-suite for Python 3.x until AFTER the 1.2.0 package is > uploaded. I just woke up... can you expand a bit? Why is this the case? > Thus, I think we will need to do before officially releasing > 1.2.0: > > 1) Get 1.1.0 on conda-forge [0] > 2) Make ocw compatible with podaacpy 1.4.0 [1] > Both of the above seem fine. > 3) Put 1.2.0 release candidate on PyPI AND THEN conda-forge > This is a bit tricky, the reason I say is that we can put a release candidate into test.pypi.org but not on to pypi.org. The former is fine, the latter would constitute a release... which is not what we are trying to do unless we are actually releasing. > 4) Update CI testing to download all packages via conda and fully > deprecating Easy-OCW > ack, however could this not be done prior to releasing 1.2.0? > 5) If resolved, we are ready to release > > [0] https://github.com/conda-forge/staged-recipes/pull/1784 > [1] https://github.com/apache/climate/pull/411 > > What do you think? > >
