RE: [VOTE] Move Jakarta to the Attic; close down Jakarta PMC
+1 Rest in peace! -Original Message- From: i...@darwinsys.com [mailto:i...@darwinsys.com] Sent: Thursday, November 10, 2011 13:19 PM To: Jakarta General List; Jakarta General List Subject: Re: [VOTE] Move Jakarta to the Attic; close down Jakarta PMC +1. Hail and farewell! -- Ian - Reply message - From: Henri Yandell bay...@apache.org To: Jakarta General List general@jakarta.apache.org Subject: [VOTE] Move Jakarta to the Attic; close down Jakarta PMC Date: Thu, Nov 10, 2011 19:01 A joint vote to retire Jakarta into the Attic and to ask the board to close down the PMC. [ ] +1 [ ] -1, because Hen - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [VOTE][LAZY] Move BCEL and JCS to Commons
+1 Gary On Jun 22, 2011, at 22:38, Rahul Akolkar rahul.akol...@gmail.com wrote: After reasonable support to the idea on Jakarta and Commons lists, this is a vote to move BCEL and JCS to Apache Commons. As part of the move, I'll nominate any active committers for Commons karma (so far: dbrosius, asmuts, tv -- anyone else, please ping this thread). Since neither may have enough PMC members active, this vote will be held by lazy consensus. If you object to moving either/both, please also provide a reason and an alternative course of action. Vote runs for 72 hours. Vote is being held on general@jao but is being cross-posted to ensure we reach the full audience. -Rahul - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
RE: [VOTE][LAZY] Move Jakarta Regexp to Attic
+1, move it. Gary Gregory Senior Software Engineer Rocket Software 3340 Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA Tel: +1.404.760.1560 Email: ggreg...@seagullsoftware.com Web: seagull.rocketsoftware.com -Original Message- From: Rahul Akolkar [mailto:rahul.akol...@gmail.com] Sent: Monday, March 21, 2011 20:00 To: Jakarta General List Cc: Jakarta Project Management Committee List; d...@jakarta.apache.org Subject: [VOTE][LAZY] Move Jakarta Regexp to Attic This is a vote to move Jakarta Regexp to the Apache Attic, based on the outcome of the most recent discussion on the topic. Since Regexp may not have enough PMC members active, this vote will be held by lazy consensus. If you object, please also provide a reasonable explanation. Vote runs for a week, ending no sooner than Mar 28th, ~8:00 pm Eastern US. Vote is being held on general@jao but is being cross-posted to ensure we reach the full audience. Please include general@jao on any replies. -Rahul - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
RE: [VOTE][LAZY] Move ECS, ORO and Regexp to Attic
For ORO and RegEx I am +1 to mothball. With RegEx in Java since 1.4, I do not see the need for these libs aside from legacy application support. I consider mothballing a service to the community at large: please, join us in the 21st century, port your RegEx code to Java 1.4. ;) Gary Gregory Senior Software Engineer Seagull Software email: ggreg...@seagullsoftware.com email: ggreg...@apache.org www.seagullsoftware.com -Original Message- From: Rahul Akolkar [mailto:rahul.akol...@gmail.com] Sent: Tuesday, August 17, 2010 18:19 To: Jakarta General List Subject: Re: [VOTE][LAZY] Move ECS, ORO and Regexp to Attic On Tue, Aug 17, 2010 at 8:21 PM, Vadim Gritsenko va...@reverycodes.com wrote: On Aug 15, 2010, at 12:16 AM, Rahul Akolkar wrote: This is a vote (or more correctly, three independent votes) to move Jakarta ECS, Jakarta ORO and Jakarta Regexp to the Apache Attic, based on the outcome of the most recent discussion on the topic. There is one unreleased bugfix on trunk since the last regexp release, that's probably the only reason stopping me from voting +1. But if you are eager to mothball it, I won't object. My vote is +0. snip/ I wouldn't say I'm eager to mothball any codebase, its upto the remaining developers of each of these codebases. In recent discussions, it seemed like one or more of the mentioned codebases may be ready for the Attic. My opinion is that unless we anticipate release activity, we can go ahead with the move. WRT Regex then, were/are you planning a release some time in the not so distant future with said bugfix? If so, it'd be great to make that release and then mothball it -- worth waiting in that case. What do you think? -Rahul Vadim Since none of these subprojects may have enough PMC members active, this vote will be held by lazy consensus. If you object, please also provide a reasonable explanation. Vote runs for a week, ending no sooner than Aug 22nd, ~1:00 am Eastern US. Vote is being held on gene...@jao but is being cross-posted to ensure we reach the full audience. Please include gene...@jao in your reply. -Rahul - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
RE: [PROPOSAL] One development list
-Original Message- From: Rahul Akolkar [mailto:rahul.akol...@gmail.com] Sent: Friday, October 09, 2009 14:44 To: Jakarta General List Cc: bcel-...@jakarta.apache.org; bsf-...@jakarta.apache.org; cactus- d...@jakarta.apache.org; ecs-...@jakarta.apache.org; jcs- d...@jakarta.apache.org; jmeter-...@jakarta.apache.org; oro- d...@jakarta.apache.org; regexp-...@jakarta.apache.org; slide- d...@jakarta.apache.org; Jakarta Project Management Committee List Subject: [PROPOSAL] One development list [Out of necessity, this is heavily cross-posted. Suggestion is to send any replies to the gene...@jakarta list only to keep any discussion in one place.] We currently have 8 active development lists at Jakarta, each devoted to a subproject. I've been subscribed to all for a while and based on my observations and the overall benefits of doing so, I think its time to consolidate them into a single development list at Jakarta. Motivations (not in any order): * Flattens and simplifies oversight - Not much else to be said on that. * Communication - Subprojects can often have various touch points. So, Rony's surprise today at the BSF taglib being retired is one example. Lets have all dev discussions on one list. * Cross-pollination - Most subprojects are at the point where it certainly wouldn't hurt to have the active folks from all of Jakarta around for dev discussions, votes etc. * Manageable overhead - More on this later, but we have a number of usual suspects showing up on many of the dev lists, they'd barely notice a difference. Others can manage, IMO/hopefully. Operationally: * The combined list traffic will obviously be more than any one of the separate lists. However, development tends to be in spurts on these lists and the probabilistic chances of more than a couple of subproject spurts happening at the same time seems quite low. Overall, combined traffic is not at all overpowering IMO. * The proposal will include closing current dev lists and adding all subscribers to the one new dev list. We'll post a heads up on these lists before that. Throw in site-cvs@ as well for good measure. * We could repurpose general@ as the one dev list, but OTOH, seems worthwhile to maintain the dev / general separation. * No changes proposed to the user lists. +1 to merging into one dev list. Thoughts? Lets say a little over a week (10 days, which should give us two weekends) for initial feedback and opinions please. -Rahul - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
RE: [RESULT][VOTE] Release BSF 3.0 RC1
I'm pretty sure there is no need for a delay once the vote has been tallied. It's up to the RM's schedule though :) Gary From: sebb [seb...@gmail.com] Sent: Monday, September 28, 2009 3:07 PM To: Bean Scripting Framework developers; Jakarta General List Subject: [RESULT][VOTE] Release BSF 3.0 RC1 It's been a while since the vote ... The tally is +1 (binding) Ant Elder Rony Flatscher Sebastian Bazley There were no other votes. The vote therefore passes. I propose to upload the files in a day or so. - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
RE: [VOTE] Release BSF 3.0 RC1
The first thing I looked for is information as to when I should use BSF vs. Java 6 javax.script. Since we do not build a site with Maven for this project, I looked on the project page but found nothing. We must make this information available somewhere. Thanks, Gary -Original Message- From: seb...@gmail.com [mailto:seb...@gmail.com] On Behalf Of sebb AT ASF Sent: Wednesday, August 12, 2009 11:14 AM To: Bean Scripting Framework developers; Jakarta General List Subject: [VOTE] Release BSF 3.0 RC1 Please review and vote on the BSF 3.0 RC1 release. The artifacts are available at: http://people.apache.org/~sebb/bsf-3.0-RC1/ and the an SVN tag is at: http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.0-rc1/ The vote will be open for at least 72 hours. S/// - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
RE: [VOTE] Release BSF 3.0 RC1
The build fails with Maven 2.2.1 and Sun Java 1.6.0_16 on Windows XP SP 3
32-bits.
---
T E S T S
---
Running org.apache.bsf.xml.JavaScriptXMLHelperTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.565 sec
FAILURE!
Results :
Tests in error:
testToOmElement(org.apache.bsf.xml.JavaScriptXMLHelperTestCase)
testToScriptXML(org.apache.bsf.xml.JavaScriptXMLHelperTestCase)
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
See attachements.
The works when I use Sun Java 1.5.0_19 though.
Gary
-Original Message-
From: seb...@gmail.com [mailto:seb...@gmail.com] On Behalf Of sebb AT ASF
Sent: Wednesday, August 12, 2009 11:14 AM
To: Bean Scripting Framework developers; Jakarta General List
Subject: [VOTE] Release BSF 3.0 RC1
Please review and vote on the BSF 3.0 RC1 release.
The artifacts are available at:
http://people.apache.org/~sebb/bsf-3.0-RC1/
and the an SVN tag is at:
http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.0-rc1/
The vote will be open for at least 72 hours.
S///
-
To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org
For additional commands, e-mail: general-h...@jakarta.apache.org
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Apache BSF
[INFO] Apache BSF API
[INFO] Apache BSF project to install 3rd party script engines
[INFO] Apache BSF Utils
[INFO] Apache BSF project to create the bsf-all jar
[INFO] Apache BSF testing for JavaScript/E4X
[INFO] Apache BSF testing for JavaScript/E4X 1.6R7 Axiom
[INFO] Apache BSF testing for Groovy
[INFO] Apache BSF testing for Groovy 1.1 release
[INFO] Apache BSF testing for JavaScript
[INFO] Apache BSF testing for Python
[INFO] Apache BSF testing for Jython 2.2
[INFO] Apache BSF Tests
[INFO]
[INFO] Building Apache BSF
[INFO]task-segment: [install]
[INFO]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing C:\temp\bsf-3.0-src-1\bsf-3.0-src\pom.xml to C:\Documents and
Settings\ggregory\.m2\repository\org\apache\bsf\parent\3.0\parent-3.0.pom
[INFO]
[INFO] Building Apache BSF API
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 12 source files to
C:\temp\bsf-3.0-src-1\bsf-3.0-src\bsf-api\target\classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 8 source files to
C:\temp\bsf-3.0-src-1\bsf-3.0-src\bsf-api\target\test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
C:\temp\bsf-3.0-src-1\bsf-3.0-src\bsf-api\target\surefire-reports
---
T E S T S
---
Running org.apache.bsf.ScriptEngineManagerTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.094 sec
Running org.apache.bsf.SimpleBindingsTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.bsf.ScriptExceptionTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
Running org.apache.bsf.SimpleScriptContextTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.bsf.AbstractScriptEngineTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Results :
Tests run: 30, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
C:\temp\bsf-3.0-src-1\bsf-3.0-src\bsf-api\target\bsf-api-3.0.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
C:\temp\bsf-3.0-src-1\bsf-3.0-src\bsf-api\target\bsf-api-3.0.jar to
C:\Documents and
Settings\ggregory\.m2\repository\org\apache\bsf\bsf-api\3.0\bsf-api-3.0.jar
[INFO]
[INFO] Building Apache BSF project to install 3rd party script engines
[INFO]task-segment:
RE: Announce: Commons-IO 1.3.2
The download link on this page: Thank you, Gary -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 1:05 PM To: general@jakarta.apache.org Subject: Announce: Commons-IO 1.3.2 Hi, the Jakarta Commons Team (or Apache Commons Team, nowadays) is glad to announce the release of Commons IO 1.3.2. Commons IO is a library of low-level utilities to assist with developing IO functionality. This is a bug fix release with the following changes: - Some tests, which are implicitly assuming a Unix-like file system, are now skipped on Windows. Fixes IO-115. - Created the FileCleaningTracker, basically a non-static version of the FileCleaner, which can be controlled by the user. Fixes IO-116. - EndianUtils - both readSwappedUnsignedInteger(...) methods could return negative numbers due to int/long casting. Fixes IO-117. Thanks to Hiroshi Ikeda. Commons-IO 1.3.2 is available from http://jakarta.apache.org/site/downloads/downloads_commons-io.cgi Jochen - 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: Announce: Commons-IO 1.3.2
Oops, I mean: The download link on this page: http://jakarta.apache.org/site/downloads/downloads_commons-io.cgi?Preferred=http%3A%2F%2Fwww.apache.org%2Fdist labeled '1.3.2.zip' for the Binary points to: http://www.apache.org/dist/jakarta/commons/io/binaries/commons-io-1.3.2.zip but the file is: http://www.apache.org/dist/jakarta/commons/io/binaries/commons-io-1.3.2-bin.zip Thank you, Gary -Original Message- From: Gary Gregory Sent: Tuesday, July 03, 2007 2:48 PM To: 'Jakarta General List' Subject: RE: Announce: Commons-IO 1.3.2 The download link on this page: Thank you, Gary -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 1:05 PM To: general@jakarta.apache.org Subject: Announce: Commons-IO 1.3.2 Hi, the Jakarta Commons Team (or Apache Commons Team, nowadays) is glad to announce the release of Commons IO 1.3.2. Commons IO is a library of low-level utilities to assist with developing IO functionality. This is a bug fix release with the following changes: - Some tests, which are implicitly assuming a Unix-like file system, are now skipped on Windows. Fixes IO-115. - Created the FileCleaningTracker, basically a non-static version of the FileCleaner, which can be controlled by the user. Fixes IO-116. - EndianUtils - both readSwappedUnsignedInteger(...) methods could return negative numbers due to int/long casting. Fixes IO-117. Thanks to Hiroshi Ikeda. Commons-IO 1.3.2 is available from http://jakarta.apache.org/site/downloads/downloads_commons-io.cgi Jochen - 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: Submitting patches
+1. I like having one place, Bugzilla, as the 'repository' for patches as opposed to email lists. Gary -Original Message- From: sebb [mailto:[EMAIL PROTECTED] Sent: Sunday, March 26, 2006 3:42 AM To: Jakarta General List Subject: Submitting patches Generally I find that patches are much easier to process as Bugzilla attachments, rather than sent to the developer list as an attachment. And if the patch is large, it uses everyones mail resources, most of whom aren't interested. Just received such a patch on JMeter - the poster helpfully has a blog where he says that he followed the guidelines in: http://jakarta.apache.org/site/source.html#Patches which do indeed suggest sending patches to the developer mailing list. I'd like to suggest a change, so that the preferred method of submitting patches is via Bugzilla or JIRA. In the case of projects using JIRA, I believe that asks for a software grant, so it's important that code is submitted that way. [Actually, I'm not sure when emailed patches are appropriate...] I'd also like to split the patch section into two: Patch Creation Patch Submission Any objections to this? If not, I'll make a start on updating the text - and put a copy on my home page for review. Sebastian (sebb AT AO) - 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] [site] New download pages
+1. Finally, I can download the a component + source on the /same/ page. :-) Gary -Original Message- From: Henri Yandell [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 4:48 PM To: general@jakarta.apache.org Subject: [VOTE] [site] New download pages I'd like to go ahead and move to my suggested new download pages: http://jakarta.apache.org/~bayard/jakarta/site/downloads/downloads.html [ ] +1 [ ] -1 or alternatively: [ ] +1, but fix this first: [ ] Currently the filenames match the names on the binindex.cgi page, I'm trying to stay as close as possible to the current site before making any other changes. It's easy enough to then do things like change 1.0.zip to hivemind-1.0.zip as Howard suggested. Post change, I'll focus on improving the Taglibs page to match the Commons one in style. 72 hour consensus vote. ie) a single -1 is a veto. Hen - 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: Exception handling Was: Future JDK features 2 items
try {
} catch(JMSException, RemoteException, SQLException e) {
}
+1
(We used to have something like that in Smalltalk)
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Future JDK features: Class Instance Variables (a la Smalltalk)
Future JDK features: Class Instance Variables (a la Smalltalk). Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Future JDK features: Class Instance Variables (a la Smalltalk)
IMO, the class instance variables concept is a great feature that one does not need everyday; but, when you do run into a use-case in Java, it hurts. I'll present the top two classic examples that I've run into countless times: (1) The GUI Node subclasses. o You need to populate a GUI list or a tree where each item is represented in the view in some fancy manner: icons, fonts colors, bells and whistles. o You create an abstract super class, like a UiTreeNode, with a subclasses for each kind of domain object you care to represent: FileTreeNode, DirectoryTreeNode, CustomerTreeNode, ZingBatTreeNode, etc. o You decide that for your application, some attributes like font and color can change for each instance of UITreeNode but that each subclass needs only one icon and one bell. o You create a font and color instance variable in UITreeNode. o But what do you do for the icon (and bell)? You cannot create a 'class instance variable' in Java. What you'd want is a static variable defined in UITreeNode whose value is unique for each subclass. You have two choices: (a) You make the icon (or whatever resource) an instance variable, which uses more memory (not that big a deal IMO unless you have huge lists) and incorrectly lets the reader believe that it is OK for each instance to have a different icon. This is not good because your code does not reflect your design. You are forced to very carefully Javadoc things or add code to make sure rules are not broken. In this case you can share the code in the super class like the accessor, the mutator and some management methods. By definition, you are not sharing the instance variable between instances obviously. (b) You can do it the other way, which is, you *duplicate* code in each subclass. You duplicate the static variable definition and the code. So, here, you share nothing and as we'll all agree, code duplication should be avoided. The third solution that I am only listing for completeness is to use some abstract methods in the root class, which ends up being a mixture of (a) and (b) and is even more confusion and hard to grok, IMO. The Class Instance Variable solves all of these problems. (2) Logging with subclasses A Class Instance Variable is nice when you want to have one log category per subclass in a hierarchy. Gary -Original Message- From: Dain Sundstrom [mailto:[EMAIL PROTECTED] Sent: Monday, October 25, 2004 15:21 To: Jakarta General List Subject: Re: Future JDK features: Class Instance Variables (a la Smalltalk) Can you explain what this is and why it is more useful then annoying? IMHO, most of the new features in Java 5 are way more annoying then useful. -dain -- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26 On Oct 25, 2004, at 2:42 PM, Gary Gregory wrote: Future JDK features: Class Instance Variables (a la Smalltalk). Gary - 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] Updating PMC bylaws
Minor tweak under Membership: I would switch the 2 paragraphs such that the voting-new-members-in bit comes before the I'm outta here bit. Makes the item more positive methinks. Gary -Original Message- From: Henri Yandell [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 10, 2004 08:59 To: Jakarta General List Subject: [VOTE] Updating PMC bylaws Suggested new bylaws are at: http://www.osjava.org/~hen/jakarta/management.html The aim is to identify the current reality, rather than plan out a new set of bylaws. I believe I've responded to the past week of comments, sometimes by dropping things from the text as they require discussion (ie: active/inactive projects). Voting rules are that we need at least 3 +1 _PMC votes_, and a 3/4 majority of +1's to -1's. I'll announce results next Tuesday. === [ ] +1 - let's do it [ ] -1 - not good === I think the above voting rule is fair enough, though there are others we could use. Let's not worry too much about it unless we have major disagreements. Also, if people have non-voting commentary, it would be nice if they could change the subject (ie: Madness Was: [VOTE] Updating PMC bylaws). Makes counting the votes a lot easier. Hen - 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: Overrode an entry Was: [Jakarta Wiki] Updated: JakartaReport-July2004
No problem, I did not really know where to put it, so I placed the item
near another Commons one.
Gary
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 13:00
To: Verwaltung
Cc: Gary Gregory
Subject: Overrode an entry Was: [Jakarta Wiki] Updated: JakartaReport-
July2004
Apologies for this Gary, but I think you won't mind.
Release news goes higher up, so when Commons Codec is out, it can just
appear at the top. It's not a big deal as it's very easy for me to
collate
the releases from the front page.
I'm also aiming to only have subprojects listed (HttpClient will be a
subproject soon I think), so Commons bits under the Commons section.
Hen
On Wed, 14 Jul 2004 [EMAIL PROTECTED] wrote:
Date: 2004-07-14T11:16:10
Editor: GaryGregory [EMAIL PROTECTED]
Wiki: Jakarta Wiki
Page: JakartaReport-July2004
URL: http://wiki.apache.org/jakarta/JakartaReport-July2004
no comment
Change Log:
--
@@ -24,6 +24,10 @@
Commons HttpClient
+ Commons Codec
+
+The vote to release version 1.3 has passed. Gary Gregory is
currently
going through the signing and publish process.
+
ECS
HiveMind
-
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] ORO 2.0.8 maintenance release
-Original Message- From: Daniel F. Savarese [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 23, 2003 17:40 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [VOTE] ORO 2.0.8 maintenance release [X] +1 I approve the release of jakarta-oro version 2.0.8. [ ] -1 I do not approve the release of jakarta-oro version 2.0.8. Gary Gregory (in a pending state, awaiting adding to the committee file)
RE: [VOTE] ORO 2.0.8 maintenance release
Ah, no, sorry, I was quoting my state as a PMC member from the last message I saw my name in. Actually, I am now wondering if my voting was even appropriate. I would guess not since I am an ORO user, not a developer, perhaps a +0 would be better. I am not sure. Gary -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 24, 2003 15:34 To: Jakarta Project Management Committee List; Gary Gregory Cc: 'Jakarta Project Management Committee List'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [VOTE] ORO 2.0.8 maintenance release Quoting Gary Gregory [EMAIL PROTECTED]: -Original Message- From: Daniel F. Savarese [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 23, 2003 17:40 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [VOTE] ORO 2.0.8 maintenance release [X] +1 I approve the release of jakarta-oro version 2.0.8. [ ] -1 I do not approve the release of jakarta-oro version 2.0.8. Gary Gregory (in a pending state, awaiting adding to the committee file) Do you mean you're awaiting commit karma on the jakarta-oro repository? If so, cnan you (or anyone) point me to a vote thread electing Gary as a committer? With that I can add you immediately. Craig McClanahan
