mark code.* attributes as release candidate

.chloggen/1599.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: code
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Mark code semantic conventions as release candidate
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [ 1377 ]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

internal/tools/go.mod

@@ -1,6 +1,6 @@
 module github.com/open-telemetry/opentelemetry-specification/internal/tools
 
-go 1.22
+go 1.22.0
 
 require (
 	github.com/client9/misspell v0.3.4

model/code/registry.yaml

@@ -7,38 +7,38 @@ groups:
     attributes:
       - id: code.function
         type: string
-        stability: experimental
+        stability: experimental # RELEASE CANDIDATE
         brief: >
           The method or function name, or equivalent (usually rightmost part of the code unit's name).
         examples: serveRequest
       - id: code.namespace
         type: string
-        stability: experimental
+        stability: experimental # RELEASE CANDIDATE
         brief: >
           The "namespace" within which `code.function` is defined. Usually the qualified class or module name,
           such that `code.namespace` + some separator + `code.function` form a unique identifier for the code unit.
         examples: com.example.MyHttpService
       - id: code.filepath
         type: string
-        stability: experimental
+        stability: experimental # RELEASE CANDIDATE
         brief: >
           The source code file name that identifies the code unit as uniquely as possible (preferably an absolute file path).
         examples: /usr/local/MyApplication/content_root/app/index.php
       - id: code.lineno
         type: int
-        stability: experimental
+        stability: experimental # RELEASE CANDIDATE
         brief: >
           The line number in `code.filepath` best representing the operation. It SHOULD point within the code unit named in `code.function`.
         examples: 42
       - id: code.column
         type: int
-        stability: experimental
+        stability: experimental # RELEASE CANDIDATE
         brief: >
           The column number in `code.filepath` best representing the operation. It SHOULD point within the code unit named in `code.function`.
         examples: 16
       - id: code.stacktrace
         type: string
-        stability: experimental
+        stability: experimental # RELEASE CANDIDATE
         brief: >
           A stacktrace as a string in the natural representation for the language runtime.
           The representation is to be determined and documented by each language SIG.