--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/5885e613-e225-4479-a069-da5d9fc7b75e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
1. I would say egregious and/or technical errors would be a -1. That is, it would hinder an offline user from using JanusGraph.2. If -1 and technical, it should hold up the release. Everything else should get fixed and can be published later online.3. If -1 and technical, yes.4. No, unless someone feels like the extra time is needed.To apply this to the current release, the outstanding issue involves minor link errors. There is nothing that would prevent a user from comprehending documentation or using JanusGraph. If the user were viewing offline (the packaged documentation), then the links wouldn't work anyway. The corrected documentation can be published online which is done separately from building the artifacts thus no need to rebuild artifacts.
Robert Dale
Thanks, Robert. I agree with that approach also.
Still interested in hearing other opinions or affirmations.
On Friday, October 13, 2017 at 10:40:36 AM UTC-4, Robert Dale wrote:
1. I would say egregious and/or technical errors would be a -1. That is, it would hinder an offline user from using JanusGraph.2. If -1 and technical, it should hold up the release. Everything else should get fixed and can be published later online.3. If -1 and technical, yes.4. No, unless someone feels like the extra time is needed.To apply this to the current release, the outstanding issue involves minor link errors. There is nothing that would prevent a user from comprehending documentation or using JanusGraph. If the user were viewing offline (the packaged documentation), then the links wouldn't work anyway. The corrected documentation can be published online which is done separately from building the artifacts thus no need to rebuild artifacts.
Robert Dale
On Fri, Oct 13, 2017 at 10:03 AM, Jason Plurad wrote:
I want to bring this up since it isn't clearly listed out in the current release policy docs.
There has been one issue so far that has been identified during the vote on the 0.2.0 release.
1. What types of issues qualify for a -1 vote?
2. Should a doc error hold up the release or should it be fixed?
3. If the docs are fixed, do we rebuild the release artifacts, update the tags, etc?
4. Does the voting clock get reset?
--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/CABed_4rLM%3DO_M4f%3DfB8PwEAaXnACD8R7WuFW4MLdq5FB_YtOHg%40mail.gmail.com.
I'm with Robert on this, and I should also point out these links have been broken since the 0.1.0 release, and no one has yet complained (or discovered) them other than Robert.Another way to think about it is as follows: imagine the 0.2.0 release happened, and we then realized some HTML links are broken. We can't "recall" the 0.2.0 release then, so the only thing we would be able to do is to release an 0.2.1 with updated docs, but I don't think that's a sufficient reason to call for a release, so we would either fix the docs in-place (*) or leave them broken until 0.3.0 release (**).In this case, we are choosing between (*) or (**). I am not the release manager, so it's easy to request all binary artifacts to be rebuilt, but I just don't see the value of spending that time/effort — they will be effectively the same, and while not bit-for-bit identical, they will be indistinguishable from the user perspective.In summary, I'm fine with either shipping the artifacts as-is with the minor doc fixes. Alternatively, if we are going for strictness, we can leave the artifacts as-is and push the docs with links known to be broken, consistent with 0.1.0 and 0.1.1 releases, and the updated docs will be pushed with the next 0.2.x or 0.3.0 release.
I'm fine with either of these options.
On Fri, Oct 13, 2017 at 10:40 AM, Robert Dale wrote:
1. I would say egregious and/or technical errors would be a -1. That is, it would hinder an offline user from using JanusGraph.2. If -1 and technical, it should hold up the release. Everything else should get fixed and can be published later online.3. If -1 and technical, yes.4. No, unless someone feels like the extra time is needed.To apply this to the current release, the outstanding issue involves minor link errors. There is nothing that would prevent a user from comprehending documentation or using JanusGraph. If the user were viewing offline (the packaged documentation), then the links wouldn't work anyway. The corrected documentation can be published online which is done separately from building the artifacts thus no need to rebuild artifacts.
Robert Dale
On Fri, Oct 13, 2017 at 10:03 AM, Jason Plurad wrote:I want to bring this up since it isn't clearly listed out in the current release policy docs.--
There has been one issue so far that has been identified during the vote on the 0.2.0 release.
1. What types of issues qualify for a -1 vote?
2. Should a doc error hold up the release or should it be fixed?
3. If the docs are fixed, do we rebuild the release artifacts, update the tags, etc?
4. Does the voting clock get reset?
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/5885e613-e225-4479-a069-da5d9fc7b75e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Robert Dale
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/5885e613-e225-4479-a069-da5d9fc7b75e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.