You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the feature freeze period, we will not accept new feature pull requests to Gazebo.
34
+
This includes new features to the upcoming release as well as to currently stable versions. The focus will be reviewing open pull requests that are likely to be merged before the code freeze starts.
35
+
If you have a new feature you want to contribute, please open a PR before we go into feature freeze noting that changes can be made to open pull requests during the feature freeze period.
36
+
37
+
***Initial Two-Week Review Period:** For the first two weeks following the feature freeze date, all branches remain frozen to *new-feature pull requests opened after the deadline*.
38
+
During this time, our focus is to review, merge, and forward-port eligible pull requests that were submitted *before* the freeze began.
39
+
***Unfreezing Stable Branches:** After this initial two-week period, branches for older, stable Gazebo releases will be "unfrozen." New-feature pull requests targeting these branches can once again be opened and merged.
40
+
***Protecting the `main` Branch:** To ensure the stability of the upcoming release, features merged into stable branches during the freeze **will not** be forward-ported to `main` until after the release is complete.
41
+
42
+
**Exception**: Branches shared between the upcoming release and older releases (which can happen to slowly changing packages such as `gz-cmake`) will remain fully frozen for the entire duration of the freeze.
43
+
44
+
#### Code Freeze
45
+
46
+
After the code freeze date, only critical bug fixes and documentation updates may be merged.
47
+
48
+
#### Tutorial Party
49
+
50
+
To make sure we have the best release possible the team goes over all the tutorials using pre-releases to check that everything is working as it should and make final tweaks.
51
+
We invite the community to join the party! If you are new to Gazebo, this would be a great opportunity to get your feet wet.
52
+
The tutorial party is also a great way for prospective interns and GSoC students to get familiar with Gazebo, meet the community, and close their first Github issue.
53
+
The tutorials are hosted on https://github.com/gazebosim/gazebo_test_cases and instructions will be posted on [Discourse](https://discourse.openrobotics.org/) a few weeks before the party starts.
54
+
55
+
#### Internal QA/Demo Preparation
56
+
57
+
Every year, the Gazebo team prepares a demo to showcase all the new features in the upcoming release. During this period, the team works on finalizing the demo as well as making final package releases.
58
+
59
+
#### Community Meeting
60
+
61
+
The demo mentioned above is presented to the community.
62
+
63
+
#### Official Announcement
64
+
65
+
The official release announcement is made on [Discourse](https://discourse.openrobotics.org/).
66
+
24
67
## Planned releases
25
68
26
69
Please see the [Releases](https://github.com/gazebosim/docs/blob/master/releases.md) for the timeline of and information about future distributions.
0 commit comments