Re: [jetty-dev] Project meta data is out of date for rt.jetty

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

We are going to have to start distinguishing between eclipse releases
and or normal jetty community releases as they will not necessarily be
1 to 1 going forward...  We have technically not had an eclipse
release yet as we have not had the release review yet. :)

We have the Graduation review (which is also our first release review)
on June 24th coming up and from that point forward we are going to
have to be a little more select in what is getting termed an eclipse
release and what is a normal jetty community release.  Our community
releases can be released on our terms, but the eclipse releases have
to go through a release review and then we are also going to have to
have those jars signed and sealed by the standard eclipse processes
(which I started to work out a few weeks back but haven't completed).

I think as a project we should strive for a one to one eclipse release
to community release relationship but I don't think we should hold it
as a requirement for us.  The community releases are super easy to
perform, whereas there is a heavier process involved with an official
eclipse release.  Release review scheduling, docuware, update sites,
renamed bundles, signed and sealed jars, things that are not easily
managed with a maven plugin. :)

This is something we are going to have to decide though.. Do we:

A) perform our normal community release as we traditionally have done
and then tack on the eclipse release process on the end of it if we
are happy with outside eclipse community feedback (effectively
isolating the eclipse community from some issues that might prompt us
to make a subsequent community release)

B) schedule our eclipse release reviews appropriately (2 weeks lead
time, docuware updated, yadda yadda yadda) and prepare the entire
release goop at once, mvn artifacts, update sites, bundles (signed and
sealed mvn artifacts repackaged into p2 update site -
http://wiki.eclipse.org/Jetty/Project/UpdateSite) and all of that jazz
at the same time?

I know it sounds bad to term it eclipse release and community release
as eclipse is part of our community, but the incredibly varied types
of artifacts we are having to produce here is overwhelming and complex
so some distinction is required in my mind.

* mvn artifacts - which are by and far the easiest to produce
* jetty distribution bundle (.tgz, zip, etc) - easy to produce with assseblies
* p2 update site - not difficult but very manual, take mvn artifacts,
condition them (sign and seal with eclipse process), copy them around
into eclipse instance, load eclipse, update the site project,
regenerate update site, zip it, copy to download site, unpack
* hightide - distribution bundling the jetty artifacts we can't have
located anywhere near eclipse for IP reasons
* deb, rpm - not sure current status of these atm, dyu was working on them

It is a bit of a mess..

jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Fri, Jun 5, 2009 at 02:41, Athena <athena@xxxxxxxxxxx> wrote:
> There's no "SNAPSHOT available" (only tentative, planned, released), but
> I've created a new release item, tagged it "planned", and used the link
> to the blog entry as the url for "plan"
>
> Hm, should I move some of the text to the wiki, and link to that that
> instead?
> On Fri, 2009-06-05 at 00:09 -0700, Greg Wilkins wrote:
>> Athena,
>>
>> Athena wrote:
>> > I've added a link to http://www.eclipse.org/jetty/ as the project url.
>>
>> thanks
>>
>> > I haven't added the next planned release as that requires some
>> > additional information. Namely:
>> >
>> > required:
>> > * name (7.0.0.M3?)
>>
>> yes
>>
>> > * date (?)
>>
>> Let's aim for a M3 around June 12, and I'd hope the next release
>> after that would be a RC
>>
>> > * status (planned)
>>
>> SNAPSHOT available.
>>
>>
>>
>> > not required:
>> > * download link (download URL once released)
>> > * plan (url to documentation referring to the release; we haven't had
>> > this before)
>>
>> Hmmm perhaps take the text from my recent blog about it.
>>
>> cheers
>>
>>
>> > On Fri, 2009-06-05 at 00:00 -0400, portal on behalf of emo wrote:
>> >> Greg, Jan,
>> >> Projects are required to keep meta data up to date using the MyFoundation
>> >> Portal (http://portal.eclipse.org/).  The following problems were found
>> >> with this project's meta-data:
>> >>
>> >> * There is no next/future release of this project. All Eclipse projects
>> >> must have a "next release" planned and scheduled.
>> >> * There is no 'projecturl' pointing to the project home page
>> >>
>> >> _______________________________________________
>> >> jetty-dev mailing list
>> >> jetty-dev@xxxxxxxxxxx
>> >> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>> >
>> > _______________________________________________
>> > jetty-dev mailing list
>> > jetty-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>
>> _______________________________________________
>> jetty-dev mailing list
>> jetty-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>