Re: [jetty-dev] IP Status of jetty @ eclipse

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

CD3385

once this gets through I'll get the updated frozen IP log and then it
is up to you and greg to hash out details on getting into the initial
release

jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Mon, Jun 8, 2009 at 20:10, David Jencks<david_jencks@xxxxxxxxx> wrote:
> I just started a vote on the geronimo-jaspic_1.0_spec over at geronimo.
>  With all the new tooling and checking maybe I won't have made any mistakes
> :-)
>
> Note that the aritifactId changed slightly -- I'll update jetty when the
> vote passes.
>
> Tag is at
>
> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jaspic_1.0_spec-1.0
>
> staging site
>
> https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/specs/geronimo-jaspic_1.0_spec/1.0/
>
> and just in case you are nuts enough to want to look at the maven generated
> site it's staged
>
> http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jaspic_1.0_spec/1.0/
>
> Hopefully this is enough to get the IP review going.
>
> many thanks
> david jencks
>
>
> On May 29, 2009, at 2:47 PM, Jesse McConnell wrote:
>
>> Folks,
>>
>> I just got word from Barb that we are cleared, everything in place
>> that needed to be reviewed has been reviewed now for jetty to leave
>> incubation.
>>
>> That is to say everything that is _required_ to be reviewed has been,
>> but David Jencks pinged me the other day about the jaspi bits and if
>> we can get them into the initial drop of jetty as geronimo needs us to
>> release with it (which is amusing since we need geronimo to release
>> their jaspi as well).
>>
>> Anyway, djencks is going to try and get us a cut of that api in a
>> released repo and the follow steps need to happen for us to finally
>> graduate and release 7.0.0.WHATEVER
>>
>> 1) get frozen IP log from Barb (request submitted, awaiting now)
>> 2) edit Release Review Docuware in jetty admin svn to reflect frozen
>> IP log location
>> 3) submit release review to emo@xxxxxxxxxxx
>> 4) release review is scheduled ~2 weeks away
>>
>> for the JASPI to make it in time:
>>
>> 1) get released tag of jaspi-api
>> 2) open a CQ in ipzilla for the jaspi-api dependency (attaching zip or
>> linking to zip of source in mvn repo)
>> 3) open a CQ in ipzilla for the jetty-jaspi module (attaching zip as
>> well, current svn is fine)
>> 4) wait for these to past muster
>> 5) update ip log and generate a new frozen IP log
>>
>> Lastly, starting now we can get the graduation review docuware in
>> place and get that scheduled:
>> 1) create graduation review docuware
>> 2) notify mentors (which has been done)
>> 3) submit graduation review to emo@xxxxxxxxxxx
>> 4) review is scheduled in 2-4 weeks (they try for twice a month)
>>
>>
>> I am taking care of the first set of numbers right now, I got word
>> while typing this that the frozen log was created so I'll update the
>> release review and get that in place and submitted to emo today.  For
>> the JASPI stuff to make it into the graduation review we need to jump
>> on that pronto because ideally I'll knock out that graduation docuware
>> this weekend/first thing monday and get it submitted and we _need_ to
>> have the jaspi stuff approved in CQ and a new frozen IP log generated
>> (not difficult anymore now that we have the first one done) before the
>> graduation review...
>>
>> I am hoping that we can get the graduation review scheduled for the
>> release review time so we have everything covered all at once in that
>> one meeting.  Then we have a lot of our overhead done and we can fit
>> into a smoother release cycle in terms of eclipse releases.
>>
>> cheers,
>> jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@xxxxxxxxx
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>