Re: [VOTE] [email] promote RC4 to 1.0 status
On Wed, 2005-06-22 at 22:22 +1000, Dion Gillard wrote: What usually goes in that for 1.0? The changes from the most recent pre-1.0 release (ie distribution available via the official downloads page). Email, of course, has never made a release of any sort. However I would still document any recent changes; the change from Hashtable to Map would be one such item. And noting that this is the first release ever would also be nice. I can't think of much else. Just having the file there is good; otherwise people may wonder where it is. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
On Thu, 2005-06-23 at 18:18 +1200, Simon Kitching wrote: On Wed, 2005-06-22 at 22:22 +1000, Dion Gillard wrote: What usually goes in that for 1.0? The changes from the most recent pre-1.0 release (ie distribution available via the official downloads page). Email, of course, has never made a release of any sort. However I would still document any recent changes; the change from Hashtable to Map would be one such item. And noting that this is the first release ever would also be nice. I can't think of much else. Just having the file there is good; otherwise people may wonder where it is. +1 it's also a good idea to include a brief summary of the aims of component and an overview of it's current progress. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
[AARGH - I hate top-posting!!] It certainly seems like email is generally ready for release. I think one more RC and a new VOTE thread would be a good idea, as the vote thread from december last year really can't be continued now :-). Besides there are a few minor things that need fixing: === website * navigation bar contains CVS entry (see xdocs/navigation.xml) * welcome page: * site welcome page refers to CVS * build -- built * in the examples page, exmaples -- examples * I recommend disabling the following maven reports: * changelog * developer activity * file activity These reports are of questionable use. And all date-based selection is stuffed in the apache svn repository anyway, due to cvs imports, so the reports can contain incorrect data. === code * Why does method Email.setHeaders take a Hashtable parameter? If this is an attempt to get the Email class to support JVM1.1 it won't work because this class also uses interface List. I would definitely prefer to see this method take a Map. * Shouldn't MultiPartEmail.addPart return a MultiPartEmail object? * One of the MultiPartEmail.addPart methods is missing javadoc. === downloads * the project.properties file has no maven.compile.target entry so what JVMs are supported will depend on what JVM was used to build the release. What exactly is the minimum JVM supported? Whatever it is, I would recommend adding maven.compile.target (and maven.compile.source) to the project.properties file *and* building the release with that JVM too. * There is no RELEASE-NOTES.txt file. === other I also see that Eric Pugh created a tags/EMAIL_1_0 tag with message Release 1.0 based on voted 1.0 RC4 but I think this should be deleted. Regards, Simon On Wed, 2005-06-22 at 09:41 +1000, Dion Gillard wrote: From what I can tell, the distributions below needed to be signed differently and more votes are still needed. I'm +1 on the release, but believe we need to repackage for the release. Anyone else care to vote or have opinions about the distribution? On 3/12/05, Eric Pugh [EMAIL PROTECTED] wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
On 6/22/05, Simon Kitching [EMAIL PROTECTED] wrote: [AARGH - I hate top-posting!!] It certainly seems like email is generally ready for release. I think one more RC and a new VOTE thread would be a good idea, as the vote thread from december last year really can't be continued now :-). Besides there are a few minor things that need fixing: === website * navigation bar contains CVS entry (see xdocs/navigation.xml) * welcome page: * site welcome page refers to CVS * build -- built * in the examples page, exmaples -- examples * I recommend disabling the following maven reports: * changelog * developer activity * file activity These reports are of questionable use. And all date-based selection is stuffed in the apache svn repository anyway, due to cvs imports, so the reports can contain incorrect data. === code * Why does method Email.setHeaders take a Hashtable parameter? If this is an attempt to get the Email class to support JVM1.1 it won't work because this class also uses interface List. I would definitely prefer to see this method take a Map. * Shouldn't MultiPartEmail.addPart return a MultiPartEmail object? * One of the MultiPartEmail.addPart methods is missing javadoc. === downloads * the project.properties file has no maven.compile.target entry so what JVMs are supported will depend on what JVM was used to build the release. What exactly is the minimum JVM supported? Whatever it is, I would recommend adding maven.compile.target (and maven.compile.source) to the project.properties file *and* building the release with that JVM too. All sound good. * There is no RELEASE-NOTES.txt file. What usually goes in that for 1.0? === other I also see that Eric Pugh created a tags/EMAIL_1_0 tag with message Release 1.0 based on voted 1.0 RC4 but I think this should be deleted. +1. -- http://www.multitask.com.au/people/dion/ You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live. - George Bernard Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
On 6/22/05, Simon Kitching [EMAIL PROTECTED] wrote: [AARGH - I hate top-posting!!] It certainly seems like email is generally ready for release. I think one more RC and a new VOTE thread would be a good idea, as the vote thread from december last year really can't be continued now :-). Besides there are a few minor things that need fixing: === website * navigation bar contains CVS entry (see xdocs/navigation.xml) Fixed. * welcome page: * site welcome page refers to CVS * build -- built Fixed. * in the examples page, exmaples -- examples Fixed. * I recommend disabling the following maven reports: * changelog * developer activity * file activity Agreed, and done. These reports are of questionable use. And all date-based selection is stuffed in the apache svn repository anyway, due to cvs imports, so the reports can contain incorrect data. === code * Why does method Email.setHeaders take a Hashtable parameter? If this is an attempt to get the Email class to support JVM1.1 it won't work because this class also uses interface List. I would definitely prefer to see this method take a Map. I believe there are some bugzilla entries to address this and the javadoc, I'll chase them up. * Shouldn't MultiPartEmail.addPart return a MultiPartEmail object? * One of the MultiPartEmail.addPart methods is missing javadoc. On looking at them again, I'd say yes. This shouldn't break any code based on the previous RCs. === downloads * the project.properties file has no maven.compile.target entry so what JVMs are supported will depend on what JVM was used to build the release. What exactly is the minimum JVM supported? Whatever it is, I would recommend adding maven.compile.target (and maven.compile.source) to the project.properties file *and* building the release with that JVM too. * There is no RELEASE-NOTES.txt file. === other I also see that Eric Pugh created a tags/EMAIL_1_0 tag with message Release 1.0 based on voted 1.0 RC4 but I think this should be deleted. Regards, Simon On Wed, 2005-06-22 at 09:41 +1000, Dion Gillard wrote: From what I can tell, the distributions below needed to be signed differently and more votes are still needed. I'm +1 on the release, but believe we need to repackage for the release. Anyone else care to vote or have opinions about the distribution? On 3/12/05, Eric Pugh [EMAIL PROTECTED] wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live. - George Bernard Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
On 6/22/05, Dion Gillard [EMAIL PROTECTED] wrote: On 6/22/05, Simon Kitching [EMAIL PROTECTED] wrote: [snip] === code * Why does method Email.setHeaders take a Hashtable parameter? If this is an attempt to get the Email class to support JVM1.1 it won't work because this class also uses interface List. I would definitely prefer to see this method take a Map. I believe there are some bugzilla entries to address this and the javadoc, I'll chase them up. Done. * Shouldn't MultiPartEmail.addPart return a MultiPartEmail object? * One of the MultiPartEmail.addPart methods is missing javadoc. On looking at them again, I'd say yes. This shouldn't break any code based on the previous RCs. Done. -- http://www.multitask.com.au/people/dion/ You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live. - George Bernard Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
On Thu, 2005-06-23 at 00:04 +1200, Simon Kitching wrote: [AARGH - I hate top-posting!!] It certainly seems like email is generally ready for release. I think one more RC and a new VOTE thread would be a good idea, as the vote thread from december last year really can't be continued now :-). +1 sounds like a good plan - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
+1 Can everybody just vote? Or is this only for committers? Regards, Matthijs robert burrell donkin wrote: On Thu, 2005-06-23 at 00:04 +1200, Simon Kitching wrote: [AARGH - I hate top-posting!!] It certainly seems like email is generally ready for release. I think one more RC and a new VOTE thread would be a good idea, as the vote thread from december last year really can't be continued now :-). +1 sounds like a good plan - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
On Wed, 2005-06-22 at 23:32 +0200, Matthijs Wensveen wrote: +1 Can everybody just vote? Or is this only for committers? anyone can vote (indeed, everyone is encouraged to) but only some votes are binding (notably the votes of the committers). your vote is an expression of support (which will be noted) but will not be used to determine the official outcome. many people do something like: +1 (non binding) if you're interested in learning more, see http://www.apache.org and http://jakarta.apache.org. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
From what I can tell, the distributions below needed to be signed differently and more votes are still needed. I'm +1 on the release, but believe we need to repackage for the release. Anyone else care to vote or have opinions about the distribution? On 3/12/05, Eric Pugh [EMAIL PROTECTED] wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live. - George Bernard Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
I'm using the commons-email RC4 on a project I'm working on and I've no problems to report. It seems that this project is quite stable. I'm not sure if my vote counts for something but if it does I'm a +1. Ramiro Pereira de Magalhães Dion Gillard wrote: From what I can tell, the distributions below needed to be signed differently and more votes are still needed. I'm +1 on the release, but believe we need to repackage for the release. Anyone else care to vote or have opinions about the distribution? On 3/12/05, Eric Pugh [EMAIL PROTECTED] wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] [email] promote RC4 to 1.0 status
Ugh. Cygwin. Fast way to frustration on windows.. Actually, I just got my new powerbook, so theoretically I can run MacPGP from http://macgpg.sf.net and do it. However, when I generate a new keypair, that means that I'll either have two keypairs, or I just don't use the first one anymore? I haven't signed anything else with it, and haven't cross signed it at all, so theorectically moving to a new keypair is fine, correct? Eric -Original Message- From: Phil Steitz [mailto:[EMAIL PROTECTED] Sent: Monday, March 14, 2005 6:51 PM To: Jakarta Commons Developers List Subject: Re: [VOTE] [email] promote RC4 to 1.0 status The gpg docs are here http://www.gnupg.org/gph/en/manual.html and yes, you need to generate a keypair first before trying to sign something. I don't know if it is ok to gen and store keys on apache boxes, though. Anyone know? If you can get Cygwin or something equivalent that lets you run gpg and shell scripts locally, you can use the scripts that I added to /committers/releases to create and verify the sigs once you have created the keypair using gpg --gen-key hth, Phil On Mon, 14 Mar 2005 09:56:17 -, Eric Pugh [EMAIL PROTECTED] wrote: I was taking a swing at ascii armour'ing the signatures, and have a couple questions. Following the directions in http://wiki.apache.org/jakarta-commons/SigningReleases, there is a section about using gpg. I logged onto my Apache account, and tried to do the command: gpg --armor --export 'your name' However, nothing gets produced. What I am wondering is if I need to somehow install my key? I followed the PGPMail directions, so my private key is on my windows laptop. Do I need to create using gpg my main key instead? There are some tantalizing mentions in PGPMail's documentation about ascii armouring, but no details on how to do it, just that it exists. Eric -Original Message- From: robert burrell donkin [mailto:[EMAIL PROTECTED] Sent: Friday, March 11, 2005 9:01 PM To: Jakarta Commons Developers List Subject: Re: [VOTE] [email] promote RC4 to 1.0 status hi eric could you ascii armour the signatures? (it's not essential but it makes them a lot nicer to read and download) - robert On Fri, 2005-03-11 at 20:30, Eric Pugh wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] [email] promote RC4 to 1.0 status
I was taking a swing at ascii armour'ing the signatures, and have a couple questions. Following the directions in http://wiki.apache.org/jakarta-commons/SigningReleases, there is a section about using gpg. I logged onto my Apache account, and tried to do the command: gpg --armor --export 'your name' However, nothing gets produced. What I am wondering is if I need to somehow install my key? I followed the PGPMail directions, so my private key is on my windows laptop. Do I need to create using gpg my main key instead? There are some tantalizing mentions in PGPMail's documentation about ascii armouring, but no details on how to do it, just that it exists. Eric -Original Message- From: robert burrell donkin [mailto:[EMAIL PROTECTED] Sent: Friday, March 11, 2005 9:01 PM To: Jakarta Commons Developers List Subject: Re: [VOTE] [email] promote RC4 to 1.0 status hi eric could you ascii armour the signatures? (it's not essential but it makes them a lot nicer to read and download) - robert On Fri, 2005-03-11 at 20:30, Eric Pugh wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] [email] promote RC4 to 1.0 status
hi eric i don't know of a way to convert a binary to an ascii armored sign. so it's best to try signing again using your laptop. (it's important not to use any ASF server for signing for security reasons). i've never used PGPMail but i wonder (after looking at the wiki) whether it's the 'text output' option that needs to be checked. you'll be able to tell quite easily if it's ascii armoured since they'll be a header and a footer text explaining. the body will be a string of alphanumerics with no odd characters. - robert On Mon, 2005-03-14 at 09:56 +, Eric Pugh wrote: I was taking a swing at ascii armour'ing the signatures, and have a couple questions. Following the directions in http://wiki.apache.org/jakarta-commons/SigningReleases, there is a section about using gpg. I logged onto my Apache account, and tried to do the command: gpg --armor --export 'your name' However, nothing gets produced. What I am wondering is if I need to somehow install my key? I followed the PGPMail directions, so my private key is on my windows laptop. Do I need to create using gpg my main key instead? There are some tantalizing mentions in PGPMail's documentation about ascii armouring, but no details on how to do it, just that it exists. Eric -Original Message- From: robert burrell donkin [mailto:[EMAIL PROTECTED] Sent: Friday, March 11, 2005 9:01 PM To: Jakarta Commons Developers List Subject: Re: [VOTE] [email] promote RC4 to 1.0 status hi eric could you ascii armour the signatures? (it's not essential but it makes them a lot nicer to read and download) - robert On Fri, 2005-03-11 at 20:30, Eric Pugh wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- robert burrell donkin [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
The gpg docs are here http://www.gnupg.org/gph/en/manual.html and yes, you need to generate a keypair first before trying to sign something. I don't know if it is ok to gen and store keys on apache boxes, though. Anyone know? If you can get Cygwin or something equivalent that lets you run gpg and shell scripts locally, you can use the scripts that I added to /committers/releases to create and verify the sigs once you have created the keypair using gpg --gen-key hth, Phil On Mon, 14 Mar 2005 09:56:17 -, Eric Pugh [EMAIL PROTECTED] wrote: I was taking a swing at ascii armour'ing the signatures, and have a couple questions. Following the directions in http://wiki.apache.org/jakarta-commons/SigningReleases, there is a section about using gpg. I logged onto my Apache account, and tried to do the command: gpg --armor --export 'your name' However, nothing gets produced. What I am wondering is if I need to somehow install my key? I followed the PGPMail directions, so my private key is on my windows laptop. Do I need to create using gpg my main key instead? There are some tantalizing mentions in PGPMail's documentation about ascii armouring, but no details on how to do it, just that it exists. Eric -Original Message- From: robert burrell donkin [mailto:[EMAIL PROTECTED] Sent: Friday, March 11, 2005 9:01 PM To: Jakarta Commons Developers List Subject: Re: [VOTE] [email] promote RC4 to 1.0 status hi eric could you ascii armour the signatures? (it's not essential but it makes them a lot nicer to read and download) - robert On Fri, 2005-03-11 at 20:30, Eric Pugh wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
-8- [X] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 Thanks Eric! Eric Pugh wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Weßendorf Aechterhoek 18 DE-48282 Emsdetten Germany phone: +49-2572-9170275 cell phone: +49-179-1118979 email: matzew AT apache DOT org url: http://www.wessendorf.net callto://mwessendorf (Skype) icq: 47016183 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] [email] promote RC4 to 1.0 status
Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [email] promote RC4 to 1.0 status
hi eric could you ascii armour the signatures? (it's not essential but it makes them a lot nicer to read and download) - robert On Fri, 2005-03-11 at 20:30, Eric Pugh wrote: Hi all, A couple of packaging issues were discovered in Email 1.0 RC3. I was encouraged to fix them and then call for a fresh vote, so I appreciate the understanding of the community that the (now) 4 release candidates it's taken to get email to 1.0. My first time signing a project. The release candidate is available at http://www.apache.org/~epugh/email/distributions/ and is just RC3 with some packaging tweaks, not Java code changes. The documentation is available at http://www.apache.org/~epugh/email/docs This is a full release vote (and so three +1's are required). please check the release before voting +1. i will not tally the votes before 2300 hours GMT on Tuesday 15th of March. here's my +1 - Eric -8- [ ] +1 Promote RC4 to commons-email-1.0 [ ] +0 In favour of this release [ ] -0 Against this release [ ] -1 Do not release RC4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
