Despite my tweets about skiing, etc, I'm still busy working on the release.
Right now, I'm reading up on the Apache release process (http://www.apache.org/dev/release.html) + how to sign releases ( http://www.apache.org/dev/release-signing.html) + PGP ( http://www.apache.org/dev/openpgp.html#gnupg) . I'm a total beginner here, so I 'm trying to understand all this stuff. Once we know how to do it, later releases will be much easier. This first one might take a little longer though. D. On Tue, Feb 9, 2010 at 12:34 AM, Ethan Jewett <[email protected]> wrote: > Really? I have to watch him tweet about skiing and sunburns for > another week? Life just isn't fair. ;-) > > Ethan > > On Mon, Feb 8, 2010 at 5:21 PM, Anne Kathrine Petterøe > <[email protected]> wrote: >> I don't think we should start the release process before Dick is back >> anyway, so that should give us a week to fix the last small issues ;-) >> >> /Anne >> >> >> On 8. feb. 2010, at 23.09, Ethan Jewett wrote: >> >>> Excellent! One last thing, in that case, is that we need to disable >>> the automatic OpenID signup, and just make people configure their >>> OpenID after the fact. Things are a little crazy at work at the >>> moment. If no one else gets to it, I'll see what I can do. (And the >>> fix for this really is, I think, to revert the original patch to >>> ESME-111.) >>> >>> Ethan >>> >>> On Mon, Feb 8, 2010 at 3:17 PM, Vassil Dichev <[email protected]> wrote: >>>> There, ESME-111 is no more... at least you can configure the OpenID >>>> URL from the "Edit Profile" page. >>>> >>>> >>>> On Mon, Feb 8, 2010 at 5:49 PM, Richard Hirsch <[email protected]> >>>> wrote: >>>>> There is actually a JIRA for this: >>>>> http://issues.apache.org/jira/browse/ESME-105 >>>>> >>>>> The idea was to reuse the existing code in ProtoUser >>>>> >>>>> D. >>>>> >>>>> On Mon, Feb 8, 2010 at 4:01 PM, Vassil Dichev <[email protected]> wrote: >>>>>>> We now just have one JIRA item left for the release: * ESME-111: >>>>>>> OpenID login/signon is broken >>>>>>> >>>>>>> Getting close.... >>>>>> >>>>>> I noticed that we also don't have a form to change the current >>>>>> password, and I think this is also critical to have in the first >>>>>> release. Should we create a JIRA item? >>>>>> >>>>> >>>> >> >> >
