You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Paul Benedict <pb...@apache.org> on 2007/03/10 21:48:40 UTC
How to publish s1?
There are three remaining steps to accomplish.
* Update main website pages
* Publish artifacts
* Release distribution
Niall is going to help with #1. Does anyone have directions on how to
accomplish the other 2?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: How to publish s1?
Posted by Paul Benedict <pb...@apache.org>.
I deleted struts-current* from dist/struts
Wendy Smoak wrote:
> On 3/11/07, Martin Cooper <ma...@apache.org> wrote:
>
>> Now we are specifically being told to *not*
>> create symbolic links! In fact, the instructions seem to indicate that
>> the
>> 'current' links probably shouldn't be created any more.
>
> Thanks, Martin. Let's delete them, then... one less step in the
> release process is good. :)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: How to publish s1?
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/11/07, Martin Cooper <ma...@apache.org> wrote:
> Now we are specifically being told to *not*
> create symbolic links! In fact, the instructions seem to indicate that the
> 'current' links probably shouldn't be created any more.
Thanks, Martin. Let's delete them, then... one less step in the
release process is good. :)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: How to publish s1?
Posted by Martin Cooper <ma...@apache.org>.
On 3/11/07, Ted Husted <hu...@apache.org> wrote:
>
> Updating symbolic links isn't on the S2 distribution punchlist
>
> *
> http://struts.apache.org/2.0.6/docs/creating-and-signing-a-distribution.html
>
> which means I haven't been doing it. (This list really, really,
> really, is exactly what I've been doing; no more, no less.)
>
> It also means that I don't know or remember what these links do or why
> we need them.
The 'current' links used to be required / recommended as part of the
mirroring strategy. I just went looking for the instructions that used to
tell us how to set them up, and discovered that this has changed, apparently
without notice. (At least I certainly don't remember being notified that the
mirroring requirements changed.) Now we are specifically being told to *not*
create symbolic links! In fact, the instructions seem to indicate that the
'current' links probably shouldn't be created any more.
http://www.apache.org/dev/mirror-step-by-step.html
So, you're probably doing it right after all, Ted. ;-)
--
Martin Cooper
-Ted.
>
> On 3/10/07, Wendy Smoak <ws...@gmail.com> wrote:
> > On 3/10/07, Wendy Smoak <ws...@gmail.com> wrote:
> >
> > > In addition, you need to
> > > update the "current" links to point to the new version. I can't
> > > remember whether you have to delete the old ones first, but it's
> > > ln -s [target] [link-name].
> >
> > Actually... Struts 2 has a GA release now, so I think that gets the
> > "current" links. (Right now they're pointing at the 1.3.5 release.)
> >
> > --
> > Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: How to publish s1?
Posted by Ted Husted <hu...@apache.org>.
Updating symbolic links isn't on the S2 distribution punchlist
* http://struts.apache.org/2.0.6/docs/creating-and-signing-a-distribution.html
which means I haven't been doing it. (This list really, really,
really, is exactly what I've been doing; no more, no less.)
It also means that I don't know or remember what these links do or why
we need them.
-Ted.
On 3/10/07, Wendy Smoak <ws...@gmail.com> wrote:
> On 3/10/07, Wendy Smoak <ws...@gmail.com> wrote:
>
> > In addition, you need to
> > update the "current" links to point to the new version. I can't
> > remember whether you have to delete the old ones first, but it's
> > ln -s [target] [link-name].
>
> Actually... Struts 2 has a GA release now, so I think that gets the
> "current" links. (Right now they're pointing at the 1.3.5 release.)
>
> --
> Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: How to publish s1?
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/10/07, Wendy Smoak <ws...@gmail.com> wrote:
> In addition, you need to
> update the "current" links to point to the new version. I can't
> remember whether you have to delete the old ones first, but it's
> ln -s [target] [link-name].
Actually... Struts 2 has a GA release now, so I think that gets the
"current" links. (Right now they're pointing at the 1.3.5 release.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: How to publish s1?
Posted by Niall Pemberton <ni...@gmail.com>.
On 3/10/07, Wendy Smoak <ws...@gmail.com> wrote:
> On 3/10/07, Paul Benedict <pb...@apache.org> wrote:
> > There are three remaining steps to accomplish.
> > * Update main website pages
> > * Publish artifacts
> > * Release distribution
> >
> > Niall is going to help with #1. Does anyone have directions on how to
> > accomplish the other 2?
>
> Assuming you mean putting the artifacts in the Maven repo, you can
> copy them from the staging repo over to the same directory structure
> under people.apache.org/repo/m2-ibiblio-rsync-repository.
>
> (Copying breaks the repository metadata, but I'm not confident enough
> in the unreleased repositorytools project yet.)
>
> Publishing the release distribution is also a file copy, to the right
> place under www.apache.org/dist/struts. In addition, you need to
> update the "current" links to point to the new version. I can't
> remember whether you have to delete the old ones first, but it's
> ln -s [target] [link-name].
AFAIK you have to delete them:
http://jakarta.apache.org/commons/releases/release.html#7%20Update%20Release%20Directory
> Please update the release instructions for the next person...
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: How to publish s1?
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/10/07, Paul Benedict <pb...@apache.org> wrote:
> There are three remaining steps to accomplish.
> * Update main website pages
> * Publish artifacts
> * Release distribution
>
> Niall is going to help with #1. Does anyone have directions on how to
> accomplish the other 2?
Assuming you mean putting the artifacts in the Maven repo, you can
copy them from the staging repo over to the same directory structure
under people.apache.org/repo/m2-ibiblio-rsync-repository.
(Copying breaks the repository metadata, but I'm not confident enough
in the unreleased repositorytools project yet.)
Publishing the release distribution is also a file copy, to the right
place under www.apache.org/dist/struts. In addition, you need to
update the "current" links to point to the new version. I can't
remember whether you have to delete the old ones first, but it's
ln -s [target] [link-name].
Please update the release instructions for the next person...
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org