Get the Manual WAS Re: Release Often!

4 messages

Get the Manual WAS Re: Release Often!

Reply Threaded

| From "Ed Musgrove" <[hidden email]>
| Fri, 30 Oct 2009 13:56:47 -0700
| Subject: [Audacity-devel] Release Often!
> I would be happy to pitch in with the Manual work (I seem to have
> accidentally start to do so yesterday). I have not looked at it at all (it
> does not build locally on Vista or 7) until last night when I was looking at
> P2s to test.

Can you explain what does not build please, Ed? Are you following
"3. Get the Manual" from win/release.txt?

"Make sure you have python installed and on your path.
Delete audacity\help\manual if it exists.
Go to audacity\scripts\mw2html_audacity.
Run wiki2htm and wait for it to complete.
The manual should have been built in audacity\help\manual."

Gale

>
> > -----Original Message-----
> > From: Gale Andrews [mailto:[hidden email]]
> > Sent: Friday, October 30, 2009 12:34 PM
> > To: [hidden email]
> > Subject: Re: [Audacity-devel] Release Often!
> >
> >
> > | From James Crook <[hidden email]>
> > | Fri, 30 Oct 2009 13:58:08 +0000
> > | Subject: [Audacity-devel] Release Often!
> > > ... We are in no shape to announce a stable release for Windows 7, so
> > > release notes and announcement e-mails need to make it very clear that
> > > whatever we release is beta quality with regard to Windows 7, whatever
> > > we say about stability on other platforms.
> >
> > It's essentially Beta quality with regard to Vista, too (all but one of
> the
> > Windows 7 P2s applies to Vista). The only argument against that statement
> is
> > that behaviour on Vista is somewhat more of a known quantity because we
> > have more reports of it. I have Windows 7 now but of course lack time to
> test
> > it much.
> >
> > > I like your wild optimism that we can do it by 1st Dec.
> >
> > As I said before, everyone would need to chip in to get the Manual
> finished
> > (the shorter the deadline, the more that's true). For the Manual to be
> > finished without others of us contributing to it significantly, I'd say
> we'd be
> > looking at mid January 2010. Bill and John have done a lot and I've
> started
> > reviewing finished pages and marking them (IMO) as release-ready. Others
> > would have to share that task, and the missing/ hopelessly outdated pages
> > need to be written too, unless "release and be damned" applies to the
> > Manual
> > as well. In that case it needs a Beta health warning too.
> >
> >
> > > For me the really important thing is what we do after we have a stable
> > > release off CVS head. The 'release often' is even more important once
> > > we have achieved that. New P1's and P2's will either be regressions
> > > (need to be vigilant and fix them as soon as we are aware) or will be
> > > bugs in new functionality (should be releasable by turning off that
> > > feature). Maintaining a separate stable branch costs a lot of energy,
> > > and we know from experience that good new things do not get ported to
> > > the stable branch. So I would like us to be aiming to release often,
> > > i.e release a stable release often, once we have 2.0.
> >
> > I think I'd seen suggestions before of a Stable every year and a Beta
> every
> > two or three months. Is that still thought about right?
> >
> >
> >
> >
> > Gale
> >
> >
> > > Martyn Shaw wrote:
> > > > Hi
> > > >
> > > > I went to the GSoC Mentors Summit with one question on my mind:
> > "Why
> > > > don't we have a 2.0 release yet?". So I asked people from many
> > > > (about
> > > > 10) other open-source organisations about releasing code. Every
> > > > one said 'release often'. Many said 'just set a date and then do it
> > > > on that date whatever'.
> > > >
> > > > So I'm proposing a new date for 2.0, since the others have gone bye.
> > > > 1st December.
> > > >
> > > > I'll try and do a Windows release then, others can do the other
> > > > releases if they like, I can't.
> > > >
> > > > TTFN
> > > > Martyn
> > >
> > >
> > > ----------------------------------------------------------------------
> > > -------- Come build with us! The BlackBerry(R) Developer Conference in
> > > SF, CA is the only developer event you need to attend this year.
> > > Jumpstart your developing skills, take BlackBerry mobile applications
> > > to market and stay ahead of the curve. Join us from November 9 - 12,
> > > 2009. Register now!
> > > http://p.sf.net/sfu/devconference
> > > _______________________________________________
> > > audacity-devel mailing list
> > > [hidden email]
> > > https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >
> >
> >
> >
> ----------------------------------------------------------------------------
> --
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA is
> the
> > only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > audacity-devel mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> audacity-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Ed Musgrove-2

Re: Get the Manual WAS Re: Release Often!

Reply Threaded

> -----Original Message-----
> From: Gale Andrews [mailto:[hidden email]]
> Sent: Friday, October 30, 2009 9:57 PM
> To: [hidden email]
> Subject: [Audacity-devel] Get the Manual WAS Re: Release Often!
>
>
> | From "Ed Musgrove" <[hidden email]> Fri, 30 Oct 2009
> | 13:56:47 -0700
> | Subject: [Audacity-devel] Release Often!
> > I would be happy to pitch in with the Manual work (I seem to have
> > accidentally start to do so yesterday). I have not looked at it at all
> > (it does not build locally on Vista or 7) until last night when I was
> > looking at P2s to test.
>
> Can you explain what does not build please, Ed? Are you following "3. Get
> the Manual" from win/release.txt?
>
> "Make sure you have python installed and on your path.

[ Ed-- ]
Installed and in the path; working for other apps and from the command line.

> Delete audacity\help\manual if it exists.
[ Ed-- ]
It is an empty folder...deleted it.

> Go to audacity\scripts\mw2html_audacity.
> Run wiki2htm and wait for it to complete.
[ Ed-- ]
There are two files wiki2htm.bat and wiki2htm.sh.

The .sh file just gives me "Windows can't open this file...needs to know
what program you want to use to open it..." then offers a choice of "Search
the web..." or "Select a program from a list of installed programs".
Searching the web finds nothing.

The .bat file runs but only creates an empty audacity\help\manual
directory.

My (wild) guess is that this is a security issue. I doubt that Python has
scripting permission to access the internet.

So, I created a manual directory in audacity\scripts\mw2html_audacity (to
avoid all the redirection) and ran:
python mw2html.py "http://audacityteam.org/manual" "manual" -s
directly with no string replacement. This sort of worked but most of the
expected files did not retrieve--I only got the "index" page and no linked
pages:

D:\audio\Audacity\currentCVS\audacity\scripts\mw2html_audacity>python
mw2html.py "http://audacityteam.org/manual" "manual" -s
connection established to: audacityteam.org
Status 302 Found accessing /manual
connection to audacityteam.org closed.
connection to manual.audacityteam.org opened.
Status 301 Moved Permanently accessing
ERROR ResponseNotReady while retrieving
http://manual.audacityteam.org/index.php?title=Main_Page
eventually this error might be recovered. let's try again.
reconnecting...
Status 200 OK accessing /index.php?title=Main_Page
error recovered
connection to manual.audacityteam.org closed.
connection to audacityteam.org opened.
Status 200 OK accessing /favicon.ico
Status 404 Not Found accessing /skins/common/shared.css?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/common/commonPrint.css?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/common/commonPrint.css?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/monobook/main.css?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/monobook/main.css?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/monobook/IE50Fixes.css?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/monobook/IE50Fixes.css?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/monobook/IE55Fixes.css?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/monobook/IE55Fixes.css?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/monobook/IE60Fixes.css?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/monobook/IE60Fixes.css?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/monobook/IE70Fixes.css?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/monobook/IE70Fixes.css?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/common/IEFixes.js?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/common/IEFixes.js?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/common/wikibits.js?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/common/wikibits.js?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/skins/common/ajax.js?207
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /skins/common/ajax.js?207
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/images/e/e1/Audacity-logo-r-full-whitebg.jpg
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /images/e/e1/Audacity-logo-r-full-whitebg.jpg
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/images/b/b7/Index_reference.png
eventually this error might be recovered. let's try again.
reconnecting...
Status 404 Not Found accessing /images/b/b7/Index_reference.png
it's not possible to recover this error.
ERROR ResponseNotReady while retrieving
http://audacityteam.org/images/NEW_AudacityTransMediaWikiMANUAL.png
eventually this error might be recovered. let's try again.
reconnecting...
Status 200 OK accessing /images/NEW_AudacityTransMediaWikiMANUAL.png
error recovered
Status 404 Not Found accessing
/skins/common/images/poweredby_mediawiki_88x31.png
it's not possible to recover this error.
connection to audacityteam.org closed.
connection to www.audacityteam.org opened.
Status 200 OK accessing /images/cc3_88x31.png
connection to www.audacityteam.org closed.
4 files saved
32 httplib requests done
13 errors not recovered

D:\audio\Audacity\currentCVS\audacity\scripts\mw2html_audacity>

I will reference the online version when I make any suggestions for
improvement.

--Ed

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Ed Musgrove-2

Re: Get the Manual WAS Re: Release Often!

Reply Threaded

This does allow the help project to proceed successfully during the "make
solution" process. Before it reported a non-fatal error.

Right after I did the below mentioned retrieve I tried to grab the CVS HEAD
and had to try a couple of times as the online location was listed as "does
not exist". It might all have been an internet glitch--will try the retrieve
again later today.

--Ed

> So, I created a manual directory in audacity\scripts\mw2html_audacity
(to
> avoid all the redirection) and ran:
> python mw2html.py "http://audacityteam.org/manual" "manual" -s directly
> with no string replacement. This sort of worked but most of the expected
> files did not retrieve--I only got the "index" page and no linked
> pages:

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Martyn Shaw-2

Re: Get the Manual WAS Re: Release Often!

Reply Threaded

Hmm. Run for me here, with the odd connectivity issue (using
wiki2htm.bat). Don't run it too often though, it must load our server!

Martyn

Ed Musgrove wrote:

> This does allow the help project to proceed successfully during the "make
> solution" process. Before it reported a non-fatal error.
>
> Right after I did the below mentioned retrieve I tried to grab the CVS HEAD
> and had to try a couple of times as the online location was listed as "does
> not exist". It might all have been an internet glitch--will try the retrieve
> again later today.
>
> --Ed
>
>
>> So, I created a manual directory in audacity\scripts\mw2html_audacity
> (to
>> avoid all the redirection) and ran:
>> python mw2html.py "http://audacityteam.org/manual" "manual" -s directly
>> with no string replacement. This sort of worked but most of the expected
>> files did not retrieve--I only got the "index" page and no linked
>> pages:
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> audacity-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>