---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52468/#review151125
---
Ship it!
Ship It!
- Kirk Lund
On Oct. 2, 2016, 12:07 a.m.,
Did you mean a new top-level dir (e.g. geode-docs) or a subdir of geode-core?
Since the docs could cover multiple components I’m not sure it makes sense to
put them under geode-core.
Anthony
>
> I think we should just go ahead and create a feature branch off of the the
> current geode
I reviewed a bunch of CI failures today. I closed out duplicates and added the
‘CI’ label to JIRA tickets that were missing it. I just posted a big review to
add the FlakyTest category to bugs with non-reproducible failures—pretty much
any CI bug that is currently open. Your comments are
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52468/
---
Review request for geode.
Repository: geode
Description
---
Annotate
Thanks Anthony & Mark.
For 116 issues that matched the filter: "project = GEODE AND status in
(Resolved, Closed) AND fixVersion = EMPTY"
I set the fix version as 1.0.0-incubating.
Going forward please only mark the issues fixed on the release branch with
1.0.0-incubating version.
Thanks!
Version 1.1.0-incubating has now been created in JIRA.
--Mark
On Saturday, October 1, 2016, Anthony Baker wrote:
> Thanks Swapnil!
>
> I bumped the version on develop to 1.1.0-incubating. Can someone with
> JIRA karma could create the corresponding JIRA version? As we
Thanks Swapnil!
I bumped the version on develop to 1.1.0-incubating. Can someone with JIRA
karma could create the corresponding JIRA version? As we resolve issues on the
develop branch we should set the Fix Version as 1.1.0-incubating.
I also removed the -SNAPSHOT qualifier from the
Based on the " Limiting scope for Geode 1.0" thread [1] I have cut a branch
release/1.0.0-incubating from develop on commit
abef045179e5d805cb04bc55a77a82798becdaae for the 1.0 release. Please make
sure that only issues targeted for 1.0 [2] are fixed on that branch. If you
are using git flow, use
Thanks for the offer Anthony,
I tagged GEODE-17 / GEODE-1570 to be fixed in 1.0 and I removed the 1.0 tag
from GEODE-1793 so that open JIRA issues for 1.0 [1] should now be accurate.
I have also cut a branch release/1.0.0-incubating from develop on commit
abef045179e5d805cb04bc55a77a82798becdaae
On Fri, Sep 30, 2016 at 10:57 PM, Greg Chase wrote:
> With the number of hats you have Roman, you can satisfy any diversity
> requirement...
This may be helpful to fully understand the phenomenon:
http://tinyurl.com/origin-of-shaposhnik
Thanks,
Roman.
10 matches
Mail list logo