shubhamvishu commented on code in PR #12930:
URL: https://github.com/apache/lucene/pull/12930#discussion_r1462861811


##########
dev-docs/codec-version-bump-howto.md:
##########
@@ -0,0 +1,74 @@
+<!--
+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.
+-->
+
+# Lucene Codec Version Bump How-To Manual
+
+Changing the name of the codec in Lucene is required for maintaining backward 
compatibility and ensuring a smooth transition for users. 
+Through explicit versioning, we isolate changes to the codec, and prevent 
unintended interactions between different codec 
+versions. Changes to the codec format version serves as a signal that a change 
in the format or structure of the index has occurred.
+
+This manual provides a step-by-step guide through the process of "bumping" the 
version of the Lucene Codec.
+
+### Fork and modify files
+* Creating a new Codec:
+  * Create a new package for your new codec of version XXX: 
`org.apache.lucene.codecs.luceneXXX`.

Review Comment:
   How about writing this how-to with the idea of changing the codec version 
from `LuceneXY` to `LuceneXZ` (?), that way I believe it'll be more clear to 
understand which codec is referenced in as opposed to writing LuceneXXX or 
saying old vs new. What do you think?



##########
dev-docs/codec-version-bump-howto.md:
##########
@@ -0,0 +1,74 @@
+<!--
+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.
+-->
+
+# Lucene Codec Version Bump How-To Manual
+
+Changing the name of the codec in Lucene is required for maintaining backward 
compatibility and ensuring a smooth transition for users. 
+Through explicit versioning, we isolate changes to the codec, and prevent 
unintended interactions between different codec 
+versions. Changes to the codec format version serves as a signal that a change 
in the format or structure of the index has occurred.
+
+This manual provides a step-by-step guide through the process of "bumping" the 
version of the Lucene Codec.
+
+### Fork and modify files
+* Creating a new Codec:
+  * Create a new package for your new codec of version XXX: 
`org.apache.lucene.codecs.luceneXXX`.

Review Comment:
   How about writing this how-to with the idea of changing the codec version 
from `LuceneXY` to `LuceneXZ` (?), that way I believe it'll be more clear to 
understand which codec is referenced in as opposed to writing `LuceneXXX` or 
saying old vs new. What do you think?



-- 
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: issues-unsubscr...@lucene.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to