[mentors] question about release process

[Josh Thompson <jo...@ncsu.edu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So, the vote on the IPMC list passed.  However, due to a question on the vcl-
user list, I discovered a very small bug, but one that would be nice to have 
fixed in the release.  The problem is in a javascript file.  There are two 
arrays that have a comma after the final element.  Firefox is okay with that; 
IE gives a parse error.  The result is that no graphs show up under IE on the 
statistics page.  The fix is to remove the 2 commas.  I don't feel like 
removing them necessitates a full cycle of cutting another RC, having a vote 
on our list, and then having a vote on the IPMC list.  I'd like fix it in 
trunk, in the final release tag, and in the release archive, but I don't know 
if that's allowed without doing the full cycle again.

Do we need to go through the whole process again, or can I just fix it and cut 
the release?

Thanks,
Josh
- -- 
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEARECAAYFAk2TXpIACgkQV/LQcNdtPQOYmgCfRtejhdOGJ0v9kCsr7g4ZmcrZ
rukAnivFSxYOtzlj/1JeH2WCliPFzdEI
=1AY6
-----END PGP SIGNATURE-----

Re: [mentors] question about release process

["Alan D. Cabrera" <li...@toolazydogs.com>]

On Mar 30, 2011, at 9:47 AM, Josh Thompson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> So, the vote on the IPMC list passed.  However, due to a question on the vcl-
> user list, I discovered a very small bug, but one that would be nice to have 
> fixed in the release.  The problem is in a javascript file.  There are two 
> arrays that have a comma after the final element.  Firefox is okay with that; 
> IE gives a parse error.  The result is that no graphs show up under IE on the 
> statistics page.  The fix is to remove the 2 commas.  I don't feel like 
> removing them necessitates a full cycle of cutting another RC, having a vote 
> on our list, and then having a vote on the IPMC list.  I'd like fix it in 
> trunk, in the final release tag, and in the release archive, but I don't know 
> if that's allowed without doing the full cycle again.
> 
> Do we need to go through the whole process again, or can I just fix it and cut 
> the release?

Yes, any change requires a new vote.

This is because of the changes in signatures etc.


Regards,
Alan