Dane, #115 is a longstanding and (IMHO), an important issue to tackle. But also a difficult one.
However, it has huge implications for Storm, and will probably not be addressed in the initial Apache release. The first release out of Apache will basically be a slight variant of 0.9.0.1, but with legal/licensing issues resolved and backed by the Apache Software Foundation. - Taylor On Dec 9, 2013, at 10:54 PM, Dane Hammer <[email protected]> wrote: > One of the most active issues is #115, and it would solve the thrift > versioning problem. I don't know if the aim of the first incubator release > is to make no code changes, however. > > On Monday, December 9, 2013, P. Taylor Goetz wrote: > >> Excellent. Thanks James! >> >> As you migrate issues, it’s probably best to just close the github issue >> with a comment like “Migrated to Apache JIRA”. If you want to get fancy, >> including a link to the JIRA would be cool (but not necessary). >> >> This could also likely be automated. The github API exposes everything >> needed, I’m just not sure if the JIRA api does as well (and if the Apache >> JIRA is open for API access from committers). >> >> Let me know if there’s anything I can help with. >> >> - Taylor >> >> >> On Dec 9, 2013, at 9:07 PM, James Xu <[email protected] <javascript:;>> >> wrote: >> >>> Thanks Taylor for doing all of these! I can help on doing the 8th: >> Migrate github issues to JIRA. >>> >>> On 2013年12月10日, at 上午8:29, P. Taylor Goetz <[email protected]<javascript:;>> >> wrote: >>> >>>> Now that we’ve released 0.9.0, it’s time to start moving into our new >> home, and getting ready for our first Apache release. >>>> >>>> Off the top of my head, and in no particular order, here are some of >> the tasks we need to accomplish: >>>> >>>> 1. Shutter the storm-user google group and direct people to the user@and >>>> dev@mailing lists. (I think Nathan is the only one who has permissions to >>>> do >> this). >>>> >>>> 2. Close the nathanmarz/storm repo on github and direct people to git:// >> git.apache.org/incubator-storm.git (I’ve been keeping the github and >> apache repos in sync). >>>> >>>> 3. Get an answer on whether we can continue to use 0mq as a dependency >> given it’s LGPL license. And if so, what are the implications for >> source-only and binary releases. >>>> >>>> 4. Move all dependencies off of storm-specific builds >> (groupId=storm/backtype) and on to specific releases. (Nathan can probably >> best answer to which ones involve changes, and which ones are just >> point-in-time forks). >>>> >>>> 5. Figure out what to do with Thrift. Right now we’re using a forked >> version with packages renamed to avoid conflicts, which I could potentially >> cause problems with releasing under Apache. One potential fix would be to >> use a stock Thrift version and repackage it using jarjar. >>>> >>>> 6. Add apache headers to all source files. This is done [1]. I also >> need to figure out if we need the license header in generated (Thrift) >> files that are checked in to SCM. >>>> >>>> 7. Sort out the LICENSE and NOTICE files. I’ve started on this as well >> [1] (though I’ve ignored 0MQ for the moment). For a source-only release, I >> think we only need entries for jQuery and jQuery-cookie in the LICENSE >> file, which I’ve added. I’m also not sure if we have to put anything in >> LICENSE/NOTICE >>>> >>>> 8. Migrate github issues to JIRA >>>> >>>> 9. Setup storm webpage at Apache. We need to figure out what we want to >> do here: Migrate the existing storm-project.net site? Move existing wiki >> into Apache web site or cwiki, etc.? >>>> >>>> That’s all I can think of for now. When I get a chance I’ll throw them >> in JIRA. >>>> >>>> In the meantime, if anyone has any input on the above list, please >> share it. >>>> >>>> Thanks, >>>> >>>> Taylor >>>> >>>> >>>> >>>> >>>> >>>> [1] https://github.com/ptgoetz/storm/tree/apache-headers >>> >> >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
