With regard to the alpha, beta, etc designations, I'd propose to do away
with them, at least for 1.1.x. If we could just cut a release candidate
(that is what it is, even if we don't _say_ thats what it is) and vote
on it.
my .02
elliot
Sent from webmail (apologies for the poor quoting)
>>> Craig Doremus <[EMAIL PROTECTED]> 02/28/07 7:27 AM >>>
David:
I tried to publish the site, but I had problems logging in when I ran
the site:deploy goal, so thanks for moving this along. Please add
anything to the news item that I created that you think is appropriate
and send it out.
I noticed that you want to push out version 1.1.1 soon. Are we doing
away with alpha, beta and rc release designations? If, so, how does
someone judge the quality of a release? I notice that Struts 2.0 has
gone this way. I find this way to do versioning very confusing.
/Craig
> Craig,
>
> Thanks for making the doc updates. I've published the site tonight.
> Feel free to make more mods and then update again. . .I just wanted to
> get something out. If no one beats me to it, I'll send out an
> announcement in the morning.
>
> David
>
> Elliot Metsger wrote:
>> Hi Craig,
>>
>> Thanks for the updates!
>>
>> A couple of notes:
>>
>> 1. The release plugin deploys the website (this may or may not be
>> desired behavior when we are cutting a release candidate).
>>
>> 2. I'm working on a Velocity template which will interpolate strings
>> in our website content (under pluto-site/src/site/xdoc), allowing us
>> to automate version numbers. For example, from
>> pluto-site/src/site/xdoc/index.xml there's the highlightBox for
>> downloading Pluto, and it references beta2:
>>
>> Download Pluto 1.1.0-beta2 (19Mb)
>>
>> I'd like the version string to be interpolated, so the source becomes
>>
>> Download Pluto ${version}
>>
>> This goes back to automating version numbers when we release.
>>
>>
>>
>> If you can update the website and send out the announcements, that
>> would be appreciated.
>>
>> After I get the Velocity template in a good place, I'll probably
>> re-deploy the website but that won't happen until later this week.
>>
>> Elliot
>>
>> Craig Doremus wrote:
>>> Elliot:
>>>
>>> Thank you all you've done on this release. I added a few things to
>>> the wiki page that still needs to be done, which includes updating
>>> the web site and sending out announcements of the release. I can
>>> help you with this if you want.
>>> /Craig
>>>
>>>> Ok,
>>>>
>>>> The Pluto 1.1.0 distributions should be up.
>>>>
>>>> I've copied the distribution files from
>>>> /www/people.apache.org/builds/portals-pluto and placed them in
>>>> /www/www.apache.org/dist/portals/pluto under BINARIES/v1.1.0 and
>>>> SOURCES/v1.1.0.
>>>>
>>>> I've digitally signed them, and md5'ed them.
>>>>
>>>> I've created the "current" symlinks in
>>>> /www/www.apache.org/dist/portals/pluto to point to the actual files
>>>> under BINARIES/v1.1.0 and SOURCES/v1.1.0.
>>>>
>>>> I documented what I did at
>>>> http://wiki.apache.org/portals/Pluto/CuttingRelease.
>>>>
>>>> So, all that is left to do, I believe, is update and generate the
>>>> website for 1.1.0.
>>>>
>>>> Let me know if I've missed something!
>>>>
>>>> Thanks,
>>>>
>>>> Elliot
>>>>
>>>>
>>>>
>>
>
>
>
