Hey Kevin, Now that the [DISCUSS] RM thread is out of the way I'll try and answer your questions to the best of my ability below:
On 3/20/13 4:00 PM, "Kevin Minder" <[email protected]> wrote: >So in trying to get ready to do a release I do really need help figuring >out a few things. Clearly trying to figure it all out myself is >inappropriate. > >1. LICENSE and NOTICE - I think I know what to do but how do I know if >I'm right? Will someone be auditing this? JFDI -- I'll try and help where I can. Others can too. Basic principle: 1. Work on it now in dev@knox 2. On the first RC, once we are ready to take it to [email protected] expect a guy named sebb to come out of the wood work and comment/have a bunch of suggestions. 3. Expect to spin more new RCs after this :) 4. Expect time N+1 for next release version to go a lot easier >2. Artifact signatures - No idea how this is typically done for a Java >project. Any pointers? Check out Apache Tika. It generates these automatically: https://svn.apache.org/repos/asf/tika/trunk/pom.xml https://svn.apache.org/repos/asf/tika/trunk/tika-parent/pom.xml See how it inherits from the Apache parent? That parent pom along with the Tika root pom.xml generates MD5 and SHA1 on mvn release:prepare and mvn release:perform steps. See: http://wiki.apache.org/tika/ReleaseProcess Also you should generate your ASF key if you don't have one yet: http://www.apache.org/dev/release-signing.html >3. What else needs to be in place to initiate a release vote? > >So basically I'm personally interested in starting the process of >releasing 0.2.0. How knows how many RCs it will take. Do we need to >vote on starting that? Nope no need to VOTE on starting that. I've started a DISCUSS thread for you to be the RM. If there aren't any objections in the next 48 hours (which use the time to prep based on the above comments) which I doubt there will be, be ready in the next few days to start the process. Loose idea of how it works: 0. Wait 48 hours, and I'll declare DISCUSS thread done (or you just move fwd then yourself without hinging on me) 1. Go through release process: (something like Tika, but follow this since we are still in Incubator) http://incubator.apache.org/guides/releasemanagement.html 1a. Ask questions on this list (dev@) anywhere you get stuck 2. Eventually produce a [VOTE] Apache Knox Gateway version <X - we should discuss this, perhaps separate thread?> release RC #[N, N starts at 1] - artifacts to VOTE on - SHA and MD5 checksums - ASC files - possibly Maven staging repo on https://repository.apache.org/ 3. Try and muster 3 +1s from your mentors who are on the IPMC (if you get that, all we need to do is NOTIFY [email protected] and it's a lot easier, so mentors step up and VOTE) 4. Eventually go to [email protected] - watch for folks to come out of the wood work. Assume they are trying to help. Don't get pissed when you have to spin more RCs. 5. Pass [email protected]. Pop open a beer. Make release. [did I say that]? Cheers, Chris > >On 3/20/13 6:53 PM, Kevin Minder wrote: >> Hi Everyone, >> Lets see, this is all just a symptom of me learning the ropes here and >> transitioning into the open development mode. So let me address each >> point I believed was raised so that I get concrete feedback about how >> to improve and proceed. >> >> 1. Snapshot upload >> >> I certainly understand the "second class" citizen concern here and I >> was concerned about it myself. At the time I thought my only option >> was a private email about the upload. I thought that was worse that >> discussing it publically. Ideally I would expect these type of >> frequent snapshot distributions to be built via CI. We don't have >> that setup yet. I will file a Jira for that but given the information >> I received in the general@incubator thread this seemed like it could >> take awhile. In the meantime I like Alan's suggestion of uploading to >> apache.org/~kminder. I'll do that and send another email. >> >> 2. Release vote >> >> We want to avoid co-development at all costs too but at the same time >> we still need to make progresss, name and cut "unofficial releases" to >> evaluate both at Hortonworks and also to court potential community >> members. What should we be calling these to stay within the rules? I >> specifically left the SNAPSHOT in everything as an attempt. I expect >> that there is still significant work that needs to be done to create >> something that will pass legal for an official Apache release. I have >> more work to do to understand exactly what needs to be in the LICENSE >> and NOTICE files at a minimum. When that was done I was planning on >> asking about calling for a vote. >> >> 3. v0.1.0 and v0.2.0-rc1 >> >> We had all of our history from the GitHub repository imported into the >> Apache Git repo where we have continued working. Therefore there are >> existing tags for the v0.1.0 and v0.2.0-rc1 so I thought it made the >> most sense to continue on. I do acknowledge in hindsight that this is >> something that should have been discussed. >> >> 3. Co-development >> >> There is no active private repository for this. Everything is being >> committed to the Apache git repo at this point. Larry and I in >> particular need to find the right balance between high bandwidth brain >> storming (e.g. face:face, IM, phone) and email discussions on dev@knox. >> >> 4. Jira >> >> Devarj filed INFRA-5922 on March 1st to have Jira setup. I would much >> rather be using the Apache Jira so anything that can be done to speed >> that up would be appreciated. I'll take the reference to the >> Hortonworks Jira out of the docs and I guess we will just have to keep >> track of any issues discovered in email. I'll come up with some email >> subject convention (e.g. [BUG]) >> >> Continued feedback appreciated. >> Kevin. >> >> On 3/20/13 5:49 PM, Mattmann, Chris A (388J) wrote: >>> Hey Guys, >>> >>> RE: #3, after looking at it in more detail, we need to remove >>>references >>> to internal Hortonworks JIRA's in our Apache documentation. I realize >>> Hortonworks >>> people have their own company systems, etc. Those should not be >>>confused >>> with their Apache (!Hortonworks) counterparts. >>> >>> Do we have an Apache Knox JIRA? If not, I would be glad to request one. >>> >>> Cheers, >>> Chris >>> >>> >>> On 3/20/13 2:46 PM, "Mattmann, Chris A (388J)" >>> <[email protected]> wrote: >>> >>>> Hi Kevin, >>>> >>>> I'm not sure what this email means, but I'm worried by its context. >>>> >>>> Are you suggesting that you have released a version of Apache Knox, >>>> with >>>> a version # 0.2.0? >>>> >>>> If so, then I have the following statements/questions: >>>> >>>> 1. Apache releases are VOTEd on by the Apache Knox PPMC and by the >>>> Apache >>>> Incubator PMC >>>> (whose VOTEs are the binding ones in this process atm). Unless I >>>>missed >>>> it, >>>> I didn't see a VOTE thread, so I'm not sure how you released Apache >>>> Knox. >>>> See: http://incubator.apache.org/guides/releasemanagement.html >>>> Small note: where is RC1? >>>> >>>> 2. It looks like there is development occurring internally at >>>> Hortonworks >>>> here. >>>> Why? Co-developing wastes community resources. All of you guys here >>>> that >>>> are interested >>>> in the project should be developing here. Of course there are naming >>>> issues, etc., >>>> associated with this, but more importantly there are community >>>> issues. So >>>> I request >>>> clarification on this. >>>> >>>> 3. Great job on the documentation! >>>> >>>> Looking forward to the clarifications. >>>> >>>> Cheers, >>>> Chris >>>> >>>> >>>> On 3/20/13 2:35 PM, "Kevin Minder" <[email protected]> >>>> wrote: >>>> >>>>> Hi Everyone, >>>>> I decided to cut and share v0.2.0 RC2 of the gateway. I tagged the >>>>> repo >>>>> with v0.2.0-rc2. >>>>> >>>>> For those in Hortonworks I uploaded a ZIP here >>>>> >>>>>https://docs.google.com/a/hortonworks.com/file/d/0BzcmnaxIHtiAZkxhQWZC >>>>>Q21 >>>>> >>>>> y >>>>> WTA/edit >>>>> >>>>> Everyone else should be able to create their own following these >>>>> instructions. >>>>> http://knox.incubator.apache.org/release-process.html >>>>> >>>>> The Apache site is starting to come along. >>>>> http://knox.incubator.apache.org/ >>>>> >>>>> Of particular interest are the links in the Documentation section >>>>> of the >>>>> left Nav bar. >>>>> http://knox.incubator.apache.org/getting-started.html >>>>> http://knox.incubator.apache.org/examples.html >>>>> http://knox.incubator.apache.org/client.html >>>>> http://knox.incubator.apache.org/sandbox.html >>>>> >>>>> I wrote and reorganized a bunch of documentation over the last few >>>>> days >>>>> and I haven't "tested" all of it yet. So there may need to be some >>>>> tweaks there and an RC3. Functionally however the more eyes the >>>>> better >>>>> so give it a spin. We are especially interested in feedback. >>>>> >>>>> Kevin. >> >
