Re: [Boost-bugs] [Boost C++ Libraries] #2204: Crucial information missing from site update instructions

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2204: Crucial information missing from site update instructions
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-09-11 03:02:11

#2204: Crucial information missing from site update instructions
---------------------------+------------------------------------------------
  Reporter:  dave          |       Owner:  grafik     
      Type:  Bugs          |      Status:  new        
 Milestone:  Boost 1.37.0  |   Component:  website    
   Version:  Boost 1.36.0  |    Severity:  Showstopper
Resolution:                |    Keywords:             
---------------------------+------------------------------------------------

Comment(by grafik):

 Replying to [comment:4 dave]:
 > Replying to [comment:3 grafik]:
 > > But whatever, not really important... If you want to update the Boost
 release documentation that appear on the web site you need to:
 > >
 > >   1. Create a Boost release ZIP archive.
 >
 > Can I do that by unzipping the latest release, editing it, and re-
 zipping?
 > What do I need to call this file?

 Yes, taking the ZIP from the SourceForge downloads, unzipping, replacing
 with new files, and re-zipping is what you need to do. Ideally the name of
 the file needs to stay the same. As otherwise the 'live' part of the site
 needs to be adjusted to point  to the different name. But to keep the
 historical ZIPs around using a different name to indicate it's not the
 original one is fine. We can just put an appropriate symlink.

 > >   2. Upload it to the web server to the directory
 "/home/grafik/www.boost.org/archives/live".
 >
 > Hum. Do I have write access to that directory, and if so, by what means?

 I don't think you have access as there are a limited number of Boost user
 accounts. But I could give you access to my account if you give me an SSH
 public key. I suggested in the list that it would be best if Doug set up a
 general 'boost' account instead of using 'personal' accounts, so I'll
 raise that again.

 > >   3. Update the SVN repo "/website/public_html/beta" and
 "/website/public_html/live" files as described in the web site update
 instructions to point to the new release.
 >
 > OK... I still think you need to update the "updating the website"
 instructions to describe this procedure.

 Yes, will do, eventually. But be warned I'm having less and less time to
 donate to Boost recently, so it might take a while.

 > > So I ask the same question I asked on my first reply, but hopefully in
 better words :-) Do we want the GSG to be treated differently than the
 other release documentation? I.e. make it so that we show a more recent
 version on the web site than the ones on the releases by default?
 >
 > No and yes.  That is to say, at a library author's discretion, ''any''
 part of the release documentation ought to be updatable on the website.
 Perhaps I want to alert people that there's an important patch available.
 No, changing the live website won't reach everyone, but it's better than
 nothing.

 OK, got it. For now replacing the ZIP will have to do. But I think in the
 long run setting up a patch tree to do selected file replacements is best.
 I'll add a ticket for this.

-- 
Ticket URL: <http://svn.boost.org/trac/boost/ticket/2204#comment:7>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.