the progress with the release

About 13 hours to go until the announcement of the
code-freeze.

We are up to the section "Preparing the code
base"
http://forrest.apache.org/procedure
s/release/How_to_release.html#PrepCodeBase
Anyone can help with this phase.

Whatever is still left to do after our night, i will try to
pick up
tomorrow after the code-freeze. However i expect i will be
pretty
busy with the other stuff, so the review of plugins
descriptors
and deploying might not get done. Remember there were
differences
revealed when Ross started work on the automation of
plugins.xml
descriptors.

-David

David Crossley wrote:
> About 13 hours to go until the announcement of the
code-freeze.
> 
> We are up to the section "Preparing the code
base"
> http://forrest.apache.org/procedure
s/release/How_to_release.html#PrepCodeBase
> Anyone can help with this phase.
> 
> Whatever is still left to do after our night, i will
try to pick up
> tomorrow after the code-freeze. However i expect i will
be pretty
> busy with the other stuff, so the review of plugins
descriptors
> and deploying might not get done. Remember there were
differences
> revealed when Ross started work on the automation of
plugins.xml
> descriptors.

I'm about to start going through the plugins and deploy then
to ensure 
latest dev code is in the download location, although I'm on
child duty 
today so be prepared for sparodic work, I'll start at the
top of the 
list and work down so when you see a plugin deployed, that's
ow far I've 
got.

Note, a deploy is not the same as a release although
deployed plugins 
will always be used if no version number is supplied.

Ross

Phew. Done the "FOR-644 code-style cleanup for xml
files"
Amazing how many xml files that we have.

I did it section by section and tested on the way, e.g.
doing main/webapp/resources/stylesheets then rebuilding
our website, then checking with diff to see if there
were any differences. Similarly with a dispatcher-built
seed site. All seems well.

Sorry for the huge amount of diff email.

Now going on to do the final version number changes
and create the release candidate packages. That will
still take some time.

-David

If anyone is trying to follow along, i am up to the
early phases of
http://forrest.apache.org/procedures/
release/How_to_release.html#adjustDocs

Already found three extra steps. Scribbling on the
doc for next time.

-David

David Crossley wrote:
> If anyone is trying to follow along, i am up to the
> early phases of
> http://forrest.apache.org/procedures/
release/How_to_release.html#adjustDocs
> 
> Already found three extra steps. Scribbling on the
> doc for next time.

Woops, a bit of delay with more missing steps. Getting the
"Versioned docs" tab working is ticky. I need to
look
at the 0.7 release setup and see how we did it.

Anyway, dinner time now. Back soon.

-David

David Crossley wrote:
> 
> Woops, a bit of delay with more missing steps. Getting
the
> "Versioned docs" tab working is ticky. I need
to look
> at the 0.7 release setup and see how we did it.

That helped. Easy really.

Now on to the rest of the section:
"Building the release candidate packages".

-David

Some notes about the progress with the release.

The call for testing and subsequent voting
http://thread.gmane.org/gmane.text.xml.forrest.devel/2
4024

Less than five days remain.

We have one comment that it works. Thanks Paul.

This is the first release where we have not built
the Windows package using Windows. We think that the
line-endings for .bat files and the like are okay,
but cannot be sure.

So it is vital that someone using that operating system
reports success with RC1 release candidate package.

If not then we need to create another ASAP.
Saturday is the scheduled day for an RC2 if necessary,
However if we know that there are problems then
the sooner the better.

If there continues to be a lack of interest,
then the product is in danger of not being released.

Lack of interest indicates that there might not be
sufficient community base to support the product. 

People should each have their own guidelines for
testing and reviewing release candidates, and what
factors that they consider will impact their vote.
Mostly it is common-sense stuff, but if you need
help then see:
http://www.apache
.org/dev/#releases

-David

David Crossley wrote:
> So it is vital that someone using that operating
system
> reports success with RC1 release candidate package.

Don't worry David, I'm on it, but I'm taking my time to make
sure it 
gets my full focus. Don't expect a report from me until
towards the end 
of the test cycle as I'm grabbing half hour here and half
hour there.

For now, assume no news (from me) is good news.

So far so good. The dispatcher was failing, but I'm awaiting
a proper 
deploy of the plugins (I notice Thorsten fixed the site,
thanks).

Ross

Ross Gardler wrote:
> David Crossley wrote:
> >So it is vital that someone using that operating
system
> >reports success with RC1 release candidate
package.
> 
> Don't worry David, I'm on it, but I'm taking my time to
make sure it 
> gets my full focus. Don't expect a report from me until
towards the end 
> of the test cycle as I'm grabbing half hour here and
half hour there.
> 
> For now, assume no news (from me) is good news.

In general i do things the same way. Speak up
if there are issues, otherwise use the time to
do things.

In this situation we at least someone on plain Windows
to say "Hooray, it basically works, now i will get on
with more testing." Then the Release Manager is
relieved that the package is constructed properly.

> So far so good. ...



> ... The dispatcher was failing, but I'm awaiting a
proper 
> deploy of the plugins (I notice Thorsten fixed the
site, thanks).

Yep, i haven't bothered yet to test my dispatcher-based
sites because i knew it wasn't deployed.

-David

Keeping this "progress" thread happening ...

We fixed some quite serious problems with the
deployment of plugins. Thanks to those who helped
with the testing and fixing.

So far we do not need another release candidate.

People are still encouraged to test on sites that
have more complex needs.

If there are whiteboard plugins thyat you want
to be deployed up-to-date, then don't forget to ask.

-David