Can you generate the jiras that would be included in the release?
On November 16, 2018 at 10:05:50, Justin Leet (justinjl...@gmail.com) wrote: Given that we've had a couple major PRs (the ES client migration along with the Angular upgrade stuff, and I'm sure others), I'd be in favor of releasing both the plugin and the main repo. I'd be in favor of doing something like: metron-bro-plugin-kafka release 0.3.0 PR to update full dev metron release 0.7.0 (given that things changed a good amount) I would also expect this process to most likely be kicked off post Thanksgiving break (Thursday 22nd and Friday 23rd for anybody not in the US). I can kick out another summarization thread if we want, but basically: * Nov 26 - Start the Bro plugin release process * Once that finishes, PR to update full dev with new plugin version * Once PR is in, start metron release process (hopefully) sometime the week of the 3rd? Are there any objections to staggering the releases like that? They could also be done together, but it means that we have to update full dev to match the plugin version post release. On Wed, Nov 14, 2018 at 10:29 AM zeo...@gmail.com <zeo...@gmail.com> wrote: > In my opinion metron-bro-plugin-kafka is ready for a release. Anything > else people would want to see? Once it gets released, I would like to > update full dev to use the newest version prior to any future metron > release (0.6.1 or whatever we choose). > > Jon > > On Wed, Nov 7, 2018 at 8:07 PM zeo...@gmail.com <zeo...@gmail.com> wrote: > > > So, about this release, anybody have time to review > > apache/metron-bro-plugin-kafka#2 and apache/metron-bro-plugin-kafka#13? > > > > Jon > > > > On Wed, Oct 17, 2018 at 10:37 AM Michael Miklavcic < > > michael.miklav...@gmail.com> wrote: > > > >> And I do think we will be ready to roll another Metron release in the > near > >> future as well. > >> > >> On Wed, Oct 17, 2018 at 8:26 AM Justin Leet <justinjl...@gmail.com> > >> wrote: > >> > >> > I tend to agree with Mike. I think we could do a release of the main > >> > project and get benefit, but I think skipping this cycle (especially > >> since > >> > we had a release last month) let's us get things like the ES client > >> > migration in and settled and just generally make recommending a newer > >> > version easier. > >> > > >> > The main reason for doing a release for the Bro plugin is to address > >> > shortcomings that we discovered and are addressing. > >> > > >> > On Tue, Oct 16, 2018 at 4:42 PM Michael Miklavcic < > >> > michael.miklav...@gmail.com> wrote: > >> > > >> > > Migrating the ES client, refactoring parser bolt. There are some > >> > interface > >> > > changes in flight right now that I think would be beneficial to see > in > >> > the > >> > > next release. > >> > > > >> > > On Tue, Oct 16, 2018 at 2:01 PM Nick Allen <n...@nickallen.org> > >> wrote: > >> > > > >> > > > I am in favor of a release for both. > >> > > > > >> > > > There are a lot of really useful bug fixes, management of pcap > >> through > >> > > > Ambari, more flexibility for configuring JAAS in Ambari, increased > >> > > > Elasticsearch performance, the Syslog parser, and the Batch > >> Profiler, > >> > > among > >> > > > others. I would be happy with calling it a 0.6.1 point release. > >> > > > > >> > > > Mike - What is outstanding that you would like to see in the > >> release? > >> > > > > >> > > > On Tue, Oct 16, 2018, 12:21 PM Michael Miklavcic < > >> > > > michael.miklav...@gmail.com> wrote: > >> > > > > >> > > > > I'd be +1 on going with just the metron-bro-kafka-plugin > release. > >> It > >> > > > seems > >> > > > > like it's ready to go, and I think there are a few more things > I'd > >> > like > >> > > > to > >> > > > > see get into our next Metron release so I'm good with holding > off > >> > > there. > >> > > > > > >> > > > > Mike > >> > > > > > >> > > > > On Tue, Oct 16, 2018 at 10:26 AM Justin Leet < > >> justinjl...@gmail.com> > >> > > > > wrote: > >> > > > > > >> > > > > > Hi all, > >> > > > > > > >> > > > > > As you might recall from a prior discussion about release > >> cadence, > >> > we > >> > > > > were > >> > > > > > interested in initiating release threads near our board > reports > >> to > >> > > see > >> > > > if > >> > > > > > we wanted to do releases or not. Additionally, the work is > done > >> to > >> > do > >> > > > two > >> > > > > > separate releases, so our options are releasing both, a single > >> one, > >> > > or > >> > > > > > neither. > >> > > > > > > >> > > > > > Having said that, a metron-bro-kafka-plugin 0.3.0 release came > >> up > >> > on > >> > > > this > >> > > > > > thread > >> > > > > > < > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > https://lists.apache.org/thread.html/3c18c3aba6b436b11032831e7db541d50eb7cb1e3ae54b7423057c88@%3Cdev.metron.apache.org%3E > >> > > > > > >. > >> > > > > > In particular, the prospect of a release came up in the > context > >> of > >> > > > > having a > >> > > > > > version with better (and working) testing. > >> > > > > > > >> > > > > > Version Number > >> > > > > > If we choose to do a core Metron release, I propose 0.6.1. For > >> > > > > > metron-bro-kafka-plugin, I propose 0.3.0. Keep in mind, the > >> > > versioning > >> > > > > for > >> > > > > > the plugin is a bit different in that we need x.y for bro-pkg, > >> > > instead > >> > > > of > >> > > > > > x.y.z, so we wouldn't release 0.2.1. > >> > > > > > > >> > > > > > I would personally be in favor of doing a plugin release, but > >> I'm > >> > > less > >> > > > > > inclined to do a core Metron release. > >> > > > > > > >> > > > > > For Metron, I believe the main feature is the batch profiler > >> work, > >> > > but > >> > > > > > there's a fair amount of fixes and improvements. > >> > > > > > > >> > > > > > For the plugin, I believe the main improvements would be > around > >> the > >> > > > > fixing > >> > > > > > our testing and more maintenance type work. > >> > > > > > > >> > > > > > JIRA status > >> > > > > > *metron* > >> > > > > > There are 24 opens PRs at > >> https://github.com/apache/metron/pulls. > >> > > If > >> > > > we > >> > > > > > do > >> > > > > > decide to release, we should work on getting anything meriting > >> > > > inclusion > >> > > > > > closed out. > >> > > > > > > >> > > > > > There have been 49 commits since the 0.6.0 release (listed at > >> the > >> > end > >> > > > of > >> > > > > > the message). This assumes a release from master. > >> > > > > > > >> > > > > > *metron-bro-kafka-plugin* > >> > > > > > There are 6 open PRs at > >> > > > > > https://github.com/apache/metron-bro-plugin-kafka/pulls. If > >> we do > >> > > > > decide > >> > > > > > to release, we should get anything we need closed out. > >> > > > > > > >> > > > > > There have been 2 commits since the 0.2.0 release (listed at > the > >> > end > >> > > of > >> > > > > the > >> > > > > > message). This assumes a release from master. > >> > > > > > > >> > > > > > *Metron changelog* > >> > > > > > METRON-1801 Allow Customization of Elasticsearch Document > ID > >> > > > > > (nickwallen) closes apache/metron#1218 > >> > > > > > METRON-1799 Remove outdated bylaws from site. (justinleet) > >> > closes > >> > > > > > apache/metron#1216 > >> > > > > > METRON-1769 Script creation of a release candidate > >> (justinleet) > >> > > > > closes > >> > > > > > apache/metron#1188 > >> > > > > > METRON-1761 Allow a grok statement to be applied to each > >> line > >> > in > >> > > a > >> > > > > > file. (ottobackwards) closes apache/metron#1184 > >> > > > > > METRON-1813 Stellar REPL Not Initialized with Client JAAS > >> > > > > (nickwallen) > >> > > > > > closes apache/metron#1232 > >> > > > > > METRON-1812: Fix dependencies_with_url.csv (mmiklavc via > >> > > mmiklavc) > >> > > > > > closes apache/metron#1230 > >> > > > > > METRON-1811 Alert Search Fails When Sorting by Alert > Status > >> > > > > (merrimanr) > >> > > > > > closes apache/metron#1231 > >> > > > > > METRON-1809 Support Column Oriented Input with Batch > >> Profiler > >> > > > > > (nickwallen) closes apache/metron#1229 > >> > > > > > METRON-1806: Upgrade Maven Shade Plugin version (mmiklavc > >> via > >> > > > > mmiklavc) > >> > > > > > closes apache/metron#1224 > >> > > > > > METRON-1792 Simplify Profile Definitions in Integration > >> Tests > >> > > > > > (nickwallen) closes apache/metron#1211 > >> > > > > > METRON-1807 Auto populate the recommended values to some > of > >> the > >> > > > > metron > >> > > > > > config parameters (MohanDV via merrimanr) closes > >> > apache/metron#1227 > >> > > > > > METRON-1808 Add Ansible created pyc to gitignore > >> (justinleet) > >> > > > closes > >> > > > > > apache/metron#1228 > >> > > > > > METRON-1695 Expose pcap properties through Ambari > >> (anandsubbu) > >> > > > closes > >> > > > > > apache/metron#1207 > >> > > > > > METRON-1771 Update REST endpoints to support eventually > >> > > consistent > >> > > > UI > >> > > > > > updates (merrimanr) closes apache/metron#1190 > >> > > > > > METRON-1791 Add GUID to Messages Produced by Profiler > >> > > (nickwallen) > >> > > > > > closes apache/metron#1210 > >> > > > > > METRON-1804 Update version to 0.6.1 (justinleet) closes > >> > > > > > apache/metron#1220 > >> > > > > > METRON-1798 Add mpack support for parser aggregation > >> > (anandsubbu) > >> > > > > > closes apache/metron#1215 > >> > > > > > METRON-1750 Create Parser for Syslog RFC 5424 Messages > >> > > > > (ottobackwards) > >> > > > > > closes apache/metron#1175 > >> > > > > > METRON-1794 Include User Details When Escalating Alerts > >> > > > (nickwallen) > >> > > > > > closes apache/metron#1212 > >> > > > > > METRON-1782 Add Kafka Partition and Offset to Profiler > Debug > >> > Logs > >> > > > > > (nickwallen) closes apache/metron#1202 > >> > > > > > METRON-1758 Add support for Ansible 2.6 in dev (JonZeolla > >> via > >> > > > > > jonzeolla) closes apache/metron#1179 > >> > > > > > METRON-1784: Re-allow remote ssh and scp in Centos full > dev > >> > > > (mmiklavc > >> > > > > > via mmiklavc) closes apache/metron#1204 > >> > > > > > METRON-1787 Input Time Constraints for Batch Profiler > >> > > (nickwallen) > >> > > > > > closes apache/metron#1209 > >> > > > > > METRON-1508 In Ubuntu14 Dev Indexing Fails to Write to > >> > > > Elasticsearch > >> > > > > > (nickwallen) closes apache/metron#1185 > >> > > > > > METRON-1786 Pcap Topology Status Incorrect (MohanDV via > >> > > nickwallen) > >> > > > > > closes apache/metron#1206 > >> > > > > > METRON-1709 Add controls to start / stop the PCAP topology > >> from > >> > > > > Ambari. > >> > > > > > (MohanDV via nickwallen) closes apache/metron#1201 > >> > > > > > METRON-1759 PCAP UI: Removing wrong Input annotations from > >> pcap > >> > > > panel > >> > > > > > component (tiborm via nickwallen) closes apache/metron#1180 > >> > > > > > METRON-1772 Support alternative input formats in the Batch > >> > > Profiler > >> > > > > > (nickwallen) closes apache/metron#1191 > >> > > > > > METRON-1770 Add Docs for Running the Profiler with Spark > on > >> > YARN > >> > > > > > (nickwallen) closes apache/metron#1189 > >> > > > > > METRON-1774 Allow user to configure JAAS client in Ambari > >> > > > > (nickwallen) > >> > > > > > closes apache/metron#1192 > >> > > > > > METRON-1760 Kill PCAP job should prompt for confirmation > >> > (ruffle > >> > > > via > >> > > > > > nickwallen) closes apache/metron#1199 > >> > > > > > METRON-1777: Fix Elasticsearch X-Pack sample pom in > >> > documentation > >> > > > > > (mmiklavc via mmiklavc) closes apache/metron#1196 > >> > > > > > METRON-1781 Fix RPM Spec File (nickwallen) closes > >> > > > apache/metron#1200 > >> > > > > > METRON-1780 Fix broken website images (justinleet) closes > >> > > > > > apache/metron#1198 > >> > > > > > METRON-1476 Update to Angular 6.1.3 (sardell via > nickwallen) > >> > > closes > >> > > > > > apache/metron#1096 > >> > > > > > METRON-1776 Update public web site to point at 0.6.0 new > >> > release > >> > > > > > (justinleet) closes apache/metron#1195 > >> > > > > > METRON-1775 Transient exception could prevent expired > >> profiles > >> > > from > >> > > > > > being flushed (nickwallen) closes apache/metron#1194 > >> > > > > > METRON-1717 Relocate Storm Profiler Code (nickwallen) > closes > >> > > > > > apache/metron#1187 > >> > > > > > METRON-1748 Improve Storm Profiler Integration Test > >> > (nickwallen) > >> > > > > closes > >> > > > > > apache/metron#1174 > >> > > > > > METRON-1741 Move REPL Port of Profiler to Separate Project > >> > > > > (nickwallen) > >> > > > > > closes apache/metron#1170 > >> > > > > > METRON-1715 Create DEB Packaging for Batch Profiler > >> > (nickwallen) > >> > > > > closes > >> > > > > > apache/metron#1167 > >> > > > > > METRON-1736 Enhance Batch Profiler Integration Test > >> > (nickwallen) > >> > > > > closes > >> > > > > > apache/metron#1162 > >> > > > > > METRON-1714 Create RPM Packaging for the Batch Profiler > >> > > > (nickwallen) > >> > > > > > closes apache/metron#1163 > >> > > > > > METRON-1708 Run the Batch Profiler in Spark (nickwallen) > >> closes > >> > > > > > apache/metron#1161 > >> > > > > > METRON-1707 Port Profiler to Spark (nickwallen) closes > >> > > > > > apache/metron#1150 > >> > > > > > METRON-1705 Create ProfilePeriod Using Period ID > >> (nickwallen) > >> > > > closes > >> > > > > > apache/metron#1148 > >> > > > > > METRON-1706 HbaseClient.mutate should return the number of > >> > > > mutations > >> > > > > > (nickwallen) closes apache/metron#1147 > >> > > > > > METRON-1704 Message Timestamp Logic Should be Shared > >> > (nickwallen) > >> > > > > > closes apache/metron#1146 > >> > > > > > METRON-1703 Make Core Profiler Components Serializable > >> > > (nickwallen) > >> > > > > > closes apache/metron#1145 > >> > > > > > > >> > > > > > *Metron-bro-kafka-plugin changelog* > >> > > > > > METRON-1800 Increment metron-bro-plugin-kafka version > >> > (JonZeolla > >> > > > via > >> > > > > > jonzeolla) closes apache/metron-bro-plugin-kafka#10 > >> > > > > > METRON-1773 Bro plugin docs should refer to Apache Metron > >> > project > >> > > > > > (nickwallen) closes apache/metron-bro-plugin-kafka#9 > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > > -- > > > > Jon Zeolla > > > -- > > Jon Zeolla >
