2.0 release plans

[Josh Sled]

On Thu, 2006-07-06 at 20:36 -0600, Chris Lyttle wrote:
> > - Bug <http://bugzilla.gnome.org/show_bug.cgi?id=120302> in particular
> > should be addressed.  Chris, perhaps after you create a key, you can
> > send it around to the core devs?  The public key should go up on
> > www.gnucash.org, of course, and the keyservers.  It'd be good to get
> > some signatures on that key, as well
> OK thinking a little how this would work politically, I think we should 
> have a private key that each of the core devs has a copy of. This could 
> be used for sending semi-confidential messages to the dev's and signing 
> releases. This kinda breaks a little the idea behind 'private' keys, but 
> we either do this or just have a key that is 'shared', ie broken up so 
> that you need 2 people to decrypt a message/file and the release person 
> keep the 'whole' key to sign releases.

Chris, I went to put www.gnucash.org changes in place to publicize the
public key, but then I noticed that it's your pubkey rather than a
project-specific "gnucash" key. 

Can you please replace it with a proper pubkey, and update the release
sigs?  Also, as discussed, you should send the public and private parts
around to the core devs.

Thanks...
-- 
...jsled
http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo ${a}@${b}`
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20060712/bc71fe93/attachment.bin