@jake, I'm sure we will better utilize the CI pipeline infra from now on.
On 9/5/18 16:47, Jacob Barrett wrote:
We should be utilizing a CI to fix these issues.
On Sep 5, 2018, at 4:46 PM, Nabarun Nag wrote:
As mentioned in the previous emails, we are still working on fixing issues.
On We
We should be utilizing a CI to fix these issues.
> On Sep 5, 2018, at 4:46 PM, Nabarun Nag wrote:
>
> As mentioned in the previous emails, we are still working on fixing issues.
>
>> On Wed, Sep 5, 2018 at 4:42 PM Jacob Barrett wrote:
>>
>> Why hasn’t the CI pipeline been created though? How
As mentioned in the previous emails, we are still working on fixing issues.
On Wed, Sep 5, 2018 at 4:42 PM Jacob Barrett wrote:
> Why hasn’t the CI pipeline been created though? How can we be validating
> the changes going into this branch if there isn’t a CI? If there was a CI
> in place the sn
Why hasn’t the CI pipeline been created though? How can we be validating the
changes going into this branch if there isn’t a CI? If there was a CI in place
the snapshots would be published on clean builds.
-Jake
> On Sep 5, 2018, at 3:04 PM, Nabarun Nag wrote:
>
> @John, everything you menti
Thanks
On Wed, Sep 5, 2018 at 3:19 PM, Dan Smith wrote:
> Please see my reply on the other thread - there are nightly snapshots of
> the develop branch that's probably do what you need.
>
> For the release branch, when we create a release candidate we also create a
> staging maven repository wit
Please see my reply on the other thread - there are nightly snapshots of
the develop branch that's probably do what you need.
For the release branch, when we create a release candidate we also create a
staging maven repository with the release that you can test against. Watch
for a VOTE email from
Hi there John,
I've started another thread, wrt nightly snapshots. Hopefully we will
have an answer for you soon.
--Udo
On 9/5/18 15:10, John Blum wrote:
I just need nightly build snapshots (with artifacts accessible from a
snapshot repo) on a regular basis. That will eventually include th
For the nightly build snapshot hosting, it will have to go through
[DISCUSS] -> [VOTE] , then implemented.
Currently, it is out of scope for the 1.7.0 release process.
Regards
Nabarun Nag
On Wed, Sep 5, 2018 at 3:10 PM John Blum wrote:
> I just need nightly build snapshots (with artifacts acces
I just need nightly build snapshots (with artifacts accessible from a
snapshot repo) on a regular basis. That will eventually include the 1.8
bits too.
Anyway, thank you for you efforts and straightening out the bits for 1.7.
Will there be build snapshots available to test with?
If at all possib
@John, everything you mentioned in mail is how things happen in Apache
Geode where we cut a release branch and develop moves to the SNAPSHOT
version for the next release.
But as we mentioned in the release mails, 1.7.0 needs some special work
done.
We created the release branch for 1.7.0 and moved
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
@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 work
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 wrote:
> @John, the [DISCUSS] mail for the new
@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 br
The artifacts probably have not been uploaded yet. I would wait for a vote
thread on the release candidate.
On Wed, Sep 5, 2018 at 2:10 PM John Blum 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
15 matches
Mail list logo
