Re: [DISCUSS] What is a "Blocker" in our JIRA?

My reference to post-hoc was in regards to release. Concurrent dev and doc is of course ideal but I think anyone running snapshot is aware that docs may be somewhat out of sync. A better link discussing unreleased publication: http://www.apache.org/legal/release-policy.html#publication Our

Re: [DISCUSS] What is a "Blocker" in our JIRA?

On Fri, May 5, 2017 at 2:24 PM, Greg Hogan wrote: > -1 to post-hoc documentation and unreleased publication [0] Could you quickly confirm that I understand this correctly: - Post-hoc documentation means not documenting features separately from their initial PRs? - Unreleased

Re: [DISCUSS] What is a "Blocker" in our JIRA?

+1 to restricting use of “blocker" -1 to post-hoc documentation and unreleased publication [0] [0] http://www.apache.org/dev/release-publishing.html > On May 5, 2017, at 5:06 AM, Ufuk Celebi wrote: > > Thanks for this discussion Robert. I agree with your points. +1 > >

Re: [DISCUSS] What is a "Blocker" in our JIRA?

I agree with Robert’s suggestion and also vote for unblocking documentation issues. > Am 05.05.2017 um 11:06 schrieb Ufuk Celebi : > > Thanks for this discussion Robert. I agree with your points. +1 > > Regarding the documentation: I also agree with Kostas and others that > it

Re: [DISCUSS] What is a "Blocker" in our JIRA?

Thanks for this discussion Robert. I agree with your points. +1 Regarding the documentation: I also agree with Kostas and others that it is very important to have good documentation in place. The good thing about our current doc deployment model is that we can update the docs for a released

Re: [DISCUSS] What is a "Blocker" in our JIRA?

I understand the motivation to make documentation equally important as bugs in software, but from my point of view as a release manager, its not easy to keep track of the release status when some blockers are not real blockers (I can't just look at the number in JIRA, but I have to manually go

Re: [DISCUSS] What is a "Blocker" in our JIRA?

IMHO, the problem with the “add documentation” issues is that they should ideally have been documented as part of the feature development. (Full disclosure: I’m not innocent there and the Per-Key Window State Doc is somewhat my fault.) Sometimes, though, several features are developed over the

Re: [DISCUSS] What is a "Blocker" in our JIRA?

I agree with Kostas. Considering 1.3 has many new features which need non-trivial effort for testing, maybe the work on documentation can be done in parallel to testing RC0. Cheers On Thu, May 4, 2017 at 10:54 AM, Kostas Kloudas wrote: > Hi Robert, > > Thanks for

Re: [DISCUSS] What is a "Blocker" in our JIRA?

Hi Robert, Thanks for clarifying this so that we all have a common definition of what is a blocker. The only thing I would disagree, and only is some cases, is the documentation part. I think that in some cases, things that have to do with documentation can and should become blockers. Mainly

[DISCUSS] What is a "Blocker" in our JIRA?

Hi Flink Devs, while checking our JIRA for the 1.3 release, I found that some issues of type "New Feature" have the priority "Blocker". With the time-based release model, I don't think its possible to mark a new feature as a blocker. Only a bug that leads to wrong results, system failure or