[jira] Resolved: (CONNECTORS-137) Tag libraries need ASF headers
[ https://issues.apache.org/jira/browse/CONNECTORS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-137. Resolution: Fixed Fix Version/s: ManifoldCF 0.1 r1056195 (trunk), and r1056196 (release-0.1-branch) > Tag libraries need ASF headers > -- > > Key: CONNECTORS-137 > URL: https://issues.apache.org/jira/browse/CONNECTORS-137 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.1 > > > The standard tag library tld's, which came from the jakarta standard tag > library 1.1.2, do not have ASF headers on them but should. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CONNECTORS-137) Tag libraries need ASF headers
[ https://issues.apache.org/jira/browse/CONNECTORS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-137: -- Assignee: Karl Wright > Tag libraries need ASF headers > -- > > Key: CONNECTORS-137 > URL: https://issues.apache.org/jira/browse/CONNECTORS-137 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > > The standard tag library tld's, which came from the jakarta standard tag > library 1.1.2, do not have ASF headers on them but should. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-137) Tag libraries need ASF headers
Tag libraries need ASF headers -- Key: CONNECTORS-137 URL: https://issues.apache.org/jira/browse/CONNECTORS-137 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.1 Reporter: Karl Wright Priority: Blocker The standard tag library tld's, which came from the jakarta standard tag library 1.1.2, do not have ASF headers on them but should. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-132) Release image must not include binary
[ https://issues.apache.org/jira/browse/CONNECTORS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-132. Resolution: Fixed Fix Version/s: ManifoldCF 0.1 Cut out the whole deliverable except for forrest-built docs and javadocs. Also revamped the README.txt to make it consistent with the new archive. > Release image must not include binary > - > > Key: CONNECTORS-132 > URL: https://issues.apache.org/jira/browse/CONNECTORS-132 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.1 > > > The release image cannot include any compiled ManifoldCF code, according to > the incubator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-136) ant rat-sources should exclude SharePoint web service control files
[ https://issues.apache.org/jira/browse/CONNECTORS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-136. Resolution: Fixed Fix Version/s: ManifoldCF 0.1 r1056157 (trunk), r1056158 (release-0.1-branch) > ant rat-sources should exclude SharePoint web service control files > --- > > Key: CONNECTORS-136 > URL: https://issues.apache.org/jira/browse/CONNECTORS-136 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.1 > > > The following files are a Microsoft binary format that cannot have changes > made to it except through Visual Studio. They should thus be excluded from > the rat-sources license check. > connectors/sharepoint/webservice/Web > References/SPPermissionsService/Reference.map > connectors/sharepoint/webservice/Properties/Settings.settings > connectors/sharepoint/webservice/Properties/AssemblyInfo.cs > connectors/meridio/webservice/Test Harness/source code/TestHarness.cs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-135) Incorrect or missing SVN property settings
[ https://issues.apache.org/jira/browse/CONNECTORS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-135. Resolution: Fixed Fix Version/s: ManifoldCF 0.1 Commits too numerous to enumerate here; committed to trunk and to release-0.1-branch. > Incorrect or missing SVN property settings > -- > > Key: CONNECTORS-135 > URL: https://issues.apache.org/jira/browse/CONNECTORS-135 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Sebb >Priority: Minor > Fix For: ManifoldCF 0.1 > > Attachments: connectors_exec.sh, connectors_native.sh > > > There are quite a few incorrect SVN property settings. > A lot of files have been flagged as executable; this is generally a bad idea > in SVN. > If files do need to be executable, that should be done as part of the release > process (anyway the exec bit is not preserved by Zip archives) > A lot of source files don't have eol-style = native. > This tends to cause problems when committers work on different OSes. > Patches to follow - can be applied on Unix or Windows (rename the script > file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CONNECTORS-135) Incorrect or missing SVN property settings
[ https://issues.apache.org/jira/browse/CONNECTORS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-135: -- Assignee: Karl Wright > Incorrect or missing SVN property settings > -- > > Key: CONNECTORS-135 > URL: https://issues.apache.org/jira/browse/CONNECTORS-135 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Sebb >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.1 > > Attachments: connectors_exec.sh, connectors_native.sh > > > There are quite a few incorrect SVN property settings. > A lot of files have been flagged as executable; this is generally a bad idea > in SVN. > If files do need to be executable, that should be done as part of the release > process (anyway the exec bit is not preserved by Zip archives) > A lot of source files don't have eol-style = native. > This tends to cause problems when committers work on different OSes. > Patches to follow - can be applied on Unix or Windows (rename the script > file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-136) ant rat-sources should exclude SharePoint web service control files
ant rat-sources should exclude SharePoint web service control files --- Key: CONNECTORS-136 URL: https://issues.apache.org/jira/browse/CONNECTORS-136 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.1 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker The following files are a Microsoft binary format that cannot have changes made to it except through Visual Studio. They should thus be excluded from the rat-sources license check. connectors/sharepoint/webservice/Web References/SPPermissionsService/Reference.map connectors/sharepoint/webservice/Properties/Settings.settings connectors/sharepoint/webservice/Properties/AssemblyInfo.cs connectors/meridio/webservice/Test Harness/source code/TestHarness.cs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-134) Unpacked build does not build due to missing empty directories
[ https://issues.apache.org/jira/browse/CONNECTORS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-134. Resolution: Fixed Fix Version/s: ManifoldCF 0.1 r1056116 (trunk), r1056118 (release-0.1-branch). > Unpacked build does not build due to missing empty directories > -- > > Key: CONNECTORS-134 > URL: https://issues.apache.org/jira/browse/CONNECTORS-134 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.1 > > > When the .zip build is unpacked, the empty directories are not created, and > the build fails as a result. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONNECTORS-133) README should include incubator disclaimer
[ https://issues.apache.org/jira/browse/CONNECTORS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978544#action_12978544 ] Karl Wright commented on CONNECTORS-133: Further revision: incubator decided that DISCLAIMER.txt addition was better than README.txt addition. r1056104 (trunk), r1056105 (release-0.1-branch) > README should include incubator disclaimer > -- > > Key: CONNECTORS-133 > URL: https://issues.apache.org/jira/browse/CONNECTORS-133 > Project: ManifoldCF > Issue Type: Bug >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.1 > > > The incubator disclaimer is as follows: > Apache "Podling-Name" is an effort undergoing incubation at The Apache > Software Foundation (ASF), sponsored by the name of sponsor. Incubation is > required of all newly accepted projects until a further review indicates that > the infrastructure, communications, and decision making process have > stabilized in a manner consistent with other successful ASF projects. While > incubation status is not necessarily a reflection of the completeness or > stability of the code, it does indicate that the project has yet to be fully > endorsed by the ASF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-135) Incorrect or missing SVN property settings
Incorrect or missing SVN property settings -- Key: CONNECTORS-135 URL: https://issues.apache.org/jira/browse/CONNECTORS-135 Project: ManifoldCF Issue Type: Improvement Reporter: Sebb Priority: Minor Attachments: connectors_exec.sh, connectors_native.sh There are quite a few incorrect SVN property settings. A lot of files have been flagged as executable; this is generally a bad idea in SVN. If files do need to be executable, that should be done as part of the release process (anyway the exec bit is not preserved by Zip archives) A lot of source files don't have eol-style = native. This tends to cause problems when committers work on different OSes. Patches to follow - can be applied on Unix or Windows (rename the script file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CONNECTORS-135) Incorrect or missing SVN property settings
[ https://issues.apache.org/jira/browse/CONNECTORS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated CONNECTORS-135: Attachment: connectors_native.sh connectors_exec.sh > Incorrect or missing SVN property settings > -- > > Key: CONNECTORS-135 > URL: https://issues.apache.org/jira/browse/CONNECTORS-135 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Sebb >Priority: Minor > Attachments: connectors_exec.sh, connectors_native.sh > > > There are quite a few incorrect SVN property settings. > A lot of files have been flagged as executable; this is generally a bad idea > in SVN. > If files do need to be executable, that should be done as part of the release > process (anyway the exec bit is not preserved by Zip archives) > A lot of source files don't have eol-style = native. > This tends to cause problems when committers work on different OSes. > Patches to follow - can be applied on Unix or Windows (rename the script > file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-89) Quickstart build should also create a ZIP file
[ https://issues.apache.org/jira/browse/CONNECTORS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-89. --- Resolution: Won't Fix Fix Version/s: ManifoldCF 0.1 Assignee: Karl Wright The release strategy has been changed, since we determined it was more appropriate to include sources everywhere so people could build their own connectors. > Quickstart build should also create a ZIP file > -- > > Key: CONNECTORS-89 > URL: https://issues.apache.org/jira/browse/CONNECTORS-89 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.1 > > > The Quickstart example build should create a zip file that's appropriate for > download. This should include everything for Quickstart, as well as what is > needed for all auxiliary processes (namely, the Documentum and FileNet RMI > processes). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CONNECTORS-134) Unpacked build does not build due to missing empty directories
[ https://issues.apache.org/jira/browse/CONNECTORS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-134: -- Assignee: Karl Wright > Unpacked build does not build due to missing empty directories > -- > > Key: CONNECTORS-134 > URL: https://issues.apache.org/jira/browse/CONNECTORS-134 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > > When the .zip build is unpacked, the empty directories are not created, and > the build fails as a result. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-133) README should include incubator disclaimer
[ https://issues.apache.org/jira/browse/CONNECTORS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-133. Resolution: Fixed Fix Version/s: ManifoldCF 0.1 r1056054 (trunk), 1056055 (release-0.1-branch) > README should include incubator disclaimer > -- > > Key: CONNECTORS-133 > URL: https://issues.apache.org/jira/browse/CONNECTORS-133 > Project: ManifoldCF > Issue Type: Bug >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.1 > > > The incubator disclaimer is as follows: > Apache "Podling-Name" is an effort undergoing incubation at The Apache > Software Foundation (ASF), sponsored by the name of sponsor. Incubation is > required of all newly accepted projects until a further review indicates that > the infrastructure, communications, and decision making process have > stabilized in a manner consistent with other successful ASF projects. While > incubation status is not necessarily a reflection of the completeness or > stability of the code, it does indicate that the project has yet to be fully > endorsed by the ASF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-131) Download page must break out links for KEYS file, CHANGES.txt, and the signature files
[ https://issues.apache.org/jira/browse/CONNECTORS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-131. Resolution: Fixed Fix Version/s: ManifoldCF 0.1 r1056045 (trunk), and r1056048 (release-0.1-branch) > Download page must break out links for KEYS file, CHANGES.txt, and the > signature files > -- > > Key: CONNECTORS-131 > URL: https://issues.apache.org/jira/browse/CONNECTORS-131 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.1 > > > Per incubator rules, download page must break out links for KEYS file, > CHANGES.txt, and the signature files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-134) Unpacked build does not build due to missing empty directories
Unpacked build does not build due to missing empty directories -- Key: CONNECTORS-134 URL: https://issues.apache.org/jira/browse/CONNECTORS-134 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.1 Reporter: Karl Wright Priority: Blocker When the .zip build is unpacked, the empty directories are not created, and the build fails as a result. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-133) README should include incubator disclaimer
README should include incubator disclaimer -- Key: CONNECTORS-133 URL: https://issues.apache.org/jira/browse/CONNECTORS-133 Project: ManifoldCF Issue Type: Bug Affects Versions: ManifoldCF 0.1 Reporter: Karl Wright Assignee: Karl Wright Priority: Blocker The incubator disclaimer is as follows: Apache "Podling-Name" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of sponsor. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CONNECTORS-131) Download page must break out links for KEYS file, CHANGES.txt, and the signature files
[ https://issues.apache.org/jira/browse/CONNECTORS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-131: -- Assignee: Karl Wright > Download page must break out links for KEYS file, CHANGES.txt, and the > signature files > -- > > Key: CONNECTORS-131 > URL: https://issues.apache.org/jira/browse/CONNECTORS-131 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > > Per incubator rules, download page must break out links for KEYS file, > CHANGES.txt, and the signature files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CONNECTORS-132) Release image must not include binary
[ https://issues.apache.org/jira/browse/CONNECTORS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-132: -- Assignee: Karl Wright > Release image must not include binary > - > > Key: CONNECTORS-132 > URL: https://issues.apache.org/jira/browse/CONNECTORS-132 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.1 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > > The release image cannot include any compiled ManifoldCF code, according to > the incubator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-132) Release image must not include binary
Release image must not include binary - Key: CONNECTORS-132 URL: https://issues.apache.org/jira/browse/CONNECTORS-132 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.1 Reporter: Karl Wright Priority: Blocker The release image cannot include any compiled ManifoldCF code, according to the incubator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-131) Download page must break out links for KEYS file, CHANGES.txt, and the signature files
Download page must break out links for KEYS file, CHANGES.txt, and the signature files -- Key: CONNECTORS-131 URL: https://issues.apache.org/jira/browse/CONNECTORS-131 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.1 Reporter: Karl Wright Priority: Blocker Per incubator rules, download page must break out links for KEYS file, CHANGES.txt, and the signature files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-130) Output connectors that cannot deal with folder access tokens should reject documents that have them
[ https://issues.apache.org/jira/browse/CONNECTORS-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-130. Resolution: Fixed Fix Version/s: ManifoldCF next r1055960. > Output connectors that cannot deal with folder access tokens should reject > documents that have them > --- > > Key: CONNECTORS-130 > URL: https://issues.apache.org/jira/browse/CONNECTORS-130 > Project: ManifoldCF > Issue Type: Bug > Components: Lucene/SOLR connector >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Trivial > Fix For: ManifoldCF next > > > The Solr output connector is not currently structured to deal with > folder-level access tokens. None of the repository connectors generate these > either, but one theoretically could. The Solr output connector should throw > out all documents that have such security, because that security will not be > enforced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONNECTORS-130) Output connectors that cannot deal with folder access tokens should reject documents that have them
Output connectors that cannot deal with folder access tokens should reject documents that have them --- Key: CONNECTORS-130 URL: https://issues.apache.org/jira/browse/CONNECTORS-130 Project: ManifoldCF Issue Type: Bug Components: Lucene/SOLR connector Reporter: Karl Wright Assignee: Karl Wright Priority: Trivial The Solr output connector is not currently structured to deal with folder-level access tokens. None of the repository connectors generate these either, but one theoretically could. The Solr output connector should throw out all documents that have such security, because that security will not be enforced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [RESULT][VOTE] Release ManifoldCF 0.1?
Thanks for kicking this off! I take it only the incubator PMC members are allowed to vote this time round? Karl On Thu, Jan 6, 2011 at 8:08 AM, Grant Ingersoll wrote: > I can do the stuff to mirror the releases, but it is pretty easy. It does > look like we need to do an incubator vote. I will start that. > > -Grant > > On Jan 4, 2011, at 12:57 PM, Karl Wright wrote: > >> Also to be clear, the release will occur only when we tag the release >> branch, and copy the RC to the download mirror. I actually do not >> know how to do the latter step, and I probably don't have any of the >> necessary magic powers either. So, once the incubator vote is done, >> can someone point me at the correct documentation and/or walk me >> through the process? The mirror folder I presumed we would be putting >> the release in is "manifoldcf". >> >> Thanks! >> Karl >> >> On Tue, Jan 4, 2011 at 12:41 PM, Grant Ingersoll wrote: >>> Just to be clear, before anyone puts up artifacts as releases, I think >>> there are some other steps we need to go through (I believe we need a >>> Incubator level vote, but let me check) >>> >>> -Grant >>> >>> On Jan 4, 2011, at 9:15 AM, Karl Wright wrote: >>> If anyone wants to add their key to the KEYS file, please feel free to go ahead and do so on trunk. There's a release branch so you won't mess anything up for the 0.1 release. Karl On Tue, Jan 4, 2011 at 9:11 AM, Simon Willnauer wrote: > I checked out all archives, verified the checksum & signatures. Looks all > good. > All tests passed for me after downloading and extracting the sources. > > I think we are good to go. > > here is my +1 - congratulations karl! > > simon > > PS: seems like we should have another keysigning party - only two > keys there and karls is only signed by grant. > > On Tue, Jan 4, 2011 at 3:03 AM, Karl Wright wrote: >> +1 from me. >> Karl >> >> On Mon, Jan 3, 2011 at 3:20 PM, Grant Ingersoll >> wrote: >>> Sorry for the long delay. I think we are in pretty good shape as far >>> as the legal bits go. I also did an ant test and went over the >>> signatures, LICENSE.txt, NOTICE.txt and checked out the license headers >>> via RAT. >>> >>> For a 0.1 release, here's my +1. >>> >>> For the record, Karl, you can vote and it is binding. Other PPMC >>> members are the committers, so they should check it out and vote too. >>> >>> -Grant >>> >>> On Jan 3, 2011, at 6:11 AM, Karl Wright wrote: >>> Any news on this front? Karl On Sun, Dec 26, 2010 at 6:27 PM, Karl Wright wrote: > I hope we can scrape together two more votes. Who else is on the PPMC > for ManifoldCF? That's never been clear to me. > > Karl > > On Fri, Dec 24, 2010 at 4:04 PM, Grant Ingersoll > wrote: >> Yeah, sorry. It is the holidays for me. I hope to look at it on >> Monday. For the record, we need 3 votes from the PPMC and then I >> think we need to go to the Incubator PMC and vote there, but I will >> read up on it. >> >> On Dec 24, 2010, at 11:17 AM, Jack Krupansky wrote: >> >>> It's most likely the holidays. Too much of a mad rush, either to >>> leave early or to get "real" work done to try to leave early. >>> >>> Sorry I wasn't able to find time to try out the RC. Hopefully... >>> next week will be slow and I'll have better luck finding a few >>> minutes of quiet time. >>> >>> -- Jack Krupansky >>> >>> -Original Message- From: Karl Wright >>> Sent: Friday, December 24, 2010 11:09 AM >>> To: connectors-dev >>> Subject: [RESULT][VOTE] Release ManifoldCF 0.1? >>> >>> There were zero votes in favor, and zero against. >>> >>> I feel little uncomfortable voting myself, since I put together the >>> release. Therefore, the vote effectively fails. >>> >>> Karl >>> >>> On Sun, Dec 19, 2010 at 7:33 PM, Karl Wright >>> wrote: +1 if you think ManifoldCF 0.1 is ready for release, -1 if not. (If this vote passes, I believe we will still need to hold a vote in the incubator general list.) Thanks, Karl >>> >> >> -- >> Grant Ingersoll >> http://www.lucidimagination.com >> >> > >>> >>> -- >>> Grant Ingersoll >>> http://www.lucidimagination.com >>> >>> >> > >>> >>> -- >>> Grant Ingersoll >>> http://www.lucidimagination.com >>> >>> > > -- > Grant Ingersoll > http://w
Re: [RESULT][VOTE] Release ManifoldCF 0.1?
I can do the stuff to mirror the releases, but it is pretty easy. It does look like we need to do an incubator vote. I will start that. -Grant On Jan 4, 2011, at 12:57 PM, Karl Wright wrote: > Also to be clear, the release will occur only when we tag the release > branch, and copy the RC to the download mirror. I actually do not > know how to do the latter step, and I probably don't have any of the > necessary magic powers either. So, once the incubator vote is done, > can someone point me at the correct documentation and/or walk me > through the process? The mirror folder I presumed we would be putting > the release in is "manifoldcf". > > Thanks! > Karl > > On Tue, Jan 4, 2011 at 12:41 PM, Grant Ingersoll wrote: >> Just to be clear, before anyone puts up artifacts as releases, I think there >> are some other steps we need to go through (I believe we need a Incubator >> level vote, but let me check) >> >> -Grant >> >> On Jan 4, 2011, at 9:15 AM, Karl Wright wrote: >> >>> If anyone wants to add their key to the KEYS file, please feel free to >>> go ahead and do so on trunk. There's a release branch so you won't >>> mess anything up for the 0.1 release. >>> >>> Karl >>> >>> On Tue, Jan 4, 2011 at 9:11 AM, Simon Willnauer >>> wrote: I checked out all archives, verified the checksum & signatures. Looks all good. All tests passed for me after downloading and extracting the sources. I think we are good to go. here is my +1 - congratulations karl! simon PS: seems like we should have another keysigning party - only two keys there and karls is only signed by grant. On Tue, Jan 4, 2011 at 3:03 AM, Karl Wright wrote: > +1 from me. > Karl > > On Mon, Jan 3, 2011 at 3:20 PM, Grant Ingersoll > wrote: >> Sorry for the long delay. I think we are in pretty good shape as far as >> the legal bits go. I also did an ant test and went over the signatures, >> LICENSE.txt, NOTICE.txt and checked out the license headers via RAT. >> >> For a 0.1 release, here's my +1. >> >> For the record, Karl, you can vote and it is binding. Other PPMC >> members are the committers, so they should check it out and vote too. >> >> -Grant >> >> On Jan 3, 2011, at 6:11 AM, Karl Wright wrote: >> >>> Any news on this front? >>> Karl >>> >>> On Sun, Dec 26, 2010 at 6:27 PM, Karl Wright wrote: I hope we can scrape together two more votes. Who else is on the PPMC for ManifoldCF? That's never been clear to me. Karl On Fri, Dec 24, 2010 at 4:04 PM, Grant Ingersoll wrote: > Yeah, sorry. It is the holidays for me. I hope to look at it on > Monday. For the record, we need 3 votes from the PPMC and then I > think we need to go to the Incubator PMC and vote there, but I will > read up on it. > > On Dec 24, 2010, at 11:17 AM, Jack Krupansky wrote: > >> It's most likely the holidays. Too much of a mad rush, either to >> leave early or to get "real" work done to try to leave early. >> >> Sorry I wasn't able to find time to try out the RC. Hopefully... >> next week will be slow and I'll have better luck finding a few >> minutes of quiet time. >> >> -- Jack Krupansky >> >> -Original Message- From: Karl Wright >> Sent: Friday, December 24, 2010 11:09 AM >> To: connectors-dev >> Subject: [RESULT][VOTE] Release ManifoldCF 0.1? >> >> There were zero votes in favor, and zero against. >> >> I feel little uncomfortable voting myself, since I put together the >> release. Therefore, the vote effectively fails. >> >> Karl >> >> On Sun, Dec 19, 2010 at 7:33 PM, Karl Wright >> wrote: >>> +1 if you think ManifoldCF 0.1 is ready for release, -1 if not. (If >>> this vote passes, I believe we will still need to hold a vote in the >>> incubator general list.) >>> Thanks, >>> Karl >> > > -- > Grant Ingersoll > http://www.lucidimagination.com > > >> >> -- >> Grant Ingersoll >> http://www.lucidimagination.com >> >> > >> >> -- >> Grant Ingersoll >> http://www.lucidimagination.com >> >> -- Grant Ingersoll http://www.lucidimagination.com
