[Releasing] archive file naming with -rc version suffix

[Thiago Macieira]

On quarta-feira, 30 de janeiro de 2013 10.43.12, Mark Brand wrote:
> I understand the argument. However, it cannot be said ahead of time that 
> any RC will be the final release. If it isn't, then there will be failed 
> RC archives around with the same name as the final release, which is 
> likely to cause confusion. The name collision makes it impossible to 
> keep the RCs and final release in the same directory. Finally, it's 
> inconvenient for scripted build, packaging, and testing, say, for distros.

If the file name and extracted dir name are exactly the same as in the final 
release, how is it more difficult for scripted building? You don't need to 
change anything from one RC to the next, just download the new files.

> It might be too late to fix (from my perspective) the RC naming 
> convention for 5.0.1, but I hope it will be seriously considered when it 
> next becomes possible.

We need the arguments on why that is necessary. It adds to our work and 
necessarily postpones any release by 24 hours, with a possibility of failure 
in the rebuild process.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20130130/7657c6da/attachment.sig>