As a podling, I recommend that users upgrade to the latest available version during the incubation period.
Furthermore, we must take all security issues seriously. Any security issue discovered within a release milestone should be treated as a top priority. The release plan should be openly discussed in the community to determine whether to wait for the milestone version or to release an emergency hotfix version. Best Regards, Delei Shuxin Pan <[email protected]> 于2026年6月1日周一 23:35写道： > > Hi all, > > While working on recent release planning, I realized that we have not > yet formally defined a version support and release maintenance policy > for Apache Fesod (Incubating). > > As a podling, our development is still evolving rapidly, and our > community and user base are continuing to grow. My initial thought is > that keeping the policy simple may be the most practical approach at > this stage. > > For example: > > - Only the latest release line is officially supported during incubation. > - Users are encouraged to upgrade to the latest available release. > - Bug fixes and maintenance updates are generally provided only for > the latest release line. > - Older release lines may not receive additional fixes unless the > community decides otherwise. > > After graduation, or once the project reaches a more mature stage, we > could revisit this policy and consider maintaining previous release > lines for a limited period of time. > > I'd like to hear how others think we should approach: > > - Version support expectations > - Maintenance of older release lines > - Patch release strategy > - Criteria for declaring a version no longer supported > > Please share your thoughts and experiences. > > Best regards, > Shuxin Pan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
