Am 08/14/2013 10:24 PM, schrieb Marcus (OOo):
Am 08/14/2013 10:05 PM, schrieb Hagar Delest:
Le 14/08/2013 21:39, Rob Weir a écrit :
Maybe we need to call an earlier build the "RC" so it will get more
attention? We had a complete test build that we were testing for
over a month. But maybe it is ignored unless we call it an "RC"? In
other words, there were many opportunities for users to help try 4.0
before it was released, but maybe there opportunities were not well
known.
I think that it was too difficult to get to the dev versions and it was
too much complicated. There was no clear link to download a dev version
(I had to rely on the url in the messages from the dev list).
This was intended.
We hadn't published the dev builds via Apache or SF mirrors but only on
2 people accounts. Apache policy says it's not allowed to publish them
for a wider audience to save the servers from a high traffic load. It's
the job of the mirrors to handle this.
What I see (from a standard user point of view) for a RC:
- When a dev version is almost done, rename it RC and make it known
(blog and we would relay the announcement in the forums of course)
- Have a link visible under the main download button of the download
Both can be done, depending where the install files are located.
page (perhaps a similar button as a dedicated entry)
- Make that RC installable in parallel with a stable version
- No file association allowed for that RC by design
IMHO the last both points doesn't apply to a RC [1] as it wouldn't be a
RC anymore. One of the RC attributes is to change it into the final
release with, e.g., just a file name change. But this has to be done
without any code changes. Otherwise you have to change code parts, build
again, test again, ... ;-)
But a Beta release could go this separated way.
The wiki page for the dev builds were too complicated and sounded to
much beta to make the users confident in using them (when they managed
to get on that page!).
Marcus
Sorry, forgot the link:
[1]
http://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
