geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Blum <jb...@pivotal.io>
Subject Re: Concerning Apache Geode 1.7.0
Date Wed, 05 Sep 2018 21:40:50 GMT
I'd also say that, in general, those branches need to be cleaned up.  There
are a crap load of branches in there!  Are all those branches actively
developed and currently being built by a nightly CI?  I'd argue they should
be!  But, I guess not since 'release/1.7.0' is still lingering.

Also, it is common for most OSS projects to publish nightly build snapshots
(preferably from 'master', but I guess in this case, 'develop', where '
develop' should be the 1.7.0 release up to the point where 1.7.0 is
delivered, then a 1.7.x branch is created and 'master', err 'develop'
become the 1.8 development line) with the latest developments to allow
users to test drive with the latest bits, well before any release happens,
and especially before a vote, no less.

This is part of any good OSS process where their is a significant ecosystem
around the core project.  How else can downstream projects get a sense for
what is happening, collaborate on that, or if necessary, even contribute,
if we cannot test things out?

Regarding...

*> It will be unproductive of users to run their experiments on a branch
with issues.*

That is a process problem since there should not be pending changes on any
"releasable" branch that would affect core functionality, especially not
without adequate test coverage catching problems before bits are checked in.

Anyway, the point is, there needs to be some build snapshot artifacts
readily available for users/projects to consume in order for a healthy
ecosystem to thrive.

-John


On Wed, Sep 5, 2018 at 2:28 PM, Nabarun Nag <nnag@apache.org> wrote:

> @John it will be published soon. The branch is not ready yet. There are
> some known issues that need to solved before we release the branch to world
> to test.
>
> It will be unproductive of users to run their experiments on a branch with
> issues. It will be up as soon as the issues are resolved. I'm working on
> resolving them at the moment. Hopefully soon we will send out the mail and
> the updated release branch.
>
> Regards
> Nabarun Nag
>
>
> On Wed, Sep 5, 2018 at 2:22 PM John Blum <jblum@pivotal.io> wrote:
>
> > Doesn't the pending release branch, or something, publish (build)
> snapshot
> > artifacts to a snapshot repo somewhere?
> >
> > How do/can users test out the upcoming bits (that is nightly build
> snapshot
> > artifacts)?
> >
> >
> > On Wed, Sep 5, 2018 at 2:13 PM, Nabarun Nag <nnag@pivotal.io> wrote:
> >
> > > @John, the [DISCUSS] mail for the new branch has not been sent yet. The
> > > branch you are looking at is an old one that was abandoned few months
> > ago.
> > > The new branch is undergoing some preliminary tests on my local machine
> > > before getting published to the world. A mail will be sent out as soon
> as
> > > the branch is ready.
> > >
> > > Regards
> > > Nabarun Nag
> > >
> > >
> > > On Wed, Sep 5, 2018 at 2:10 PM John Blum <jblum@pivotal.io> wrote:
> > >
> > > > I see that the branch for Apache Geode 1.7.0 (release/1.7.0 [1]) has
> > been
> > > > created in preparation for the upcoming the 1.7 release.
> > > >
> > > > I am trying to get an early sense/feel for the required changes in
> SDG
> > > when
> > > > I rebase it on 1.7.
> > > >
> > > > Previously, I was able to obtain Geode snapshots from...
> > > >
> > > >
> > > > <repository>
> > > >    <id>apache-snapshots</id
> > > >    <url>https://repository.apache.org/content/repositories/snapshots
> > > </url
> > > > </repository>
> > > >
> > > >
> > > > But currently, Maven is unable to resolve the 1.7 JARs....
> > > >
> > > >
> > > > $ mvn dependency:resolve
> > > > [INFO] Scanning for projects...
> > > > [INFO]
> > > > [INFO] -------------< org.springframework.data:spring-data-geode
> > > > >-------------
> > > > [INFO] Building Spring Data Geode 2.2.0.BUILD-SNAPSHOT
> > > > [INFO] --------------------------------[ jar
> > > > ]---------------------------------
> > > > [WARNING] The POM for org.apache.geode:geode-core:jar:1.7.0 is
> missing,
> > > no
> > > > dependency information available
> > > > [WARNING] The POM for org.apache.geode:geode-cq:jar:1.7.0 is
> missing,
> > no
> > > > dependency information available
> > > > [WARNING] The POM for org.apache.geode:geode-lucene:jar:1.7.0 is
> > > missing,
> > > > no dependency information available
> > > > [WARNING] The POM for org.apache.geode:geode-wan:jar:1.7.0 is
> missing,
> > > no
> > > > dependency information available
> > > > [INFO]
> > > >
> > ------------------------------------------------------------------------
> > > > [INFO] BUILD FAILURE
> > > > [INFO]
> > > >
> > ------------------------------------------------------------------------
> > > > [INFO] Total time: 0.617 s
> > > > [INFO] Finished at: 2018-09-05T14:07:30-07:00
> > > > [INFO]
> > > >
> > ------------------------------------------------------------------------
> > > > [ERROR] Failed to execute goal on project spring-data-geode: Could
> not
> > > > resolve dependencies for project
> > > > org.springframework.data:spring-data-geode:jar:2.2.0.BUILD-SNAPSHOT:
> > > *The
> > > > following artifacts could not be resolved*:
> > > > org.apache.geode:geode-core:jar:1.7.0,
> org.apache.geode:geode-cq:jar:
> > > 1.7.0,
> > > > org.apache.geode:geode-lucene:jar:1.7.0,
> > > > org.apache.geode:geode-wan:jar:1.7.0: Failure to find
> > > > org.apache.geode:geode-core:jar:1.7.0 *in
> > > > https://repository.apache.org/content/repositories/snapshots
> > > > <https://repository.apache.org/content/repositories/snapshots>*
was
> > > cached
> > > > in the local repository, resolution will not be reattempted until the
> > > > update interval of apache-snapshots has elapsed or updates are forced
> > ->
> > > > [Help 1]
> > > >
> > > >
> > > > Is this the correct repo and are the 1.7 snapshots currently
> available?
> > > >
> > > > Thanks,
> > > >
> > > > --
> > > > -John
> > > >
> > > > [1] https://github.com/apache/geode/tree/release/1.7.0
> > > >
> > >
> >
> >
> >
> > --
> > -John
> > john.blum10101 (skype)
> >
>



-- 
-John
john.blum10101 (skype)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message