nizhikov commented on code in PR #13740: URL: https://github.com/apache/ignite/pull/13740#discussion_r4389408774
########## rfcs/IGNITE-29201-public-api-and-rfc-process.md: ########## @@ -0,0 +1,66 @@ +<!-- +Licensed to the Apache Software Foundation (ASF) under one or more +contributor license agreements. See the NOTICE file distributed with +this work for additional information regarding copyright ownership. +The ASF licenses this file to You under the Apache License, Version 2.0 +(the "License"); you may not use this file except in compliance with +the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. +--> + +# Public API changes through tickets and PRs + +Ticket: [IGNITE-29201](https://issues.apache.org/jira/browse/IGNITE-29201) + +## Why + +We should agree on changes to public API before merging them. Use a ticket to describe the problem and a PR to review an RFC stored alongside the code. Review Comment: public API has rules on how to change it, already. But, we don't have clear definition of what public API are. So, we have two goals that must be adressed in different RFCs in my optinion: 1. Give clear definition of public API and public behavior in Apache Ignite. 2. Define (change) process of creation, changes or removal public API. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
