Hi Karl, Okey as I understand you ran
create_release_branch.py" 1.6 1.7 /my-disk/mcf-trunk and this resulted last three commits. Correct? I pretty much converted release.bat into release.sh. I see that release scripts don't have license headers. Is it ok? I just don't get why we need md5temp and sha1temp. What are those for loops? And temporary file tiny? I would simply do this: gpg --print-md MD5 apache-manifoldcf-%1-src.zip.asc > apache-manifoldcf-%1-src.zip.md5 gpg --print-md MD5 apache-manifoldcf-%1-src.tar.gz.asc > apache-manifoldcf-%1-src.tar.gz.md5 gpg --print-md MD5 apache-manifoldcf-%1-lib.zip.asc > apache-manifoldcf-%1-lib.zip.md5 gpg --print-md MD5 apache-manifoldcf-%1-lib.tar.gz.asc > apache-manifoldcf-%1-lib.tar.gz.md5 gpg --print-md MD5 apache-manifoldcf-%1-bin.zip.asc > apache-manifoldcf-%1-bin.zip.md5 gpg --print-md MD5 apache-manifoldcf-%1-bin.tar.gz.asc > apache-manifoldcf-%1-bin.tar.gz.md5 gpg --print-md SHA512 apache-manifoldcf-%1-src.zip.asc > apache-manifoldcf-%1-src.zip.sha gpg --print-md SHA512 apache-manifoldcf-%1-src.tar.gz.asc > apache-manifoldcf-%1-src.tar.gz.sha gpg --print-md SHA512 apache-manifoldcf-%1-lib.zip.asc > apache-manifoldcf-%1-lib.zip.sha gpg --print-md SHA512 apache-manifoldcf-%1-lib.tar.gz.asc > apache-manifoldcf-%1-lib.tar.gz.sha gpg --print-md SHA512 apache-manifoldcf-%1-bin.zip.asc > apache-manifoldcf-%1-bin.zip.sha gpg --print-md SHA512 apache-manifoldcf-%1-bin.tar.gz.asc > apache-manifoldcf-%1-bin.tar.gz.sha Wouldn't that work? Ahmet On Tuesday, April 15, 2014 1:58 AM, Karl Wright <[email protected]> wrote: I ran the script and confirmed that it hangs silently when it queries for a password. So that needs to be fixed. Meanwhile, there's a release-1.6-branch created for you to work with. Karl On Mon, Apr 14, 2014 at 6:48 PM, Karl Wright <[email protected]> wrote: I'm running it now; it is not terribly verbose, but you can see what it is doing by using "top" or the equivalent. > > >I can't figure out how to grant permissions to edit the wiki to anyone; I >suggest ask infra if they can point us the way. > >Karl > > > > > >On Mon, Apr 14, 2014 at 6:42 PM, Karl Wright <[email protected]> wrote: > >Hi Ahmet, >> >>A quick response to some of your questions: >> >>(1) I think it is possible that the scripts won't work if you don't have a >>stored password for svn, because they invoke svn copy (yes) but they do not >>permit it to ask for a password. >>(2) The parameters would be: 1.6 1.7 , as you guessed. >>(3) Getting permission to edit confluence may be a challenge; I will see if I >>have privs to grant you the ability to do it. >> >>I think it might be best for the moment if I ran the script to set up the >>release branch. Any objections? but I agree we should work on it to make it >>acceptable for Mac users. >> >>Karl >> >> >> >> >> >>On Mon, Apr 14, 2014 at 5:56 PM, Ahmet Arslan <[email protected]> wrote: >> >>Hi, >>> >>>Regarding create_release_branch.py and update_release_branch.py, >>> >>> >>>* do they "svn copy" operations too? >>>* where do I run them? >>>* what will be the parameters for this particular release? >>> >>>After I delete my ~subversion/auth, I tried following command but nothing >>>happened. >>> >>>python release-scripts/create_release_branch.py 1.6 1.7 >>> >>> >>>How can I verify these python scripts are working on mac os? >>> >>> >>> >>>Regarding gpg,(I am a new learner with this one), documentation >>>(http://www.apache.org/dev/openpgp.html#sha1) says we should avoid sha-1. I >>>don't fully digest release.bat but I see sha-1 in it. >>> >>> >>>By the way it seems that I cannot edit confluence, my user name is iorixxx . >>>There are two spam comments in >>>https://cwiki.apache.org/confluence/display/CONNECTORS/HowToBecomeACommitter >>>I want to delete them. >>> >>> >>>Thanks for guidance, >>>Ahmet >>> >>> >>> >>>On Thursday, April 10, 2014 12:44 PM, Karl Wright <[email protected]> wrote: >>>I just updated the release process document for MCF, because uploading to >>>people.apache.org has now changed to require a public/private key pair. So >>>you will need to generate that too, and make sure your >>>people.apache.orglogin supports login by private key. I've included >>> >>>the link in the wiki >>>page. >>> >>>Thanks, >>>Karl >>> >>> >>> >>> >>>On Tue, Apr 8, 2014 at 8:46 AM, Karl Wright <[email protected]> wrote: >>> >>>> Hi Ahmet, >>>> >>>> Thanks for volunteering! >>>> >>>> The release process is actually automated with scripts. The scripts, >>>> though, are in part Windows batch files. If you are releasing on Linux you >>>> will want to code the bash versions of these. >>>> >>>> Anyway, please read the following: >>>> >>>> https://cwiki.apache.org/confluence/display/CONNECTORS/Release+Process >>>> >>>> You will need various tools installed on your release system, AND you will >>>> need to have a signing key. Your public key will need to be added to the >>>> KEYS file included in the release as well as being registered. Please read >>>> this: >>>> >>>> http://www.apache.org/dev/release-signing.html >>>> >>>> Thanks, >>>> Karl >>>> >>>> >>>> >>>> >>>> On Tue, Apr 8, 2014 at 7:59 AM, Ahmet Arslan <[email protected]> wrote: >>>> >>>>> Hi Karl, >>>>> >>>>> I am volunteer to be release manager for 1.6 Release. >>>>> I assume http://www.apache.org/dev/release.html is the guide? >>>>> >>>>> Ahmet >>>>> >>>>> >>>>> >>>>> On Monday, April 7, 2014 3:23 PM, Karl Wright <[email protected]> wrote: >>>>> Hi Folks, >>>>> >>>>> A reminder that MCF 1.6 is due to be released on April 29. This means we >>>>> probably will want our first release candidate in about a week. >>>>> >>>>> There is only one outstanding ticket at the moment, owned by Piergiorgio. >>>>> Please evaluate this ticket and either resolve it or postpone it. >>>>> >>>>> I am also wondering if anyone is interested in being the release manager >>>>> for this release. I've done the last half-dozen releases or so and am >>>>> happy to do another, but it would be good if other committers also had >>>>> some >>>>> release engineering experience, I think. Volunteers? >>>>> >>>>> Karl >>>>> >>>>> >>>> >>> >> >
