From: Philippe M. <mak...@fi...> - 2011-06-05 09:48:43
|
Hi, First thanks to all for this good work I have now two questions : - How can we publish snapshots builds ? - On the old web site, developers can have a "rabbit hole" so they can publish drafts or others thinks they want (for example I publish on my rabbit hole results of QA test run) how can we have the same possibility ? I mean just a place to put files via ftp or ssh ? May be one solution is to keep the old web server for that and snapshots builds ? with just a front page with links to svn, snapshots, rabbit holes, main web site and give it a new name like dev.firebirdsql.org ? |
From: Helen B. <he...@ii...> - 2011-06-05 10:19:39
|
At 09:48 PM 5/06/2011, Philippe wrote: >Hi, > >First thanks to all for this good work > > >I have now two questions : > >- How can we publish snapshots builds ? >- On the old web site, developers can have a "rabbit hole" so they can >publish drafts or others thinks they want (for example I publish on my >rabbit hole results of QA test run) >how can we have the same possibility ? >I mean just a place to put files via ftp or ssh ? > >May be one solution is to keep the old web server for that and snapshots >builds ? >with just a front page with links to svn, snapshots, rabbit holes, main >web site > >and give it a new name like dev.firebirdsql.org ? FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date) is still accessible via http://web.firebirdsql.org. For the present at least it is the only place where people can find the full and correct links to all the lists, the download pages, the driver pages and the up-to-date FF membership and sponsorship details. I think Sergey needs to find a way to let visitors to the new site know that the old site is still available and has the up-to-date content. We have a 2.5 point release coming up, with no clarity about how the Download page will be available, either. Helen |
From: Alexey K. <ak...@ib...> - 2011-06-05 17:26:13
|
Helen, >FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date) is still accessible via http://web.firebirdsql.org. For the present at least it is the only >place where people can find the full and correct links to all the lists, the download pages, the driver pages and the up-to-date FF membership and sponsorship details. I think >Sergey needs to find a way to let visitors to the new site know that the old site is still available and has the up-to-date content. Please provide us with list of links to pages you refer as outdated. >We have a 2.5 point release coming up, with no clarity about how the Download page will be available, either. During migration Olga Popcova created all pages at Downloads, including recent 2.1.4 minor release. Send content to be updated to Olga with CC to me and everything will be done. Regards, Alexey Kovyazin > > > Helen > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is safe, > secure and there when you need it. Discover what all the cheering's about. > Get your free trial download today. > http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > Firebird-website mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-website > |
From: Philippe M. <mak...@fi...> - 2011-06-05 11:01:48
|
Helen Borrie [05/06/2011 12:19] : > FYI, the "old" website (actually, CURRENT, since the "new" one is two > months out of date) is still accessible via > http://web.firebirdsql.org. thanks Helen, for now it is enough for me > I think Sergey needs to find a > way to let visitors to the new site know that the old site is still > available and has the up-to-date content. yes and this way links to snapshots builds is solved no need to push builds on another place than web.firebirdsql.org (209.183.20.105) that the easiest way to solve http://tracker.firebirdsql.org/browse/WEB-71 and it is the best way to do it instead of http://www.firebirdsql.org/download/snapshot_builds/ just put http://web.firebirdsql.org/download/snapshot_builds/ |
From: marius a. p. <ma...@gm...> - 2011-06-05 11:29:25
|
On Sun, Jun 5, 2011 at 2:01 PM, Philippe Makowski <mak...@fi...> wrote: > Helen Borrie [05/06/2011 12:19] : >> FYI, the "old" website (actually, CURRENT, since the "new" one is two >> months out of date) is still accessible via >> http://web.firebirdsql.org. > thanks Helen, for now it is enough for me > >> I think Sergey needs to find a >> way to let visitors to the new site know that the old site is still >> available and has the up-to-date content. > yes and this way links to snapshots builds is solved > no need to push builds on another place than web.firebirdsql.org > (209.183.20.105) > > that the easiest way to solve > http://tracker.firebirdsql.org/browse/WEB-71 > and it is the best way to do it > instead of http://www.firebirdsql.org/download/snapshot_builds/ > just put http://web.firebirdsql.org/download/snapshot_builds/ I agree also the python documentation should be kept on old web server (i think it can be regenerated easily there) http://www.firebirdsql.org/devel/python/docs/3.3.0/tutorial.html should point to http://web.firebirdsql.org/devel/python/docs/3.3.0/tutorial.html |
From: Paul V. <pa...@vi...> - 2011-06-05 11:32:42
|
Helen wrote: > FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date) If that is the case, wasn't the DNS change a bit premature? Paul Vinkenoog |
From: marius a. p. <ma...@gm...> - 2011-06-05 11:40:06
|
On Sun, Jun 5, 2011 at 2:32 PM, Paul Vinkenoog <pa...@vi...> wrote: > Helen wrote: > >> FYI, the "old" website (actually, CURRENT, since the "new" one is two months out of date) > > If that is the case, wasn't the DNS change a bit premature? Well i guess it's better that it happened (sooner than later) and we have a lot of content to check , we all can submit bugs to the tracker and i see they are fixed as we speak. And i think we need access to the subsections as it was promised Also if the docs are wrong i think the links should pont to the right generated documents until they are fixed |
From: Paul V. <pa...@vi...> - 2011-06-05 12:20:21
|
Marius wrote: > And i think we need access to the subsections as it was promised > Also if the docs are wrong i think the links should pont to the right > generated documents until they are fixed That would work, were it not that the old docs contain links that are specific to the old site structure. Pointing to the old docs would ensure that the content is correct and consistent, but would break those links. Pointing to the newly-generated docs (as is done now) means the links are valid, but the content is not - at least in some essential manuals. So it looks like we weren't ready to move yet. But... we'll fix it. Paul Vinkenoog |