You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Jeremias Maerki <je...@apache.org> on 2005/10/06 16:33:37 UTC
[NOTICE] xml-site CVS repository to be migrated to SVN
The xml-site CVS module is about to be migrated to SVN shortly. This has
some effects on website deployment for websites under
http://xml.apache.org. Currently, all the generated websites are
uploaded under the targets directory in the xml-site repository and
updated on cvs.apache.org using a CVS update.
I strongly suggest to the Xerces and Xalan projects to deploy their
subproject websites under their subdomain and instead add ".htaccess"
files under xml.apache.org, like the other TLP-promoted projects have
done, to redirect visitors to the new location. Examples of .htaccess
files can be found for FOP, Batik, Cocoon, Forrest etc. FOP's .htaccess
file looks like this:
RedirectPermanent /fop http://xmlgraphics.apache.org/fop
Using Forrest 0.7 to create the xml.apache.org site and having had good
experiences for the XML Graphics and FOP sites, I'm going to change the
xml.apache.org deployment to use (local) ForrestBot. The generated site
will not be committed to the SVN repository anymore, but directly
uploaded using SCP to cvs.apache.org:/www/xml.apache.org. If someone
doesn't agree with that, please tell me. The other subproject sites can
still be uploaded to the targets directory (only now through SVN which
will take some manual work on minotaur).
As soon as the SVN migration is completed I'm going to:
- update the xml.apache.org site
- remove the obsolete FOP website from the targets directory.
- remove the obsolete SOAP website (now found here: http://ws.apache.org/soap/)
- remove the obsolete XMLBeans website (now found here: http://xmlbeans.apache.org/)
- document the new deployment process
- help anyone who gets stuck
I won't touch the other XML subproject sites unless asked to.
The xml.apache.org site will be located here after the migration:
https://svn.apache.org/repos/asf/xml/site/
Check out using: svn co https://svn.apache.org/repos/asf/xml/site/
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: [NOTICE] xml-site CVS repository to be migrated to SVN
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
After republishing the site again after the latest changes, I see why my
approach may not be the best. mirrors.cgi on Windows has CRLF
line-endings and is copied as such to minotaur. Furthermore, no
executable permission is set. This could be avoided by setting different
properties on mirrors.cgi in SVN and adjusting the post-process script
in publish.xml but both problems are easily solveable with SVN. Sigh.
On 13.10.2005 10:31:18 Jeremias Maerki wrote:
> Two reasons:
> - One step less for publishing the site. Because the whole process is so
> complicated and annoying people tend not to do anything. That's bad.
> - I don't like storing generated files in version control. It makes no
> sense IMO.
>
> I agree that reverting changes may be a little bit more difficult, but
> with ForrestBot regenerating the site is a no-brainer. No hard feelings
> if we go back to committing the generated site to SVN but I don't like
> it.
>
> On 13.10.2005 09:48:32 David Crossley wrote:
> > Jeremias Maerki wrote:
> > >
> > > Using Forrest 0.7 to create the xml.apache.org site and having had good
> > > experiences for the XML Graphics and FOP sites, I'm going to change the
> > > xml.apache.org deployment to use (local) ForrestBot.
> >
> > Great.
> >
> > > The generated site
> > > will not be committed to the SVN repository anymore, but directly
> > > uploaded using SCP to cvs.apache.org:/www/xml.apache.org. If someone
> > > doesn't agree with that, please tell me.
> >
> > What is the reason for doing that?
> >
> > For any projects that i have worked on, we have
> > remained with storing the generated docs in SVN.
> > It seems more efficient.
> >
> > Also that is what infra wanted. It makes it possible
> > to restore a site easily. The people at site-dev@a.o
> > are trying to work out better ways of publishing sites,
> > but not happened yet.
> >
> > There are a couple of problems with doing stuff via scp.
> > One is that it uploads every doc, even if not changed.
> > Also it is harder to revert a change if we stuff up.
> >
> > Even though i don't agree with using SCP, i am not
> > going to suggest changing it. What you have done does
> > work okay and xml-site is a small site and is not
> > receiving lots of changes.
> >
> > Still, i am interested to know why you think SCP
> > is better.
> >
> > -David
>
>
> Jeremias Maerki
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: [NOTICE] xml-site CVS repository to be migrated to SVN
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Two reasons:
- One step less for publishing the site. Because the whole process is so
complicated and annoying people tend not to do anything. That's bad.
- I don't like storing generated files in version control. It makes no
sense IMO.
I agree that reverting changes may be a little bit more difficult, but
with ForrestBot regenerating the site is a no-brainer. No hard feelings
if we go back to committing the generated site to SVN but I don't like
it.
On 13.10.2005 09:48:32 David Crossley wrote:
> Jeremias Maerki wrote:
> >
> > Using Forrest 0.7 to create the xml.apache.org site and having had good
> > experiences for the XML Graphics and FOP sites, I'm going to change the
> > xml.apache.org deployment to use (local) ForrestBot.
>
> Great.
>
> > The generated site
> > will not be committed to the SVN repository anymore, but directly
> > uploaded using SCP to cvs.apache.org:/www/xml.apache.org. If someone
> > doesn't agree with that, please tell me.
>
> What is the reason for doing that?
>
> For any projects that i have worked on, we have
> remained with storing the generated docs in SVN.
> It seems more efficient.
>
> Also that is what infra wanted. It makes it possible
> to restore a site easily. The people at site-dev@a.o
> are trying to work out better ways of publishing sites,
> but not happened yet.
>
> There are a couple of problems with doing stuff via scp.
> One is that it uploads every doc, even if not changed.
> Also it is harder to revert a change if we stuff up.
>
> Even though i don't agree with using SCP, i am not
> going to suggest changing it. What you have done does
> work okay and xml-site is a small site and is not
> receiving lots of changes.
>
> Still, i am interested to know why you think SCP
> is better.
>
> -David
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: [NOTICE] xml-site CVS repository to be migrated to SVN
Posted by David Crossley <cr...@apache.org>.
Jeremias Maerki wrote:
>
> Using Forrest 0.7 to create the xml.apache.org site and having had good
> experiences for the XML Graphics and FOP sites, I'm going to change the
> xml.apache.org deployment to use (local) ForrestBot.
Great.
> The generated site
> will not be committed to the SVN repository anymore, but directly
> uploaded using SCP to cvs.apache.org:/www/xml.apache.org. If someone
> doesn't agree with that, please tell me.
What is the reason for doing that?
For any projects that i have worked on, we have
remained with storing the generated docs in SVN.
It seems more efficient.
Also that is what infra wanted. It makes it possible
to restore a site easily. The people at site-dev@a.o
are trying to work out better ways of publishing sites,
but not happened yet.
There are a couple of problems with doing stuff via scp.
One is that it uploads every doc, even if not changed.
Also it is harder to revert a change if we stuff up.
Even though i don't agree with using SCP, i am not
going to suggest changing it. What you have done does
work okay and xml-site is a small site and is not
receiving lots of changes.
Still, i am interested to know why you think SCP
is better.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: [NOTICE] xml-site CVS repository to be migrated to SVN
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
The XML site has been migrated and I've updated it today according to
the notes cited below. I've also already deployed the updated XML
website. It should show up after the next rsync.
XML subprojects: Don't forget to remove the old CVS working copy and
to replace it with an SVN checkout the next time you update the
subproject website.
Migrated (sub)projects: Please consider deploying your project websites
under the new subdomains next time you update the site. When you do that
please remove the old site and replace it with a .htaccess file as
described below.
A note for those using Stylebook: Stylebook has also been migrated to
SVN! Consider migrating to Apache Forrest. ;-)
If there's anything, I'm around. :-)
On 06.10.2005 16:33:37 Jeremias Maerki wrote:
> The xml-site CVS module is about to be migrated to SVN shortly. This has
> some effects on website deployment for websites under
> http://xml.apache.org. Currently, all the generated websites are
> uploaded under the targets directory in the xml-site repository and
> updated on cvs.apache.org using a CVS update.
>
> I strongly suggest to the Xerces and Xalan projects to deploy their
> subproject websites under their subdomain and instead add ".htaccess"
> files under xml.apache.org, like the other TLP-promoted projects have
> done, to redirect visitors to the new location. Examples of .htaccess
> files can be found for FOP, Batik, Cocoon, Forrest etc. FOP's .htaccess
> file looks like this:
>
> RedirectPermanent /fop http://xmlgraphics.apache.org/fop
>
> Using Forrest 0.7 to create the xml.apache.org site and having had good
> experiences for the XML Graphics and FOP sites, I'm going to change the
> xml.apache.org deployment to use (local) ForrestBot. The generated site
> will not be committed to the SVN repository anymore, but directly
> uploaded using SCP to cvs.apache.org:/www/xml.apache.org. If someone
> doesn't agree with that, please tell me. The other subproject sites can
> still be uploaded to the targets directory (only now through SVN which
> will take some manual work on minotaur).
>
> As soon as the SVN migration is completed I'm going to:
> - update the xml.apache.org site
> - remove the obsolete FOP website from the targets directory.
> - remove the obsolete SOAP website (now found here: http://ws.apache.org/soap/)
> - remove the obsolete XMLBeans website (now found here: http://xmlbeans.apache.org/)
> - document the new deployment process
> - help anyone who gets stuck
>
> I won't touch the other XML subproject sites unless asked to.
>
> The xml.apache.org site will be located here after the migration:
> https://svn.apache.org/repos/asf/xml/site/
>
> Check out using: svn co https://svn.apache.org/repos/asf/xml/site/
>
> Jeremias Maerki
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org