That would be fantastic!
On 19 October 2013 23:53, Jacob Clark <[email protected]> wrote: > Hi Noah, > > Thanks for sending these documents over. I will have a read of the Release > Procedure article you sent over. > > I'm familiar with Git, so possibly next month I could work with yourself > and Dirkjan to learn the ropes and begin writing up a proposal for a > 'preferred' Git workflow? > > Jacob. > > On 19 Oct 2013, at 22:43, Noah Slater <[email protected]> wrote: > > > Here are some wiki pages: > > > > http://wiki.apache.org/couchdb/Merge_Procedure > > > > This page is outdate. Search the mailing lists for "Git workflow" to see > > where this conversation went. Basically, we want to document our > preferred > > Git workflow, and how that interfaces with our release process. > > > > This is an active item. We're still looking for someone familiar enough > > with Git, and with the time and patience to document a proposal and then > > get the community to rubber stamp it. > > > > Mailing list search: > > > > > http://markmail.org/search/?q=list%3Aorg.apache.couchdb.dev+order%3Adate-backward > > > > http://wiki.apache.org/couchdb/Release_Procedure > > > > This is our current release procedure. This is an actively maintained > doc. > > There are actually bits here that are out of ate. But it should give you > a > > good idea about what is involved in being a release manager. > > > > I started this too, but it's not got very far: > > > > http://wiki.apache.org/couchdb/Release_Preparation > > > > When we send out the release vote email to get the community to test, we > > link them to: > > > > http://wiki.apache.org/couchdb/Test_procedure > > > > This is an current doc. > > > > > > > > On 19 October 2013 23:39, Noah Slater <[email protected]> wrote: > > > >> Welcome, Jacob! > >> > >> Me and Dirkjan are the most recent release managers. Perhaps Dirkjan can > >> weigh in with some of his outstanding items. I know he was planning to > do > >> some more automation work. > >> > >> Our current goal is to start each release process one month after the > >> previous release announcement. (Note: the release process itself can > take > >> anywhere from a week to several months, depending on how many bugs we > hit.) > >> > >> We're just wrapping up the 1.5 release, so the next one should be in a > >> month or so. That would be a great time to work side-by-side with > Dirkjan > >> and me and learn the ropes. We'd like to share the duty of performing > >> releases with as many people as possible. > >> > >> Jan is the guy to speak to about QA. He has a Jenkins setup, but I think > >> it needs some work doing before we can use it properly. So perhaps that > is > >> something you could help out with! Till might know more. > >> > >> CCed all the people mentioned. > >> > >> > >> On 19 October 2013 23:33, Jacob Clark <[email protected]> wrote: > >> > >>> Awesome! > >>> > >>> I'd also be interested in helping out with Release Efforts and Q/A, are > >>> there any further resources I could get to regarding that? > >>> > >>> The site suggests the ML is the best place to find out, though! > >>> > >>> Jacob. > >>> > >>> On 19 Oct 2013, at 22:31, Robert Newson <[email protected]> wrote: > >>> > >>>> Hi! > >>>> > >>>> We maintain a difficulty filter on our jira tickets. Have a look at > >>> things > >>>> marked Easy to get started. And welcome! > >>>> On 19 Oct 2013 22:28, "Jacob Clark" <[email protected]> wrote: > >>>> > >>>>> Hello all, > >>>>> > >>>>> I'd like to get stuck in contributing to the CouchDB Core/Patching > >>> bugs. > >>>>> Can any seasoned contributors link me up with a random, non-assigned, > >>> easy > >>>>> to attack bug that I could get started with? > >>>>> > >>>>> Thanks, > >>>>> Jacob Clark. > >>> > >>> > >> > >> > >> -- > >> Noah Slater > >> https://twitter.com/nslater > >> > >> > > > > > > -- > > Noah Slater > > https://twitter.com/nslater > > -- Noah Slater https://twitter.com/nslater
