This change includes the following:

* Added the topic Implementing Editions Support
* Corrected code in the Editions overview topic
* Added a news entry for dropping support for building Protobuf Java from source with Maven
* Added a section about message type fields having presence to the proto3 topic
* Added clarifying information to the Go Generated Code topic
* Corrected the syntax for options in the proto2 and proto3 spec topics

PiperOrigin-RevId: 646953738
Change-Id: I2a3306a3ff49da39769e3e6166152a938137fde6

Author: Protocol Buffer Team

content/editions/_index.md

@@ -7,3 +7,4 @@ type = "docs"
 
 *   [Protocol Buffers Overview](/editions/overview)
 *   [Feature Settings for Editions](/editions/features)
+*   [Implementing Editions Support](/editions/implementation)

content/editions/implementation.md

@@ -244,7 +244,7 @@ option features.enum_type = CLOSED;
 
 message Person {
   string name = 1;
-  int32 id = 2 [features.presence = IMPLICIT];
+  int32 id = 2 [features.field_presence = IMPLICIT];
 
   enum Pay_Type {
     PAY_TYPE_UNSPECIFIED = 1;

content/editions/overview.md

@@ -0,0 +1,24 @@
++++
+title = "Changes Announced on June 26, 2024"
+linkTitle = "June 26, 2024"
+toc_hide = "true"
+description = "Changes announced for Protocol Buffers on June 26, 2024."
+type = "docs"
++++
+
+## Dropping Support for Building Protobuf Java from Source with Maven
+
+We are planning to drop support for building Protobuf Java OSS from source with
+the Maven build system in the Protobuf Java 4.28 release. This has been marked
+deprecated in the 4.27 release.
+
+After this point, you can continue to use Bazel, or another build system, to
+build Protobuf. You can read more about building from source in
+[the Protobuf Java README](https://github.com/protocolbuffers/protobuf/tree/main/java).
+
+This change may impact Protobuf Java contributors that build protobuf from
+source. It does not impact the majority of users that uses the precompiled
+protobuf-java or protobuf-javalite artifacts from a repository. Note
+specifically that we do not plan to stop supporting the ability to compile
+gencode with Maven, and we plan to continue to make prebuilt artifacts available
+in the Maven Central repository.

content/news/2024-06-26.md

@@ -20,6 +20,8 @@ New news topics will also be published to the
 The following news topics provide information in the reverse order in which it
 was released.
 
+*   [June 26, 2024](/news/2024-06-26) - Dropping support
+    for building Protobuf Java from source with Maven
 *   [February 27, 2024](/news/2024-02-27) - Dropping
     support for older versions of Ruby
 *   [February 5, 2024](/news/2024-02-05) - Breaking

content/news/_index.md

@@ -151,6 +151,31 @@ parser will accept the input, but only uses the last field. So, the "bytes" may
 not be "well-formed" but the resulting message would have only one and would be
 "well-formed" (but would not roundtrip the same).
 
+#### Message Type Fields Have Field Presence {#field-presence}
+
+In proto3, message-type fields already have field presence. Because of this,
+adding the `optional` modifier doesn't change the field presence for the field.
+
+The definitions for `Message2` and `Message3` in the following code sample
+generate the same code for all languages, and there is no difference in
+representation in binary, JSON, and TextFormat:
+
+```proto
+syntax="proto3";
+
+package foo.bar;
+
+message Message1 {}
+
+message Message2 {
+  Message1 foo = 1;
+}
+
+message Message3 {
+  optional Message1 bar = 1;
+}
+```
+
 ### Adding More Message Types {#adding-types}
 
 Multiple message types can be defined in a single `.proto` file. This is useful

content/programming-guides/proto3.md

@@ -38,13 +38,15 @@ Where in the output directory the generated `.pb.go` file is placed depends on
 the compiler flags. There are several output modes:
 
 -   If the `paths=import` flag is specified, the output file is placed in a
-    directory named after the Go package's import path. For example, an input
+    directory named after the Go package's import path (such as one provided by
+    the `go_package` option within the `.proto` file). For example, an input
     file `protos/buzz.proto` with a Go import path of
     `example.com/project/protos/fizz` results in an output file at
     `example.com/project/protos/fizz/buzz.pb.go`. This is the default output
     mode if a `paths` flag is not specified.
 -   If the `module=$PREFIX` flag is specified, the output file is placed in a
-    directory named after the Go package's import path, but with the specified
+    directory named after the Go package's import path (such as one provided by
+    the `go_package` option within the `.proto` file), but with the specified
     directory prefix removed from the output filename. For example, an input
     file `protos/buzz.proto` with a Go import path of
     `example.com/project/protos/fizz` and `example.com/project` specified as the

content/reference/go/go-generated.md

@@ -148,7 +148,8 @@ language guide.
 
 ```
 option = "option" optionName  "=" constant ";"
-optionName = ( ident | "(" ["."] fullIdent ")" )
+optionName = ( ident | bracedFullIdent ) { "." ( ident | bracedFullIdent ) }
+bracedFullIdent = "(" ["."] fullIdent ")"
 ```
 
 For examples:

content/reference/protobuf/proto2-spec.md

@@ -151,7 +151,8 @@ language guide.
 
 ```
 option = "option" optionName  "=" constant ";"
-optionName = optionNamePart { "." optionNamePart }
+optionName = ( ident | bracedFullIdent ) { "." ( ident | bracedFullIdent ) }
+bracedFullIdent = "(" ["."] fullIdent ")"
 optionNamePart = { ident | "(" ["."] fullIdent ")" }
 ```