You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2021/03/22 17:10:00 UTC
[jira] [Created] (HBASE-25690) Specify and document the criteria
for moving the 'stable' pointer
Andrew Kyle Purtell created HBASE-25690:
-------------------------------------------
Summary: Specify and document the criteria for moving the 'stable' pointer
Key: HBASE-25690
URL: https://issues.apache.org/jira/browse/HBASE-25690
Project: HBase
Issue Type: Task
Components: documentation
Reporter: Andrew Kyle Purtell
We can consider reported experience with new code lines released ahead of where the stable pointer currently points, when and if it happens but this should not be a formal criteria because it has nothing directly to do with our PMC or project. We need a criteria for deciding when new code lines are sufficiently stable as to warrant moving the 'stable' pointer that we as project and PMC can achieve and implement effectively.
IMHO "one of our project devs has it running" does not meet that requirement, because this depends on third party organizations (a dev's employer, and such) and idiosyncratic criteria.
Collect and document requirements, test scenarios, and success (and failure) criteria.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)