Hi Ralph, Yep, I'll get the keys taken care of as well as get the docs updated and the artifacts published to central.
Regards, Mike On Wednesday, June 27, 2012 at 4:27 PM, Ralph Goers wrote: > Mike, > > I previously mentioned that you need a signed key to do the release. Did you > take care of that? > > Also, I mentioned that the release instructions should be updated to make > sure the artifacts are released to the Nexus repository - Do you know how to > do that? > > Ralph > > > On Jun 27, 2012, at 3:50 PM, Mike Percy wrote: > > > Hi all, > > This is a friendly reminder that I plan on cutting branch-1.2.0 this Friday > > (in 2 days)! > > > > After the branch is cut, the plan is to only accept critical application > > bug fixes, build fixes, and documentation updates until release. This is to > > ensure as stable a 1.2.0 release as possible. So if you want something in > > for 1.2.0, please submit your patches now. > > > > Looking forward to our first official release as an Apache TLP! > > > > Best regards, > > Mike > > > > On Sun, Jun 17, 2012 at 1:21 AM, Mike Percy wrote: > > > > > Thanks everyone for your votes and responses! Here's what I'd like to do > > > for the release schedule: > > > > > > - Friday, June 29: cut release branch > > > - Rel. Mgr. to backport critical bugfix/build/doc changes between branch > > > and release > > > - Monday, July 9: begin release vote > > > > > > Note that this a bit more conservative than the 2-3 week release schedule > > > I originally mentioned (but not by much). As suggested, I've marked the > > > wishlist items through JIRA as Blocker tickets. However, since these JIRAs > > > are in varying stages of completion, I propose that anything that misses > > > the deadline will need to be pushed to the next release (even if it's > > > marked as a Blocker). > > > > > > Here is a JIRA link to the list of v1.2.0 Blocker tickets: > > > http://s.apache.org/1eH > > > > > > Please raise any issues or concerns right away. Here's to putting out a > > > great 1.2.0 release! > > > > > > Best, > > > Mike > > > > > > > > > PS: These were the wishlist items I saw that were raised in the discuss > > > thread: > > > - Cannot start agent a 3rd time when using FileChannel < > > > https://issues.apache.org/jira/browse/FLUME-1232> > > > - Remove the org.apache.hadoop.io (http://org.apache.hadoop.io).* > > > dependencies from FileChannel and ResumableMemoryChannel < > > > https://issues.apache.org/jira/browse/FLUME-1285> > > > - Add more unit tests for HBase sink < > > > https://issues.apache.org/jira/browse/FLUME-1204> > > > - Create metric collection infrastructure < > > > https://issues.apache.org/jira/browse/FLUME-748> > > > - Support external tooling in configuration system < > > > https://issues.apache.org/jira/browse/FLUME-1051> > > > - Flume hot-reconfiguration specification < > > > https://issues.apache.org/jira/browse/FLUME-1278> > > > - OutOfMemory errors in Flume build < > > > https://issues.apache.org/jira/browse/FLUME-1256> > > > - FileChannel hangs silently when Hadoop libs not found < > > > https://issues.apache.org/jira/browse/FLUME-1246> > > > > > > > > > > > > > > > On Wednesday, June 13, 2012 at 12:57 AM, Mike Percy wrote: > > > > > > > Developers, > > > > It has been nearly 3 months since we released Flume 1.1.0. Since the > > > > > > > > > 1.1.0 release, we have had 117 commits to the trunk, and 114 JIRAs have > > > been marked "Resolved Fixed" with a target of v1.2.0. This flurry of > > > activity represents a whole slew of new features and a bunch of bug fixes. > > > > > > > > Because of the above, I think we should release a Flume 1.2.0 to the > > > world within 2-3 weeks. I propose that I be the release manager for this > > > release. To that end, I would like to cut an SVN branch pretty soon to > > > stabilize and test the code in advance of the release. > > > > > > > > In addition, I'd like to gather input on what other devs would like to > > > see included in a 1.2.0 release. > > > > > > > > Aside from a few JIRAs already marked as Patch Available, the one thing > > > I'd really like to make happen is a once-over on the user guide to cover > > > the latest features. I'm willing to help. > > > > > > > > Regards, > > > > Mike > > > > > >
