Your use of the packages on this site means you understand they are not supported or guaranteed in any way. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed.
ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: No further LTS release will be made.Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. In early 2021, a decision was made to review the process and requirements for LTS releases, and in October 2021 a decision was made to concentrate solely on quarterly releases, changing the numbering scheme accordingly. At the end of 2020, master freezing was replaced by a move to a delivery and release branch mechanism. This started from Apache NetBeans 11.1, and retrospectively designated Apache NetBeans 11.0 as an LTS release.Īt the end of 2019 the schedule was shifted back by one month, to avoid the end of year period. In 2019 there was a decision to move towards a time-based, quarterly release schedule for Apache NetBeans releases. All fixes merged to delivery after the feature-freeze date should be assessed and reviewed in accordance with the Bug Priority Guidelines.The delivery branch will be merged to both master and release branches on a weekly schedule. After the feature freeze date, fixes intended for the release should be merged to delivery until the next feature window opens.Merging earlier rather than later in the merge window is to be encouraged!.Everything merged to master at all times prior to feature freeze is intended and ready to be included in the next scheduled release.Features may be targeted for releases, but no promises are made of features being included unless they have been merged to master by that date. Each release has a fixed and well known feature-freeze date.
Four releases a year on known dates (within reason, weekends, blockers, etc.).Voting candidate created and release vote commences. Weekly Release Candidate made available for testing.
0 kommentar(er)
