You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by mo...@apache.org on 2001/05/03 17:34:06 UTC

cvs commit: jakarta-taglibs HOWTO-RELEASE

morgand     01/05/03 08:34:05

  Modified:    .        HOWTO-RELEASE
  Log:
  fixing instructions for beta releases (didn't I already do this?)
  
  Revision  Changes    Path
  1.5       +1 -1      jakarta-taglibs/HOWTO-RELEASE
  
  Index: HOWTO-RELEASE
  ===================================================================
  RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- HOWTO-RELEASE	2001/04/16 23:58:31	1.4
  +++ HOWTO-RELEASE	2001/05/03 15:33:58	1.5
  @@ -51,7 +51,7 @@
   
   2.5 "BETA" RELEASE NUMBERS
   
  -Beta releases are denoted by adding the phrase "beta" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta.jar.
  +Beta releases are denoted by adding the phrase "beta<beta version number>" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta1.jar.
   
   3 STARTING/COMPLETING MAJOR RELEASES
   
  
  
  

Re: cvs commit: jakarta-taglibs HOWTO-RELEASE

Posted by Glenn Nielsen <gl...@voyager.apg.more.net>.
As part of my work to overhaul the jakarta-taglibs dir/file layout and
build process I will be working with Justyna to update the nightly
crontab scripts used to update http://jakarta.apache.org/taglibs.

Regards,

Glenn

horwat wrote:
> 
> I use scp when I need to push things out to the site. Something as simple
> as:
> 
> ----
> #!/bin/ksh
> 
> export BUILD_HOME="/home/horwat/Build"
> 
> echo "Copying web docs to jakarta site"
> 
> /home/horwat/ssh/bin/scp -r $BUILD_HOME/build/taglibs/*-doc \
>     horwat@jakarta.apache.org:/www/jakarta.apache.org/taglibs/doc
> 
> echo "END Copying web docs to jakarta site"
> ----
> 
> Justy
> 
> ----- Original Message -----
> 
> > Sure thing.  I'll also put it on the home page, as soon as I figure out
> > how to push stuff out.  I don't suppose anyone has some hints on
> > that?  :)  If so, I'll be sure to immortalize your comments in the
> > HOWTO-RELEASE docs.
> >
> > - Morgan
> >
> > On Fri, 4 May 2001, Glenn Nielsen wrote:
> >
> > > Morgan,
> > >
> > > jakarta-taglibs-sandbox has been created, will you be mentioning it
> > > in the HOWTO-RELEASE document?
> > >
> > > Thanks for taking the lead on this.
> > >
> > > Regards,
> > >
> > > Glenn
> > >
> > > morgand@apache.org wrote:
> > > >
> > > > morgand     01/05/03 08:34:05
> > > >
> > > >   Modified:    .        HOWTO-RELEASE
> > > >   Log:
> > > >   fixing instructions for beta releases (didn't I already do this?)
> > > >
> > > >   Revision  Changes    Path
> > > >   1.5       +1 -1      jakarta-taglibs/HOWTO-RELEASE
> > > >
> > > >   Index: HOWTO-RELEASE
> > > >   ===================================================================
> > > >   RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
> > > >   retrieving revision 1.4
> > > >   retrieving revision 1.5
> > > >   diff -u -r1.4 -r1.5
> > > >   --- HOWTO-RELEASE     2001/04/16 23:58:31     1.4
> > > >   +++ HOWTO-RELEASE     2001/05/03 15:33:58     1.5
> > > >   @@ -51,7 +51,7 @@
> > > >
> > > >    2.5 "BETA" RELEASE NUMBERS
> > > >
> > > >   -Beta releases are denoted by adding the phrase "beta" after the
> release number in the released archive.  For example, if the current release
> version is 2.0.4, and the developer wished to preview the next major
> release, the jar would be named foo-3.0-beta.jar.
> > > >   +Beta releases are denoted by adding the phrase "beta<beta version
> number>" after the release number in the released archive.  For example, if
> the current release version is 2.0.4, and the developer wished to preview
> the next major release, the jar would be named foo-3.0-beta1.jar.
> > > >
> > > >    3 STARTING/COMPLETING MAJOR RELEASES
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > ----------------------------------------------------------------------
> > > Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> > > MOREnet System Programming               |  * if iz ina coment.      |
> > > Missouri Research and Education Network  |  */                       |
> > > ----------------------------------------------------------------------
> > >
> >
> >

-- 
----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

Re: cvs commit: jakarta-taglibs HOWTO-RELEASE

Posted by horwat <Ju...@Sun.COM>.
I use scp when I need to push things out to the site. Something as simple
as:

----
#!/bin/ksh

export BUILD_HOME="/home/horwat/Build"

echo "Copying web docs to jakarta site"

/home/horwat/ssh/bin/scp -r $BUILD_HOME/build/taglibs/*-doc \
    horwat@jakarta.apache.org:/www/jakarta.apache.org/taglibs/doc

echo "END Copying web docs to jakarta site"
----


Justy


----- Original Message -----

> Sure thing.  I'll also put it on the home page, as soon as I figure out
> how to push stuff out.  I don't suppose anyone has some hints on
> that?  :)  If so, I'll be sure to immortalize your comments in the
> HOWTO-RELEASE docs.
>
> - Morgan
>
> On Fri, 4 May 2001, Glenn Nielsen wrote:
>
> > Morgan,
> >
> > jakarta-taglibs-sandbox has been created, will you be mentioning it
> > in the HOWTO-RELEASE document?
> >
> > Thanks for taking the lead on this.
> >
> > Regards,
> >
> > Glenn
> >
> > morgand@apache.org wrote:
> > >
> > > morgand     01/05/03 08:34:05
> > >
> > >   Modified:    .        HOWTO-RELEASE
> > >   Log:
> > >   fixing instructions for beta releases (didn't I already do this?)
> > >
> > >   Revision  Changes    Path
> > >   1.5       +1 -1      jakarta-taglibs/HOWTO-RELEASE
> > >
> > >   Index: HOWTO-RELEASE
> > >   ===================================================================
> > >   RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
> > >   retrieving revision 1.4
> > >   retrieving revision 1.5
> > >   diff -u -r1.4 -r1.5
> > >   --- HOWTO-RELEASE     2001/04/16 23:58:31     1.4
> > >   +++ HOWTO-RELEASE     2001/05/03 15:33:58     1.5
> > >   @@ -51,7 +51,7 @@
> > >
> > >    2.5 "BETA" RELEASE NUMBERS
> > >
> > >   -Beta releases are denoted by adding the phrase "beta" after the
release number in the released archive.  For example, if the current release
version is 2.0.4, and the developer wished to preview the next major
release, the jar would be named foo-3.0-beta.jar.
> > >   +Beta releases are denoted by adding the phrase "beta<beta version
number>" after the release number in the released archive.  For example, if
the current release version is 2.0.4, and the developer wished to preview
the next major release, the jar would be named foo-3.0-beta1.jar.
> > >
> > >    3 STARTING/COMPLETING MAJOR RELEASES
> > >
> > >
> > >
> > >
> >
> > --
> > ----------------------------------------------------------------------
> > Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> > MOREnet System Programming               |  * if iz ina coment.      |
> > Missouri Research and Education Network  |  */                       |
> > ----------------------------------------------------------------------
> >
>
>


Re: cvs commit: jakarta-taglibs HOWTO-RELEASE

Posted by Morgan Delagrange <mo...@apache.org>.
Do I just ftp files out to /www/jakarta.apache.org/taglibs?  That doesn't
look too tough.

On Mon, 7 May 2001, Morgan Delagrange wrote:

> Sure thing.  I'll also put it on the home page, as soon as I figure out
> how to push stuff out.  I don't suppose anyone has some hints on
> that?  :)  If so, I'll be sure to immortalize your comments in the
> HOWTO-RELEASE docs.
> 
> - Morgan
> 
> On Fri, 4 May 2001, Glenn Nielsen wrote:
> 
> > Morgan,
> > 
> > jakarta-taglibs-sandbox has been created, will you be mentioning it
> > in the HOWTO-RELEASE document?
> > 
> > Thanks for taking the lead on this.
> > 
> > Regards,
> > 
> > Glenn
> > 
> > morgand@apache.org wrote:
> > > 
> > > morgand     01/05/03 08:34:05
> > > 
> > >   Modified:    .        HOWTO-RELEASE
> > >   Log:
> > >   fixing instructions for beta releases (didn't I already do this?)
> > > 
> > >   Revision  Changes    Path
> > >   1.5       +1 -1      jakarta-taglibs/HOWTO-RELEASE
> > > 
> > >   Index: HOWTO-RELEASE
> > >   ===================================================================
> > >   RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
> > >   retrieving revision 1.4
> > >   retrieving revision 1.5
> > >   diff -u -r1.4 -r1.5
> > >   --- HOWTO-RELEASE     2001/04/16 23:58:31     1.4
> > >   +++ HOWTO-RELEASE     2001/05/03 15:33:58     1.5
> > >   @@ -51,7 +51,7 @@
> > > 
> > >    2.5 "BETA" RELEASE NUMBERS
> > > 
> > >   -Beta releases are denoted by adding the phrase "beta" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta.jar.
> > >   +Beta releases are denoted by adding the phrase "beta<beta version number>" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta1.jar.
> > > 
> > >    3 STARTING/COMPLETING MAJOR RELEASES
> > > 
> > > 
> > > 
> > > 
> > 
> > -- 
> > ----------------------------------------------------------------------
> > Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> > MOREnet System Programming               |  * if iz ina coment.      |
> > Missouri Research and Education Network  |  */                       |
> > ----------------------------------------------------------------------
> > 
> 
> 


Re: cvs commit: jakarta-taglibs HOWTO-RELEASE

Posted by Morgan Delagrange <mo...@apache.org>.
Sure thing.  I'll also put it on the home page, as soon as I figure out
how to push stuff out.  I don't suppose anyone has some hints on
that?  :)  If so, I'll be sure to immortalize your comments in the
HOWTO-RELEASE docs.

- Morgan

On Fri, 4 May 2001, Glenn Nielsen wrote:

> Morgan,
> 
> jakarta-taglibs-sandbox has been created, will you be mentioning it
> in the HOWTO-RELEASE document?
> 
> Thanks for taking the lead on this.
> 
> Regards,
> 
> Glenn
> 
> morgand@apache.org wrote:
> > 
> > morgand     01/05/03 08:34:05
> > 
> >   Modified:    .        HOWTO-RELEASE
> >   Log:
> >   fixing instructions for beta releases (didn't I already do this?)
> > 
> >   Revision  Changes    Path
> >   1.5       +1 -1      jakarta-taglibs/HOWTO-RELEASE
> > 
> >   Index: HOWTO-RELEASE
> >   ===================================================================
> >   RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
> >   retrieving revision 1.4
> >   retrieving revision 1.5
> >   diff -u -r1.4 -r1.5
> >   --- HOWTO-RELEASE     2001/04/16 23:58:31     1.4
> >   +++ HOWTO-RELEASE     2001/05/03 15:33:58     1.5
> >   @@ -51,7 +51,7 @@
> > 
> >    2.5 "BETA" RELEASE NUMBERS
> > 
> >   -Beta releases are denoted by adding the phrase "beta" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta.jar.
> >   +Beta releases are denoted by adding the phrase "beta<beta version number>" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta1.jar.
> > 
> >    3 STARTING/COMPLETING MAJOR RELEASES
> > 
> > 
> > 
> > 
> 
> -- 
> ----------------------------------------------------------------------
> Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> MOREnet System Programming               |  * if iz ina coment.      |
> Missouri Research and Education Network  |  */                       |
> ----------------------------------------------------------------------
> 


Re: cvs commit: jakarta-taglibs HOWTO-RELEASE

Posted by Glenn Nielsen <gl...@voyager.apg.more.net>.
Morgan,

jakarta-taglibs-sandbox has been created, will you be mentioning it
in the HOWTO-RELEASE document?

Thanks for taking the lead on this.

Regards,

Glenn

morgand@apache.org wrote:
> 
> morgand     01/05/03 08:34:05
> 
>   Modified:    .        HOWTO-RELEASE
>   Log:
>   fixing instructions for beta releases (didn't I already do this?)
> 
>   Revision  Changes    Path
>   1.5       +1 -1      jakarta-taglibs/HOWTO-RELEASE
> 
>   Index: HOWTO-RELEASE
>   ===================================================================
>   RCS file: /home/cvs/jakarta-taglibs/HOWTO-RELEASE,v
>   retrieving revision 1.4
>   retrieving revision 1.5
>   diff -u -r1.4 -r1.5
>   --- HOWTO-RELEASE     2001/04/16 23:58:31     1.4
>   +++ HOWTO-RELEASE     2001/05/03 15:33:58     1.5
>   @@ -51,7 +51,7 @@
> 
>    2.5 "BETA" RELEASE NUMBERS
> 
>   -Beta releases are denoted by adding the phrase "beta" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta.jar.
>   +Beta releases are denoted by adding the phrase "beta<beta version number>" after the release number in the released archive.  For example, if the current release version is 2.0.4, and the developer wished to preview the next major release, the jar would be named foo-3.0-beta1.jar.
> 
>    3 STARTING/COMPLETING MAJOR RELEASES
> 
> 
> 
> 

-- 
----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------