You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2001/05/11 15:01:52 UTC
[Formal Release] Today's the day!
OFFICIAL VOTE: Are we ready? +1 from me!
What steps need to be taken for the formal release?
* We need to build the official packages
- LogKit 1.0b1
- Framework 4.0b1
- Excalibur 4.0b1
* We need to update the site with the new site docs
and the releases. (Is there any way we can get a
link at http://jakarta.apache.org/site/binindex.html?)
* We need to make announcements to xml-announce and
jakarta-announce about Avalon 4.0b1. Please note,
that I would like to wait until the other two steps
have been completed first.
Am I missing anything?
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Berin Loritsch <bl...@apache.org>.
Charles Benett wrote:
>
> Berin Loritsch wrote:
> >
> > OFFICIAL VOTE: Are we ready? +1 from me!
>
> +1
>
> >
> > What steps need to be taken for the formal release?
> >
> > * We need to build the official packages
> > - LogKit 1.0b1
> > - Framework 4.0b1
> > - Excalibur 4.0b1
> >
> > * We need to update the site with the new site docs
> > and the releases. (Is there any way we can get a
> > link at http://jakarta.apache.org/site/binindex.html?)
>
> Easy basically checkout jakarta-site2 module and amend xdocs. See
> jakarta.apache.org/site/jakarta-site2.html
>
> Four questions, though:
> 1) I guess we are calling this a milestone (rather than release or
> nightly)
Milestone ~ Beta Release (it's the same concept)
> 2) Do we want all three under an Avalon link on binindex
I think so.
> 3) There are avalon nightly builds in the ant directory (follow ant from
> binindex), do we want these in an avalon dir with an avalon link from
> the nightly section? How did they get there?
The nightly builds are automatic (I believe). But yes, we should put a link
to the nightly section as well.
> 4) Are we doing a source dist?
Yes. We are doing both a source dist and a binary dist.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Peter Donald wrote:
>
> At 02:16 11/5/01 +0100, Charles Benett wrote:
> >Four questions, though:
> >1) I guess we are calling this a milestone (rather than release or
> >nightly)
>
> +1
>
> >2) Do we want all three under an Avalon link on binindex
>
> +1
I'll add links from binindex to milestone and nightly buidls dirs.
>
> >3) There are avalon nightly builds in the ant directory (follow ant from
> >binindex), do we want these in an avalon dir with an avalon link from
> >the nightly section? How did they get there?
>
> eek - I prolly gave Sam the wrong directory name or something ... though I
> couldn't see them - can you give me a URL ?
Ah, actually a one off on 3 May The ones since then are in the right
place.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Peter Donald <do...@apache.org>.
At 02:16 11/5/01 +0100, Charles Benett wrote:
>Four questions, though:
>1) I guess we are calling this a milestone (rather than release or
>nightly)
+1
>2) Do we want all three under an Avalon link on binindex
+1
>3) There are avalon nightly builds in the ant directory (follow ant from
>binindex), do we want these in an avalon dir with an avalon link from
>the nightly section? How did they get there?
eek - I prolly gave Sam the wrong directory name or something ... though I
couldn't see them - can you give me a URL ?
>4) Are we doing a source dist?
+1
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Berin Loritsch wrote:
>
> OFFICIAL VOTE: Are we ready? +1 from me!
+1
>
> What steps need to be taken for the formal release?
>
> * We need to build the official packages
> - LogKit 1.0b1
> - Framework 4.0b1
> - Excalibur 4.0b1
>
> * We need to update the site with the new site docs
> and the releases. (Is there any way we can get a
> link at http://jakarta.apache.org/site/binindex.html?)
Easy basically checkout jakarta-site2 module and amend xdocs. See
jakarta.apache.org/site/jakarta-site2.html
Four questions, though:
1) I guess we are calling this a milestone (rather than release or
nightly)
2) Do we want all three under an Avalon link on binindex
3) There are avalon nightly builds in the ant directory (follow ant from
binindex), do we want these in an avalon dir with an avalon link from
the nightly section? How did they get there?
4) Are we doing a source dist?
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Peter Donald <do...@apache.org>.
At 10:29 11/5/01 -0400, Berin Loritsch wrote:
>Charles Benett wrote:
>>
>> 2) Whoever does the actual release build should do the cvs tagging.
>
>No problem there--BUT the docs aren't building. Ant keeps giving me
>the following error:
>
>BUILD FAILED
>
>C:\projects\jakarta-avalon\build.xml:309: Could not create task of type:
>stylebook. Common solutions are to use taskdef to declare your task, or,
>if this is an optional task, to put the optional.jar in the lib directory
>of your ant installation (ANT_HOME).
>
>Can someone look into this!
Looks like when Leo updated ant he didn't have stylebook in his classpath
(and thus stylebook task isn't included in optional.jar). To fix resync to
jakarta-ant and copy stylebook jar to lib/optional. If it hasn't been done
by tomorrow I will do it ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Charles Benett wrote:
>
> Berin Loritsch wrote:
> >
> > Peter Donald wrote:
> > >
> > > At 09:01 11/5/01 -0400, Berin Loritsch wrote:
> > > >OFFICIAL VOTE: Are we ready? +1 from me!
> > >
> > > +1
> > > I got heaps of changes sitting on hardisk re documentation so I will soon
> > > be able to commit them ;)
> > >
> > > >What steps need to be taken for the formal release?
> > > >
> > > >* We need to build the official packages
> > > > - LogKit 1.0b1
> > > > - Framework 4.0b1
> > > > - Excalibur 4.0b1
> > >
> > > and Tag the CVSes appropriately.
> >
> > I new there was a detail I missed!
> > The released versions need all the conditional classes in there, so do you
> > want me to build the projects and send them to you? I've never done site
> > maintenance myself...
>
> 1) I think the only conditionals are for JNDI and javax.sql, both of
> which are in JDK1.3.
>
> 2) Whoever does the actual release build should do the cvs tagging.
>
> Charles
PS - I won't volunteer to actually build as I'm at home with a dial-up
line, It would take an age to scp the dists to daedalus. I'm guessing
either Berin or Peter have fast access.
PPS if there is a 1.3 jdk on daedalus/jakarta we could build it there.
PPPS link to nightly builds is now live on website
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: build.xml - xdocs target
Posted by Stephen McConnell <mc...@osm.net>.
The optional.jar file in cornerstone and testlet is also out-of-date.
Both need to be updated to the version currently in Avalon tools/lib
because the stylebook task is not included in the CVS version.
Steve.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@osm.net]
> Sent: Saturday, 12 May, 2001 13:10
> To: Avalon Development
> Subject: RE: build.xml - xdocs target
>
>
>
> Seems to be an inconsistency between the tools used in Avalon and Phoenix:
>
> The jakarta-avalon/tools/lib contains:
>
> stylebook-1.0-b2.jar
> optional.jar (containing the Stylebook task - ok)
>
> The jakarta-avalon-phoenix/tools/lib contains:
>
> stylebook-1.0-b3_xalan-2.jar
> optional.jar (no stylebook task - cannot build xdocs)
>
> Can someone update the CVS so that phoenix has the stylebook class in
> optional.jar - and also, can anyone confirm if the differences in the
> Stylebook jar versions between Avalon and Phoenix is a feature or an
> ommission.
>
> Steve.
>
> > -----Original Message-----
> > From: Stephen McConnell [mailto:mcconnell@osm.net]
> > Sent: Saturday, 12 May, 2001 12:35
> > To: Avalon Development
> > Subject: build.xml - xdocs target
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > > ... the docs aren't building. Ant keeps giving me
> > > the following error:
> > >
> > > BUILD FAILED
> > >
> > > C:\projects\jakarta-avalon\build.xml:309: Could not create
> task of type:
> > > stylebook. Common solutions are to use taskdef to declare
> your task, or,
> > > if this is an optional task, to put the optional.jar in the lib
> > directory
> > > of your ant installation (ANT_HOME).
> > >
> > > Can someone look into this!
> >
> > Berin:
> >
> > Seems that there are a number of errors in the buildfile related to the
> > xdocs target. I have only checked jakarta-avalon/build.xml at
> > this stage -
> > here is a summary of the changes needed to get it working:
> >
> > 1. remove the comments from the following taskdef
> >
> > <!--
> > <taskdef name="stylebook"
> > classname="org.apache.stylebook.StyleBookAntTask">
> > <classpath refid="tools.class.path"/>
> > </taskdef>
> > -->
> >
> > 2. change the classname in the above taskdef to
> > "org.apache.tools.ant.taskdefs.optional.StyleBook"
> >
> > 3. the classpath references "tools.class.path" contains the
> > reference to
> > ${stylebook.jar}" but ${stylebook.jar}" is undefined, but
> > the sylebook
> > jar is explicitly included in the fileset declaration -
> the solution
> > is to either add a defintion of the stylebook.jar
> property or remove
> > the pathelement statement and exclude statement - or more simply,
> > change tools.class.path to the following:
> >
> > <path id="tools.class.path">
> > <pathelement location="${xerces.jar}"/>
> > <pathelement location="${testlet.jar}"/>
> > <fileset dir="${tools.dir}/lib">
> > <include name="*.jar" />
> > <exclude name="testlet.jar"/>
> > </fileset>
> > </path>
> >
> > After that the xdocs target executes properly.
> > I can go ahead and update the other build file if this seems an
> > appropriate
> > direction.
> >
> > Cheers, Steve.
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: build.xml - xdocs target
Posted by Stephen McConnell <mc...@osm.net>.
Seems to be an inconsistency between the tools used in Avalon and Phoenix:
The jakarta-avalon/tools/lib contains:
stylebook-1.0-b2.jar
optional.jar (containing the Stylebook task - ok)
The jakarta-avalon-phoenix/tools/lib contains:
stylebook-1.0-b3_xalan-2.jar
optional.jar (no stylebook task - cannot build xdocs)
Can someone update the CVS so that phoenix has the stylebook class in
optional.jar - and also, can anyone confirm if the differences in the
Stylebook jar versions between Avalon and Phoenix is a feature or an
ommission.
Steve.
> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@osm.net]
> Sent: Saturday, 12 May, 2001 12:35
> To: Avalon Development
> Subject: build.xml - xdocs target
>
>
>
>
> > -----Original Message-----
> > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > ... the docs aren't building. Ant keeps giving me
> > the following error:
> >
> > BUILD FAILED
> >
> > C:\projects\jakarta-avalon\build.xml:309: Could not create task of type:
> > stylebook. Common solutions are to use taskdef to declare your task, or,
> > if this is an optional task, to put the optional.jar in the lib
> directory
> > of your ant installation (ANT_HOME).
> >
> > Can someone look into this!
>
> Berin:
>
> Seems that there are a number of errors in the buildfile related to the
> xdocs target. I have only checked jakarta-avalon/build.xml at
> this stage -
> here is a summary of the changes needed to get it working:
>
> 1. remove the comments from the following taskdef
>
> <!--
> <taskdef name="stylebook"
> classname="org.apache.stylebook.StyleBookAntTask">
> <classpath refid="tools.class.path"/>
> </taskdef>
> -->
>
> 2. change the classname in the above taskdef to
> "org.apache.tools.ant.taskdefs.optional.StyleBook"
>
> 3. the classpath references "tools.class.path" contains the
> reference to
> ${stylebook.jar}" but ${stylebook.jar}" is undefined, but
> the sylebook
> jar is explicitly included in the fileset declaration - the solution
> is to either add a defintion of the stylebook.jar property or remove
> the pathelement statement and exclude statement - or more simply,
> change tools.class.path to the following:
>
> <path id="tools.class.path">
> <pathelement location="${xerces.jar}"/>
> <pathelement location="${testlet.jar}"/>
> <fileset dir="${tools.dir}/lib">
> <include name="*.jar" />
> <exclude name="testlet.jar"/>
> </fileset>
> </path>
>
> After that the xdocs target executes properly.
> I can go ahead and update the other build file if this seems an
> appropriate
> direction.
>
> Cheers, Steve.
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
build.xml - xdocs target
Posted by Stephen McConnell <mc...@osm.net>.
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> ... the docs aren't building. Ant keeps giving me
> the following error:
>
> BUILD FAILED
>
> C:\projects\jakarta-avalon\build.xml:309: Could not create task of type:
> stylebook. Common solutions are to use taskdef to declare your task, or,
> if this is an optional task, to put the optional.jar in the lib directory
> of your ant installation (ANT_HOME).
>
> Can someone look into this!
Berin:
Seems that there are a number of errors in the buildfile related to the
xdocs target. I have only checked jakarta-avalon/build.xml at this stage -
here is a summary of the changes needed to get it working:
1. remove the comments from the following taskdef
<!--
<taskdef name="stylebook"
classname="org.apache.stylebook.StyleBookAntTask">
<classpath refid="tools.class.path"/>
</taskdef>
-->
2. change the classname in the above taskdef to
"org.apache.tools.ant.taskdefs.optional.StyleBook"
3. the classpath references "tools.class.path" contains the reference to
${stylebook.jar}" but ${stylebook.jar}" is undefined, but the sylebook
jar is explicitly included in the fileset declaration - the solution
is to either add a defintion of the stylebook.jar property or remove
the pathelement statement and exclude statement - or more simply,
change tools.class.path to the following:
<path id="tools.class.path">
<pathelement location="${xerces.jar}"/>
<pathelement location="${testlet.jar}"/>
<fileset dir="${tools.dir}/lib">
<include name="*.jar" />
<exclude name="testlet.jar"/>
</fileset>
</path>
After that the xdocs target executes properly.
I can go ahead and update the other build file if this seems an appropriate
direction.
Cheers, Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Berin Loritsch <bl...@apache.org>.
Stephen McConnell wrote:
>
> Berin:
> Which target you applying in the build ?
> Steve.
I am using
build clean distributions
for both jakarta-avalon and jakarta-avalon-logkit.
>
> > -----Original Message-----
> > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > Sent: Friday, 11 May, 2001 16:30
> > To: Avalon Development
> > Subject: Re: [Formal Release] Today's the day!
> >
> >
> > Charles Benett wrote:
> > >
> > > 2) Whoever does the actual release build should do the cvs tagging.
> >
> > No problem there--BUT the docs aren't building. Ant keeps giving me
> > the following error:
> >
> > BUILD FAILED
> >
> > C:\projects\jakarta-avalon\build.xml:309: Could not create task of type:
> > stylebook. Common solutions are to use taskdef to declare your task, or,
> > if this is an optional task, to put the optional.jar in the lib directory
> > of your ant installation (ANT_HOME).
> >
> > Can someone look into this!
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: [Formal Release] Today's the day!
Posted by Stephen McConnell <mc...@osm.net>.
Berin:
Which target you applying in the build ?
Steve.
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> Sent: Friday, 11 May, 2001 16:30
> To: Avalon Development
> Subject: Re: [Formal Release] Today's the day!
>
>
> Charles Benett wrote:
> >
> > 2) Whoever does the actual release build should do the cvs tagging.
>
> No problem there--BUT the docs aren't building. Ant keeps giving me
> the following error:
>
> BUILD FAILED
>
> C:\projects\jakarta-avalon\build.xml:309: Could not create task of type:
> stylebook. Common solutions are to use taskdef to declare your task, or,
> if this is an optional task, to put the optional.jar in the lib directory
> of your ant installation (ANT_HOME).
>
> Can someone look into this!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Berin Loritsch <bl...@apache.org>.
Charles Benett wrote:
>
> 2) Whoever does the actual release build should do the cvs tagging.
No problem there--BUT the docs aren't building. Ant keeps giving me
the following error:
BUILD FAILED
C:\projects\jakarta-avalon\build.xml:309: Could not create task of type:
stylebook. Common solutions are to use taskdef to declare your task, or,
if this is an optional task, to put the optional.jar in the lib directory
of your ant installation (ANT_HOME).
Can someone look into this!
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Berin Loritsch wrote:
>
> Peter Donald wrote:
> >
> > At 09:01 11/5/01 -0400, Berin Loritsch wrote:
> > >OFFICIAL VOTE: Are we ready? +1 from me!
> >
> > +1
> > I got heaps of changes sitting on hardisk re documentation so I will soon
> > be able to commit them ;)
> >
> > >What steps need to be taken for the formal release?
> > >
> > >* We need to build the official packages
> > > - LogKit 1.0b1
> > > - Framework 4.0b1
> > > - Excalibur 4.0b1
> >
> > and Tag the CVSes appropriately.
>
> I new there was a detail I missed!
> The released versions need all the conditional classes in there, so do you
> want me to build the projects and send them to you? I've never done site
> maintenance myself...
1) I think the only conditionals are for JNDI and javax.sql, both of
which are in JDK1.3.
2) Whoever does the actual release build should do the cvs tagging.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Berin Loritsch wrote:
>
> Peter Donald wrote:
> >
> > At 09:01 11/5/01 -0400, Berin Loritsch wrote:
> > >* We need to update the site with the new site docs
> > > and the releases. (Is there any way we can get a
> > > link at http://jakarta.apache.org/site/binindex.html?)
> >
> > Tell me when your ready and I will do it.
>
> So, do I take the generated docs and overwrite what's in the
> www directory?
Woaa! (Or not exactly) Unless something has changed, the www dir (used
by webserver) is a checkout from avalon cvs. Once the (tagged) html docs
are commited in avalon cvs, just cd to /www/jakarta.apache.org/avalon
and cvs update.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Peter Donald <do...@apache.org>.
At 09:39 11/5/01 -0400, Berin Loritsch wrote:
>> >* We need to build the official packages
>> > - LogKit 1.0b1
>> > - Framework 4.0b1
>> > - Excalibur 4.0b1
>>
>> and Tag the CVSes appropriately.
>
>I new there was a detail I missed!
>The released versions need all the conditional classes in there, so do you
>want me to build the projects and send them to you? I've never done site
>maintenance myself...
It should be just a matter of copying the binarie to correct place on
daedalus. A command like
scp Avalon* bloritsch@jakarta.apache.org:/www/jakarta.apache.org/bu
ilds/jakarta-avalon/release/
>> >* We need to update the site with the new site docs
>> > and the releases. (Is there any way we can get a
>> > link at http://jakarta.apache.org/site/binindex.html?)
>>
>> Tell me when your ready and I will do it.
>
>So, do I take the generated docs and overwrite what's in the
>www directory?
for our site you just update the www CVS directory and then goto daedalus
and check them out ala
cd /www/jakarta.apache.org/avalon
cvs update
cd /www/jakarta.apache.org/avalon/framework
cvs update
cd /www/jakarta.apache.org/avalon/logkit
cvs update
And that should be it ... I think ;)
For the main site ... either me or Charles can do it I guess ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by giacomo <gi...@apache.org>.
On Fri, 11 May 2001, Berin Loritsch wrote:
> Peter Donald wrote:
> >
> > At 09:01 11/5/01 -0400, Berin Loritsch wrote:
> > >OFFICIAL VOTE: Are we ready? +1 from me!
> >
> > +1
> > I got heaps of changes sitting on hardisk re documentation so I will soon
> > be able to commit them ;)
> >
> > >What steps need to be taken for the formal release?
> > >
> > >* We need to build the official packages
> > > - LogKit 1.0b1
> > > - Framework 4.0b1
> > > - Excalibur 4.0b1
> >
> > and Tag the CVSes appropriately.
>
> I new there was a detail I missed!
> The released versions need all the conditional classes in there, so do you
> want me to build the projects and send them to you? I've never done site
> maintenance myself...
>
> > >* We need to update the site with the new site docs
> > > and the releases. (Is there any way we can get a
> > > link at http://jakarta.apache.org/site/binindex.html?)
> >
> > Tell me when your ready and I will do it.
>
> So, do I take the generated docs and overwrite what's in the
> www directory?
In C2 I do the following:
build.sh -verbose site (builds the www site)
cvs commit foo (if not already done)
cd ../xml-site/cocoon (the site will be build outside the repo)
tar cvfz ../cocoon.tgz *
scp ../cocoon.tgz greenrd@apache.org:/tmp
ssh giacomo@apache.org
cd /www/xml.apache.org/cocoon
tar xvfz /tmp/cocoon.tgz
rm -f /tmp/cocoon.tgz
Something similar should be done for jakarta I guess.
Giacomo
>
> > >* We need to make announcements to xml-announce and
> > > jakarta-announce about Avalon 4.0b1. Please note,
> > > that I would like to wait until the other two steps
> > > have been completed first.
> >
> > sounds - buzz not writing the release note though ;) My english is sucking
> > very badly of late ;]
>
> I can take care of the release notes.
>
> > >Am I missing anything?
> >
> > Besides the CVS tag we should also bump versions post release/TAG.
>
> The new version numbers post release should be 1.0b2[rc1] and 4.0b2[rc1]
> and we bump up the [rc] numbers as we get closer to the Beta 2 release.
>
> > BTW has everyone made sure that the distributions build a-ok and include
> > all relevent stuff?
>
> So far so good.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
>
> At 09:01 11/5/01 -0400, Berin Loritsch wrote:
> >OFFICIAL VOTE: Are we ready? +1 from me!
>
> +1
> I got heaps of changes sitting on hardisk re documentation so I will soon
> be able to commit them ;)
>
> >What steps need to be taken for the formal release?
> >
> >* We need to build the official packages
> > - LogKit 1.0b1
> > - Framework 4.0b1
> > - Excalibur 4.0b1
>
> and Tag the CVSes appropriately.
I new there was a detail I missed!
The released versions need all the conditional classes in there, so do you
want me to build the projects and send them to you? I've never done site
maintenance myself...
> >* We need to update the site with the new site docs
> > and the releases. (Is there any way we can get a
> > link at http://jakarta.apache.org/site/binindex.html?)
>
> Tell me when your ready and I will do it.
So, do I take the generated docs and overwrite what's in the
www directory?
> >* We need to make announcements to xml-announce and
> > jakarta-announce about Avalon 4.0b1. Please note,
> > that I would like to wait until the other two steps
> > have been completed first.
>
> sounds - buzz not writing the release note though ;) My english is sucking
> very badly of late ;]
I can take care of the release notes.
> >Am I missing anything?
>
> Besides the CVS tag we should also bump versions post release/TAG.
The new version numbers post release should be 1.0b2[rc1] and 4.0b2[rc1]
and we bump up the [rc] numbers as we get closer to the Beta 2 release.
> BTW has everyone made sure that the distributions build a-ok and include
> all relevent stuff?
So far so good.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: [Formal Release] Today's the day!
Posted by Stephen McConnell <mc...@osm.net>.
> BTW has everyone made sure that the distributions build a-ok and include
> all relevent stuff?
Yep - I can confirm that the build has been ok over the last week.
I'll run a clean build againt today to verify.
Steve.
Stephen J. McConnell, OSM sarl
digital products for a global economy
http://www.osm.net
mailto:mcconnell@osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [Formal Release] Today's the day!
Posted by Peter Donald <do...@apache.org>.
At 09:01 11/5/01 -0400, Berin Loritsch wrote:
>OFFICIAL VOTE: Are we ready? +1 from me!
+1
I got heaps of changes sitting on hardisk re documentation so I will soon
be able to commit them ;)
>What steps need to be taken for the formal release?
>
>* We need to build the official packages
> - LogKit 1.0b1
> - Framework 4.0b1
> - Excalibur 4.0b1
and Tag the CVSes appropriately.
>* We need to update the site with the new site docs
> and the releases. (Is there any way we can get a
> link at http://jakarta.apache.org/site/binindex.html?)
Tell me when your ready and I will do it.
>* We need to make announcements to xml-announce and
> jakarta-announce about Avalon 4.0b1. Please note,
> that I would like to wait until the other two steps
> have been completed first.
sounds - buzz not writing the release note though ;) My english is sucking
very badly of late ;]
>Am I missing anything?
Besides the CVS tag we should also bump versions post release/TAG.
BTW has everyone made sure that the distributions build a-ok and include
all relevent stuff?
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: [Formal Release] Today's the day!
Posted by Leo Simons <ma...@leosimons.com>.
> > Looks like when Leo updated ant he didn't have stylebook in his
> classpath
> > (and thus stylebook task isn't included in optional.jar). To
> fix resync to
>
> ? Updated version builds correctly on my system...oh well...58 days to
> linux-switch and counting...
that was the prob. Saw Berin updated the avalon files. Could someone
do the same for the other CVSes? (I mean, someone with a cable
connection or something; binary transfer over dialin isn't really
a hobby of mine ;)
g'night!
Leo Simons
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: [Formal Release] Today's the day!
Posted by Leo Simons <ma...@leosimons.com>.
> OFFICIAL VOTE: Are we ready? +1 from me!
+1
> Looks like when Leo updated ant he didn't have stylebook in his classpath
> (and thus stylebook task isn't included in optional.jar). To fix resync to
? Updated version builds correctly on my system...oh well...58 days to
linux-switch and counting...
> I got heaps of changes sitting on hardisk re documentation so I will soon
> be able to commit them ;)
me too...I hope we didn't do too much duplicate docs...BTW, you go first;
I've barely got enough free time to keep up on my e-mail atm. Anyways,
here's
to avalon:
cheers!
Leo Simons
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org