Milestones
List view
- No due date•7/7 issues closed
- No due date•1/1 issues closed
- No due date•2/2 issues closed
- No due date•2/2 issues closed
- No due date•1/1 issues closed
- No due date•41/41 issues closed
- No due date•17/17 issues closed
- No due date•4/4 issues closed
Use for non-bug fixes (new features, improvements, etc) added to the 3.0.x release.
No due date•49/49 issues closed- No due date
- No due date•2/2 issues closed
- No due date•16/16 issues closed
- Due by March 6, 2020•106/106 issues closed
- Due by March 16, 2019•14/14 issues closed
- Due by January 18, 2019•8/8 issues closed
- Due by January 18, 2019•3/3 issues closed
- Due by December 19, 2018•11/11 issues closed
- Due by December 12, 2018•4/4 issues closed
- Due by March 31, 2019•11/11 issues closed
- Due by December 7, 2018•2/2 issues closed
- No due date•18/18 issues closed
- No due date
This milestone embodies several major initiatives in the StreamAlert project. The first is Alert Merging, this creates a mechanism to merge similarly triggered alerts together. The second is Rule Staging, where new rules can be 'staged' before promoting to production to increase efficacy. Finally, CICD Support to not require pull requests from deploys. This directly enables users to use CI systems such as Travis or Jenkins to perform StreamAlert deploys. This release will also come with other great features as side effects to the projects above.
Due by June 29, 2018•179/179 issues closed- Due by March 2, 2018•22/22 issues closed
- Due by November 30, 2017•158/158 issues closed
- Due by August 8, 2017•49/49 issues closed
- Due by July 11, 2017•50/50 issues closed
- No due date•9/9 issues closed