kou commented on code in PR #1762: URL: https://github.com/apache/arrow-adbc/pull/1762#discussion_r1580296606
########## dev/release/versions.env: ########## @@ -0,0 +1,30 @@ +# 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. + +# The release as a whole has a date-based identifier. This is used to +# identify tags, branches, and so on. +RELEASE="2024.05.06" Review Comment: > What do you think of just using a counter in that case then? (2024.1, 2024.2, 2024.3) It will work too! It may be confused but we may be able to omit the `2024.` part: `1`, `2`, `3` We need to choose the next identifier when we publish a new release. If we use date-based identifier, it may be difficult. For example, we want to publish a next release in this year but it may be slipped to the next year. (Should we choose the next identifier when we publish the next release?) -- 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]
