Re: [VOTE] Approve the release of Tuscany SDO Java 1.1-incubating (release candidate 2)

[kelvin goodson]

Thanks for taking the time to look at this release and for these points.  I
won't have time to address them immediately.  A couple of them I think I may
not be issues,  but  I'm going to need to do a respin when I can get to it.

Kelvin.

On 10/03/2008, sebb <[EMAIL PROTECTED]> wrote:
>
> On 10/03/2008, kelvin goodson <[EMAIL PROTECTED]> wrote:
> > The Tuscany community had a vote to release SDO Java 1.1-incubatingrelease
> >  candidate 2 [1] which was passed with 7+1s and no -1s.
> >
> >  Please vote to approve this release.
> >
> >  The distribution files are at [2]
> >  Maven artifacts for the release candidate are available at [3]
> >  The tag for the release is at [4]
> >
> >  The rat report is at - [5], [6]
> >
> >  Here's my +1
> >
> >  Kelvin.
> >
> >  [1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg28403.html
>
> >  [2] http://people.apache.org/~amita/tuscany/1.1-RC2<
> http://people.apache.org/%7Eamita/tuscany/1.1-RC2>
>
> -1: the source archive ought to have a NOTICE file alongside the
> LICENSE file at the root.
>
> -0: The MD5 files use a non-standard format, which means that existing
> utilities cannot check them.
>
> Instead of:
>
> apache-tuscany-sdo-1.1-incubating-src.zip:
> ED 69 2B B1 5E 6B 3C DB  DD 18 08 0A 2A 9D 4D 9A
>
> they should be
>
> ED692BB15E6B3CDBDD18080A2A9D4D9A
>
> or
>
> ED692BB15E6B3CDBDD18080A2A9D4D9A *
> apache-tuscany-sdo-1.1-incubating-src.zip
>
> Note that the Maven MD5 files use a correct format (at least the ones
> I checked).
>
> -0: the jar manifests ought to contain the Java source and target
> versions.
> And the Implementation-Version should reflect the actual version
>
> -0.5: the manifest in the binary zip is inadequate; it does not
> contain any information on the product.
>
> >  [3] http://people.apache.org/~amita/tuscany/1.1-RC2/maven<
> http://people.apache.org/%7Eamita/tuscany/1.1-RC2/maven>
>
> -0.5: the jar manifests ought to contain the Java source and target
> versions. And the correct Implementation-Version.
>
>
> >  [4]
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1-incubating/
>
>
> -1: There should be LICENSE and NOTICE files at the root of the directory
> tree.
>
> A README would also be useful, e.g. to say which Java version is
> needed and how to build/install the software (or pointers to the
> instructions).
>
> >  [5]
> >
> http://people.apache.org/~amita/tuscany/1.1-RC2/rat-SDO-1.1-incubating-RC2.txt
> <
> http://people.apache.org/%7Eamita/tuscany/1.1-RC2/rat-SDO-1.1-incubating-RC2.txt
> >
> >  [6]
> >
> http://people.apache.org/~amita/tuscany/1.1-RC2/rat-SDO-1.1-incubating-RC2-Exceptions.txt
> <
> http://people.apache.org/%7Eamita/tuscany/1.1-RC2/rat-SDO-1.1-incubating-RC2-Exceptions.txt
> >
> >
>
> -1: where is the KEYS file? This probably ought to be in SVN. Whoever
> signed the files must add their public key to the file.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

[VOTE] Approve the release of Tuscany SDO Java 1.1-incubating (release candidate 2)

[kelvin goodson]

The Tuscany community had a vote to release SDO Java 1.1-incubating release
candidate 2 [1] which was passed with 7+1s and no -1s.

Please vote to approve this release.

The distribution files are at [2]
Maven artifacts for the release candidate are available at [3]
The tag for the release is at [4]

The rat report is at - [5], [6]

Here's my +1

Kelvin.

[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg28403.html
[2] 
http://people.apache.org/~amita/tuscany/1.1-RC2
[3] 
http://people.apache.org/~amita/tuscany/1.1-RC2/maven
[4]
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1-incubating/
[5]
http://people.apache.org/~amita/tuscany/1.1-RC2/rat-SDO-1.1-incubating-RC2.txt
[6]
http://people.apache.org/~amita/tuscany/1.1-RC2/rat-SDO-1.1-incubating-RC2-Exceptions.txt

Re: [Proposal] NoNameYet : Link Error - please use this link

[kelvin goodson]

FYI,  to date the discussion I opened on jcp-open to try to understand
people's experiences re developing reference impls in an environment that
fosters innovation is sadly inconclusive.  There are 2 respondents to date,
one with a strong opinion that there is no conflict,  and one proposing that
there is a significant conflict.

Kelvin.

On 19/02/2008, kelvin goodson <[EMAIL PROTECTED]> wrote:
>
>
>
> On 19/02/2008, Simon Nash <[EMAIL PROTECTED]> wrote:
> 
>
> >
> > One topic from the tuscany-user discussion that's worth exposing here
> > is whether the NNY project would be a "pure RI" with no extensions
> > beyond the spec, or a vehicle for innovation to extend the specs, as
> > both Tuscany SCA and SDO have been.  My view is that it will need to
> > be at least some of the latter in order to build a sustainable
> > community of developers and users.
>
>
> +1
>
> This will create some challenges
> > given that one of the goals of the NNY project is to deliver the
> > official JCP RI.
> >
> >Simon
>
>  
>
> I just asked a question on the jcp-open mailing list to find out how other
> projects that do RIs in Apache handle the apparent contention.  It should
> appear under a February 2008 heading in the mailing list archive at [1]
> shortly.
>
> Kelvin.
>
> [1] http://mail-archives.apache.org/mod_mbox/www-jcp-open/

Re: [Proposal] NoNameYet : Link Error - please use this link

[kelvin goodson]

On 19/02/2008, Simon Nash <[EMAIL PROTECTED]> wrote:


>
> One topic from the tuscany-user discussion that's worth exposing here
> is whether the NNY project would be a "pure RI" with no extensions
> beyond the spec, or a vehicle for innovation to extend the specs, as
> both Tuscany SCA and SDO have been.  My view is that it will need to
> be at least some of the latter in order to build a sustainable
> community of developers and users.


+1

This will create some challenges
> given that one of the goals of the NNY project is to deliver the
> official JCP RI.
>
>Simon

 

I just asked a question on the jcp-open mailing list to find out how other
projects that do RIs in Apache handle the apparent contention.  It should
appear under a February 2008 heading in the mailing list archive at [1]
shortly.

Kelvin.

[1] http://mail-archives.apache.org/mod_mbox/www-jcp-open/

Re: [Proposal] NoNameYet : Link Error - please use this link

[kelvin goodson]

Hi Paul,

  what was it about the proposal section discussing Tuscany that confused
you?  I think what we were trying to say is that this work belongs in a
project of it own,  since Tuscany has a so much wider scope than this, and
the overall aims of the proposal are quite different. The new project
requires an environment where it can focus on the clear aim of implementing
this JSR RI and TCK, or future versions, without the distractions that would
come with being part of a larger project; needing to address the community
issues that having a wider remit would require.

Kelvin.

On 31/01/2008, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> Kelvin, NoNameProposers
>
> Maybe no-one has responded yet because no-one wants to ask the hard
> questions! So here I go:
>
> Perhaps you can explain why this effort isn't being rolled into the
> Tuscany work.
>
> There are some obvious reasons why I am confused by this proposal:
>
> 1. Tuscany already has the objective of producing code for SDO, and
> already has code for SDO.
> 2. Tuscany was another proposal to the IPMC predominantly coming from
> IBM and BEA employees.
> 3. The BEA committers left Tuscany and created a fork elsewhere
> 3. Tuscany has been identified as lacking diversity.
>
> Why will this project gain diversity when Tuscany is finding it hard?
> This move seems designed to make it even harder for both Tuscany and
> NNYP to get diversity by splitting the pool of potential committers
> even more thinly.
>
> I did read the paragraph on the relationship to Tuscany but I'm afraid
> I came out more confused.
>
> I'm sure there are more hard questions but I think that's enough to be
> going on with.
>
> Regards,
> Paul
>
> On Jan 31, 2008 9:47 AM, kelvin goodson <[EMAIL PROTECTED]> wrote:
> > http://wiki.apache.org/incubator/NoNameYetProposal
> >
> > That's what you get for employing reuse tactics -- gmail remembers the
> > original URL.  I've been caught by this before, so I thought I had taken
> > appropriate action to avoid this behaviour, but sadly not so, apologies.
> > Kelvin
> >
> > On 31/01/2008, kelvin goodson <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi all,
> > >
> > > We've posted an Apache Incubator proposal onto the incubator wiki
> > >
> > > http://wiki.apache.org/incubator/NoNameYetProposal
> > >
> > > We haven't got a good name yet,  SandStorm is a contender, as is
> Snowdon
> > >
> > > Suggestions and comments welcome,
> > >
> > > Kelvin.
> > >
> > > <http://wiki.apache.org/incubator/ThriftProposal>
> >
>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [Proposal] NoNameYet : Link Error - please use this link

[kelvin goodson]

http://wiki.apache.org/incubator/NoNameYetProposal

That's what you get for employing reuse tactics -- gmail remembers the
original URL.  I've been caught by this before, so I thought I had taken
appropriate action to avoid this behaviour, but sadly not so, apologies.
Kelvin

On 31/01/2008, kelvin goodson <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> We've posted an Apache Incubator proposal onto the incubator wiki
>
> http://wiki.apache.org/incubator/NoNameYetProposal
>
> We haven't got a good name yet,  SandStorm is a contender, as is Snowdon
>
> Suggestions and comments welcome,
>
> Kelvin.
>
> <http://wiki.apache.org/incubator/ThriftProposal>

[Proposal] NoNameYet

[kelvin goodson]

Hi all,

We've posted an Apache Incubator proposal onto the incubator wiki

http://wiki.apache.org/incubator/NoNameYetProposal

We haven't got a good name yet,  SandStorm is a contender, as is Snowdon

Suggestions and comments welcome,

Kelvin.

Re: [VOTE] Graduate Tuscany as a top level project

[kelvin goodson]

Looks good to me.

Kelvin.

On 18/10/2007, ant elder <[EMAIL PROTECTED]> wrote:
> On 10/17/07, Simon Nash <[EMAIL PROTECTED]> wrote:
> 
>
> I wonder if we could shorten this just a little.  How about:
> >
> > "...establish a Project Management Committee charged with the creation
> > and maintenance of open-source software for distribution at no charge
> > to the public, that simplifies the development, deployment and management
> > of distributed applications built as compositions of service components.
> > These components may be implemented with a range of technologies and
> > connected using a variety of communication protocols. This software will
> > implement relevant open standards including, but not limited to, the
> > SCA and SDO standards defined by the OASIS OpenCSA member section."
>
>
> That sounds ok to me, is everyone else happy with these words?
>
>...ant
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANNOUNCE] Apache Tuscany Java SDO 1.0-incubating released

[kelvin goodson]

The Apache Tuscany team are pleased to announce the 1.0-incubating release
of the Java SDO project.

This project provides an implementation of the SDO 2.1 specification
[1] and this is our first release to provide full coverage of the
specification. In addition to completing the few remaining SDO 2.1
features there are a number of new features relating to XML
serialization, new support for handling dynamic derivation from static
classes and improvement to the sample programs. For the full change
history take a look at [2]

To download SDO Java or for more information about the release go to:
http://incubator.apache.org/tuscany/sdo-java-releases.html

Apache Tuscany welcomes your help. Any contribution, including code,
testing, improving the documentation, or bug reporting is always
appreciated. For more information on how to get involved in Apache Tuscany
visit the website at: http://incubator.apache.org/tuscany.

Thank you for your interest in Apache Tuscany!
The Apache Tuscany Team.
---

Tuscany is an effort undergoing incubation at the Apache Software Foundation
(ASF), sponsored by the Apache Web services PMC. 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.


[1] 
http://osoa.org/download/attachments/36/Java-SDO-Spec-v2.1.0-FINAL.pdf?version=1
[2] 
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating/distribution/src/main/release/RELEASE_NOTES

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT] Vote to release Apache Tuscany SDO Java 1.0-incubating

[kelvin goodson]

The vote to release Apache Tuscany SDO 1.0-incubating has completed
with 5 +1 votes being cast (3 IPMC binding) and no -1s (see the
tuscany-dev list vote thread [1] and the incubator-general vote
approval thread [2]).  Thank you for reviewing and voting.

I will therefore proceed with the deployment and announcement.

Kelvin.

[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg21169.html
[2] http://www.mail-archive.com/general@incubator.apache.org/msg14882.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Approve the release of Tuscany Java DAS beta1 (1.0-incubating-beta1)

[kelvin goodson]

I filed a JIRA on the documentation for the maven assembly plugin for
this, http://jira.codehaus.org/browse/MASSEMBLY-229, noting that the
requirement for a leading 0 in order to qualify the permissions
definition as being an octal number was inconsistent with the unix
chmod command.  Since then I have also realised it is inconsistent
with other maven file styles, such as the default permissions on the
server stanza in the settings.xml file.

If you do have some 755 style entries in your
assembly descriptors then they need to be changed to
0755 style to get them to do what you want.

Regards, Kelvin.

On 08/08/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> On 8/7/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
> > The Apache Tuscany project request IPMC permission to release the Java
> > DAS beta1 (1.0-incubating-beta1).
>
> hi luciano
>
> i think that you may have the same issues with permissions as kelvin
> (see 
> http://mail-archives.apache.org/mod_mbox/incubator-general/200708.mbox/[EMAIL 
> PROTECTED])
>
> - robet
>
> -
> 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]

[VOTE] Approve the release of Tuscany SDO Java 1.0-incubating (release candidate 4)

[kelvin goodson]

The Tuscany project requests permission of the IPMC to release the SDO
Java 1.0-incubating release. The vote thread is here ...

http://www.mail-archive.com/[EMAIL PROTECTED]/msg21169.html

Since this is a small delta on the RC3 for this release (see the
detailed information below) I crave the indulgence of the IPMC to
review this release in parallel with the Tuscany vote thread in order
that I can make the release very shortly after after the requisite 72
hours.

Changes in the RC4 release candidate from the RC3 candidate
===
To assist those who have looked at RC3,  I have included links to all
the changes in [4a,4b,4c] below

-- The permissions on unix jar files have been fixed
-- Some out of date references to the use of EMF 2.2.2 have been
updated to 2.2.3
-- The DISCLAIMER files,  which were manually inserted into RC3 during
the lifetime of the vote thread are now placed there in RC4 by the
build process
-- A tiny typographical error in the RELEASE_NOTES file has been fixed
===


The release candidate RC4 for Tuscany Java SDO archive distribution
files are posted at [1]
The release audit tool (rat) files and associated exceptions are
posted at [1] also
The maven repository artifacts are posted in a staging repository [2]
The tag for the source code is at [3]

The release notes for this release are attached below

It looks OK to me so here's my +1

Regards, Kelvin.

[1] http://people.apache.org/~kelvingoodson/sdo_java/1.0-incubating/RC4/

[2] http://people.apache.org/~kelvingoodson/repo/org/apache/tuscany/sdo/

[3] 
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating/

[4a] http://svn.apache.org/viewvc?view=rev&revision=563090

[4b] http://svn.apache.org/viewvc?view=rev&revision=563099

[4c] http://svn.apache.org/viewvc?view=rev&revision=563113



=

Service Data Objects (SDO) Java version 1.0-incubating Release Notes

The Service Data Objects (SDO) API simplifies and unifies Service
Oriented Architecture
(SOA) data access and code.

SDO offers both a static and a dynamic programming model for data access.
Choosing to generate static classes to represent your data model gives you
the ease and intuitive nature of the static programming model,  backed up
by the power of the dynamic model too.

SDO also offers the capacity to track changes to data. If a graph of data
includes a change summary property, then additions, modifications, and deletions
made to the graph within the scope of that change summary will be recorded.

What's new in this Release
==

Apache Tuscany's SDO Java Release 1.0-incubating is the first such release
with full coverage of the SDO 2.1 specification.

In addition to adding the few remaining SDO 2.1 features not included in the
1.0-incubating-beta1 release and fixing a number of bugs (see below for detail)
there are a number of new features relating to XML serialization, and new
support for handling dynamic derivation from static classes.  There has also
been significant focus on making the SDO sample programs more accessible.

For previous revision history, take a look at
http://svn.apache.org/viewvc/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/sdo/distribution/RELEASE_NOTES.txt

SDO Java 1.0-incubating is a superset of previous SDO
1.0-incubating-beta1 release.
Anything in 1.0-incubating-beta1 is also in 1.0-incubating, but
1.0-incubating contains
features and bugfixes not present in 1.0-incubating-beta1 release.

Downloading
===

Please visit  http://incubator.apache.org/tuscany/sdo-java-releases.html

Binary Artifact Changes
===

PLEASE NOTE that
Since the 1.0-incubating-beta release the following binary artifacts
have been renamed

The maven groupId of the SDO API binary artifact has changed from
"commonj" to "org.apache.tuscany.sdo"

The maven artifactId for the SDO API binary artifact has changed from
"sdo-api-r2.1 " to "tuscany-sdo-api-r2.1"

The jar file containing the SDO API has a new "tuscany-" prefix,  so what was ..
sdo-api-r2.1-1.0-incubating-beta1.jar in the beta1 release becomes
tuscany-sdo-api-r2.1-1.0-incubating.jar in this release.

In addition a new maven artifact and jar has appeared.

maven groupId=org.apache.tuscany.sdo
maven artifactId=tuscany-sdo-lib
jar archive=tuscany-sdo-lib-1.0-incubating

This artifact provides a cleear distinction between Tuscany SDO
implementation,  and the Tuscany
API which extends the SDO API.  See the javadoc contained in the
binary release for details of
the function provded by this artifact.


New Features and Fixes
==

For more detail on these fixes and features please see ...
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310210&fixfor=12312521&resolution=1&sorter/field=issuekey&sorter/order=DESC&sorter/field

Re: [VOTE] Approve the release of Tuscany SDO Java 1.0-incubating

[kelvin goodson]

The issue was that the maven assembly plugin doesn't treat
644 in the way I would have expected it to (-rw-r--r--)
and requires 0644 to achieve the desired result.
This didn't show up when I tested the distribution on linux as I ran it as
root, for whom the samples run fine.

I have taken the opportunity to fix up properly the DISCLAIMER files that I
manually inserted into this release candidate and to make a couple of minor
tweaks of things I noticed while making these fixes.  I will start another
vote thread on a new release candidate RC4.

Regards, Kelvin.

On 31/07/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> On 7/29/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
> > The Tuscany project requests permission of the IPMC to release the SDO
> > Java 1.0-incubating release.
> > The tuscany-dev list vote passed with 5+1s (2 IPMC binding), see ref [0]
below
> > The release candidate RC3 for Tuscany Java SDO archive distribution
> > files are posted at [1]
> > The release audit tool (rat) files and associated exceptions are
> > posted at [1] also
> > The maven repository artifacts are posted in a staging repository [2]
> > The tag for the source code is at [3]
>
> major issue
> -
>
> apache-tuscany-sdo-1.0-incubating.zip has permission issues. in
> particular, the lib subdirectory contains write only jars. not sure
> what's gone wrong but the zip is unusable on macOSX or *nix.
>
> otherwise good
>
> comments and suggestions (not normative)
> ---
>
> maven/plugin.xml seems to lack header or generation mark. suspect that
> this is that old maven bug...
>

Re: [VOTE] Approve the release of Tuscany SDO Java 1.0-incubating

[kelvin goodson]

Robert,
  thanks for looking at this.  I have just returned from a break and
investigated the permissions issue.  I tested the execution of samples
on linux,  but because I had set up a new machine for this purpose I
did it as root.  There I see the permission on the jars as --wr-T
(not sure what the T is) and the samples run fine.  Now that I have
run the samples as an ordinary I see the permissions as --wr-- and
the execution of the samples fails.  I will look into a solution for
this now.

Kelvin.

On 31/07/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> On 7/29/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
> > The Tuscany project requests permission of the IPMC to release the SDO
> > Java 1.0-incubating release.
> > The tuscany-dev list vote passed with 5+1s (2 IPMC binding), see ref [0] 
> > below
> > The release candidate RC3 for Tuscany Java SDO archive distribution
> > files are posted at [1]
> > The release audit tool (rat) files and associated exceptions are
> > posted at [1] also
> > The maven repository artifacts are posted in a staging repository [2]
> > The tag for the source code is at [3]
>
> major issue
> -
>
> apache-tuscany-sdo-1.0-incubating.zip has permission issues. in
> particular, the lib subdirectory contains write only jars. not sure
> what's gone wrong but the zip is unusable on macOSX or *nix.
>
> otherwise good
>
> comments and suggestions (not normative)
> ---
>
> maven/plugin.xml seems to lack header or generation mark. suspect that
> this is that old maven bug...
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Approve the release of Tuscany SDO Java 1.0-incubating

[kelvin goodson]

The Tuscany project requests permission of the IPMC to release the SDO
Java 1.0-incubating release.
The tuscany-dev list vote passed with 5+1s (2 IPMC binding), see ref [0] below
The release candidate RC3 for Tuscany Java SDO archive distribution
files are posted at [1]
The release audit tool (rat) files and associated exceptions are
posted at [1] also
The maven repository artifacts are posted in a staging repository [2]
The tag for the source code is at [3]

Thank you

Kelvin

[0] http://www.mail-archive.com/[EMAIL PROTECTED]/msg20827.html
(Note, I have taken this mid-thread link from the archive since for
unknown reasons the link to the archived root of the thread does not
display all posts in the displayed hierarchy at the bottom of the
page.
[1] http://people.apache.org/~kelvingoodson/sdo_java/1.0-incubating/RC3/
[2] http://people.apache.org/~kelvingoodson/repo/org/apache/tuscany/sdo/
[3] 
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Notice of Tuscany vote for new Committer

[kelvin goodson]

Please can I make another appeal to IPMC members to consider the referenced
vote for karma for Fuhwei and cast their binding votes.  We have consensus
from the project itself,  but we need the IPMC members binding votes before
we can proceed.

Regards, Kelvin.

On 03/07/07, kelvin goodson <[EMAIL PROTECTED]> wrote:


Could I bring this notification of a vote to the attention of the IPMC
please. We have 11 +1s, no -1s but only one IPMC binding vote.  We need a
couple more IPMC+1s to take this through please.

Regards,Kelvin.

On 27/06/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
>
> Tuscany is having a vote to give Committer status to Fuhwei Lwo on the
> tuscany-dev list [1].  We invite IPMC members to cast their binding votes.
>
>
> [1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg19275.html
>
>
> Regards, Kelvin Goodson.
>

Re: CLAs

[kelvin goodson]

The "new committers" page [1] references the link that you show as the place
to go to check. It mentions that it is generated daily from the
iclas.txtfile,  which I believe is the definitive document but has
limited access.

Kelvin.
[1] http://www.apache.org/dev/pmc.html#newcommitter

On 09/07/07, Luciano Resende <[EMAIL PROTECTED]> wrote:


What's the right/official place to verify if someone has a CLA in
place with Apache ? I'm looking into [1] but can't find the names I'm
looking for, even though the persons have faxed the CLAs twice.

[1] http://people.apache.org/~jim/committers.html

--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Notice of Tuscany vote for new Committer

[kelvin goodson]

Could I bring this notification of a vote to the attention of the IPMC
please. We have 11 +1s, no -1s but only one IPMC binding vote.  We need a
couple more IPMC+1s to take this through please.

Regards,Kelvin.

On 27/06/07, kelvin goodson <[EMAIL PROTECTED]> wrote:


Tuscany is having a vote to give Committer status to Fuhwei Lwo on the
tuscany-dev list [1].  We invite IPMC members to cast their binding votes.


[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg19275.html


Regards, Kelvin Goodson.

Notice of Tuscany vote for new Committer

[kelvin goodson]

Tuscany is having a vote to give Committer status to Fuhwei Lwo on the
tuscany-dev list [1].  We invite IPMC members to cast their binding votes.


[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg19275.html


Regards, Kelvin Goodson.

Re: 3rd party dependencies that don't provide maven binary artifacts

[kelvin goodson]

Hi Guillame,
 thanks for the tip.  Could you post the reference [1] that you
referred to please?

Regards, Kelvin.

On 25/06/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

I think you can just create a JIRA at [1] so that your dependencies
will be uploaded in the public repository.
The public maven repository is handled by the maven guys.

I guess another way is to make an archive of your local repository
and store it in a publicly available location so that one can always
rebuild the release if needed.  I know maven has a feature to create
this zip file, but I can't recall where.

Cheers,
Guillaume Nodet

kelvin goodson wrote:
> How can an Apache project robustly handle the situation where 3rd
> party dependencies don't provide maven binary artifacts?  In
> particular, when an Apache release is made,  we need to be sure that
> the 3rd party dependencies are available for as long as the release is
> available.
>
> Regards, Kelvin.
>
> -
> 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]

3rd party dependencies that don't provide maven binary artifacts

[kelvin goodson]

How can an Apache project robustly handle the situation where 3rd
party dependencies don't provide maven binary artifacts?  In
particular, when an Apache release is made,  we need to be sure that
the 3rd party dependencies are available for as long as the release is
available.

Regards, Kelvin.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: missing SDO announce

[kelvin goodson]

Jukka,
 thanks,  I have reposted the note in plain text format
Kelvin.

On 18/05/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:


Hi,

On 5/18/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
> I tried to announce the 1.0-incubating-beta1 release of Tuscany's SDO
> Java earlier in the week [1],  but I haven't seen it appear on the
announce
> mailing list archive,  or pop up in my newsfeed reader.  I did send it
from
> my apache.org email address;  are there any other gotchas?  I couldn't
find
> guidance in [2]. I tried sending emails to announce-help, announce-faq
and
> announce-info,  but these don't send back anything useful.

I'm one of the moderators of the announce list, but didn't approve the
message since it was HTML mail. I actually don't know the exact
policies regarding HTML mail on the announce mailing list, so for now
I just deferred to let other moderators decide what to do with the
message. Apparently others either didn't notice the moderation request
or had similar concerns.

If you resend the announcement as plain text, I will approve it ASAP.

BR,

Jukka Zitting

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

missing SDO announce

[kelvin goodson]

Hi,
  I tried to announce the 1.0-incubating-beta1 release of Tuscany's SDO
Java earlier in the week [1],  but I haven't seen it appear on the announce
mailing list archive,  or pop up in my newsfeed reader.  I did send it from
my apache.org email address;  are there any other gotchas?  I couldn't find
guidance in [2]. I tried sending emails to announce-help, announce-faq and
announce-info,  but these don't send back anything useful.

Kelvin.

[1]
http://permalink.gmane.org/gmane.comp.apache.webservices.tuscany.devel/17841
[2] http://www.apache.org/dev/release-publishing.html

Re: [Vote] Ratify the release of Apache Tuscany SDO 1.0-incubating-beta1

[kelvin goodson]

Niall,
 many thanks for the fix.  That's really helpful.  With regards to the
license issue,  in the future I believe OSOA will publish the SDO APIs, in a
maven repository,  but that's not the case yet,  and we need these artifacts
to publish an SDO release.  I believe that we are compliant with the Apache
"Treatment of 3rd Party Works" policy in [1] as discussed in [2].  The
discussions we have had in the Tuscany community [3][4] all suggest the
course of action of releasing as we are at the moment,  with a view to
shifting the dependency onto OSOA provided artifacts when they are
available.

Many thanks,  Kelvin.

[1] http://www.apache.org/legal/src-headers.html
[2]
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200607.mbox/[EMAIL 
PROTECTED]
[3] http://www.mail-archive.com/[EMAIL PROTECTED]/msg17270.html
[4] http://www.mail-archive.com/[EMAIL PROTECTED]/msg17442.html



On 14/05/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:


Ant refers to the need to "clarify the use of the OSOA licensed code"
in the following message:

  http://www.mail-archive.com/[EMAIL PROTECTED]/msg17270.html:

Not sure whats meant exactly by clarify - but sounds to me like
something that should be done before a release?

One minor nitpick with the release is that the MANIFEST files in the
"impl" and "tools" jars have an Implementation-Version of
"incubating-M3" rather than "1.0-incubating-beta1" - would be better
to have the version no. automatically generated, otherwise its a
potential error for every release. I've created a possible patch for
this:

https://issues.apache.org/jira/browse/TUSCANY-1284

Otherwise looks good to me.

Niall

On 5/2/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
> The Tuscany community held a vote to release Apache Tuscany SDO version
> 1.0-incubating-beta; see ref [0] below.
> Please vote to ratify this release.
>
> The release candidate RC1 for Tuscany Java SDO beta1 archive
distribution
> files are posted at [1]
> The maven repository artifacts are posted in a staging repository [2]
> The release audit tool (rat) files and associated exceptions are
attached to
> the jira under which the release work was done [3].
> The tag for the source code is at [4]
> Changes in this release are shown in [5]
>
> [0] http://www.mail-archive.com/[EMAIL PROTECTED]/msg17099.html
> [1] http://people.apache.org/~kelvingoodson/sdo_java/beta1/RC1/
> [2] http://people.apache.org/~kelvingoodson/repo/org/apache/tuscany/sdo/
> [3] http://issues.apache.org/jira/browse/TUSCANY-1171
> [4]
>
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/
> [5]
>
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/sdo/distribution/RELEASE_NOTES.txt
>
> ---
> Kelvin.
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] Ratify the release of Apache Tuscany SDO 1.0-incubating-beta1

[kelvin goodson]

Thanks guys,  but were still looking for one more vote,  since Paul's 2 +1s
won't carry it I think  ;-)

Kelvin.

On 11/05/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:


+1 from me.

Paul

On 5/2/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
> The Tuscany community held a vote to release Apache Tuscany SDO version
> 1.0-incubating-beta; see ref [0] below.
> Please vote to ratify this release.
>
> The release candidate RC1 for Tuscany Java SDO beta1 archive
distribution
> files are posted at [1]
> The maven repository artifacts are posted in a staging repository [2]
> The release audit tool (rat) files and associated exceptions are
attached to
> the jira under which the release work was done [3].
> The tag for the source code is at [4]
> Changes in this release are shown in [5]
>
> [0] http://www.mail-archive.com/[EMAIL PROTECTED]/msg17099.html
> [1] http://people.apache.org/~kelvingoodson/sdo_java/beta1/RC1/
> [2] http://people.apache.org/~kelvingoodson/repo/org/apache/tuscany/sdo/
> [3] http://issues.apache.org/jira/browse/TUSCANY-1171
> [4]
>
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/
> [5]
>
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/sdo/distribution/RELEASE_NOTES.txt
>
> ---
> Kelvin.
>


--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Vote] Ratify the release of Apache Tuscany SDO 1.0-incubating-beta1

[kelvin goodson]

The Tuscany community held a vote to release Apache Tuscany SDO version
1.0-incubating-beta; see ref [0] below.
Please vote to ratify this release.

The release candidate RC1 for Tuscany Java SDO beta1 archive distribution
files are posted at [1]
The maven repository artifacts are posted in a staging repository [2]
The release audit tool (rat) files and associated exceptions are attached to
the jira under which the release work was done [3].
The tag for the source code is at [4]
Changes in this release are shown in [5]

[0] http://www.mail-archive.com/[EMAIL PROTECTED]/msg17099.html
[1] http://people.apache.org/~kelvingoodson/sdo_java/beta1/RC1/
[2] http://people.apache.org/~kelvingoodson/repo/org/apache/tuscany/sdo/
[3] http://issues.apache.org/jira/browse/TUSCANY-1171
[4]
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/
[5]
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/sdo/distribution/RELEASE_NOTES.txt

---
Kelvin.

Re: [VOTE] Andy Grove for Tuscany Committer ------ needs 2 more IPMC votes please

[kelvin goodson]

Many thanks for your prompt attention.  So now we have 15+1s, 1 non binding,
3 IPMC binding and no -1s  I think we can confidently declare this vote
closed.

Regards, Kelvin.

On 01/05/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:


On 5/1/07, kelvin goodson <[EMAIL PROTECTED]> wrote:

> ...Please take a look at the summary of
> Andy's activities at the head of the vote thread and cast your vote...

+1

-Bertrand

Fwd: [VOTE] Andy Grove for Tuscany Committer ------ needs 2 more IPMC votes please

[kelvin goodson]

IPMC members,

 Tuscany held a vote to  make Andy Grove a committer [1].  In the 13 +1s
there was one IPMC binding vote,  so I understand we need to get a couple of
those before the vote is closed.  Please take a look at the summary of
Andy's activities at the head of the vote thread and cast your vote.

Regards, Kelvin.

[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg16920.html

-- Forwarded message --
From: kelvin goodson <[EMAIL PROTECTED]>
Date: 26-Apr-2007 09:40
Subject: Re: [VOTE] Andy Grove for Tuscany Committer
To: tuscany-dev <[EMAIL PROTECTED]>

That's voting time up and with my +1 that makes 13 +1s (including 1 non
binding) and no -1s so --  Welcome Andy.

Next steps are defined in [1],  If you haven't already submitted a
Contributor License Agreement (CLA) then this need to be done and
acknowledged by ASF before they will create a user id for you. When your CLA
has been acknowledged your name will appear in [2] and will not be
italicized.

Please let me know an apache userid you'd like to use (see [2] for those
that have been taken), along with full name and the email address you want
for forwarding (this must be the same email address as on the CLA).

[1] http://www.apache.org/dev/pmc.html#newcommitter
[2] http://people.apache.org/~jim/committers.html
<http://people.apache.org/%7Ejim/committers.html>

Kelvin.

On 23/04/07, kelvin goodson <[EMAIL PROTECTED]> wrote:


Andy has taken part in SDO Java and C++ discussions since November of
2006, in particular in the area of the Community Test Suite (CTS).  As some
of you may not follow this closely, I've distilled quite a bit of detail
from the lists to show Andy's participation.  He ...


   - been active in creating and resolving numerous JIRAs
   - did some of the work of the initial drop of tests to the SDO Java
   CTS from Rogue Wave and in the CTS infrastructure design, including ensuring
   vendor independence.
   - has discovered and offered solutions to a number of anomalies
   between the CTS and the specification
   - developed and contributed tests for testing XML schema choice
   function.
   - provided good insights to the required and permitted behaviours of
   implementations when dealing with elements which are nillable
   - has taken part in discussions for an M1 release of the CTS
   - Initiated discussions on DataHelper formats wrt dates and
   durations
   - developed new test cases for spec section 9.10 -- XML without
   Schema to SDO Type and Property
   - solicited input from the Tuscany community with respect to the
   equivalence or otherwise of null URIs versus empty strings,  in order to
   feed back to the spec group
   - took a significant part in discussions of how to ensure the CTS is
   test harness agnostic, and provided patches to update tests to assist in
   this goal
   - contributed a set of tests for XSD complex types
   - provided support to the community with problems running the CTS
   and with insights into new Junit features

Aside from Tuscany, Andy has been active in the SDO Java and C++
specification efforts, and I think he will be a great asset to the project.

Regards, Kelvin.

Re: Posting release candidate artifacts to incubator repo

[kelvin goodson]

Upayavira,
 OK,  thanks for the clarification.
Kelvin.

On 24/04/07, Upayavira <[EMAIL PROTECTED]> wrote:


kelvin goodson wrote:
> Robert, thanks for that.  Can I just clarify something please.  I may be
> mistaken but I thought I had understood that the incubator repo is not
> mirrored anywhere.  If this is true one could interpret from your
response
> that publishing artifacts that have not yet been approved to the
incubator
> repo is a special case.  If so it would mean that the difficulties of
> moving
> artifacts from a staged repo to the real repo would be circumvented.

Regardless of mirroring, an incubator repo implies that it contains
releases made by the incubator PMC. A release candidate as you are
talking about has NOT been made by the IPMC, thus cannot go in that
repo. It should go somewhere private, where you can make it available
just to those who will be voting upon it. Until that vote, it is just a
tarball you happened to make. Once the vote is complete, it is an
artifact that can go into official ASF repositories.

As Robert suggested, creating mini repo in your home directory on
people.a.o is really the best bet.

Regards, Upayavira


> On 23/04/07, robert burrell donkin <[EMAIL PROTECTED]>
wrote:
>>
>> On 4/23/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
>> > I had some recent comments on a release candidate I posted for
>> > consideration/voting [1].
>> > In particular the comment ...
>> >
>> > - There are no SDO artifact jars to review, are the SDO jars going
>> to be
>> > installed to the Apache maven repository?
>> >
>> > I want to post my release artifacts to the incubator repo but I'm
>> unsure
>> > whether this is OK.
>>
>> i'm not sure i know the official answer but i do have a strong personal
>> opinion
>>
>> as a release manager,  i would be uncomfortable posting an artifact
>> anywhere that is mirrored before a release vote. there are a couple of
>> reasons behind this opinion:
>>
>> * in the event of an IP issue with the release, the manager can only
>> be helped by apache if they are acting on the instructions of apache.
>> this is only possible after a release vote.
>> * i've had bad experiences in the past trying to recall bad releases
>> from maven repositories
>>
>> AIUI it would be possible to set up a local repository in your home
>> directory. others can then configure maven to use this. that's the
>> approach that i would take.
>>
>> - 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: Posting release candidate artifacts to incubator repo

[kelvin goodson]

Robert, thanks for that.  Can I just clarify something please.  I may be
mistaken but I thought I had understood that the incubator repo is not
mirrored anywhere.  If this is true one could interpret from your response
that publishing artifacts that have not yet been approved to the incubator
repo is a special case.  If so it would mean that the difficulties of moving
artifacts from a staged repo to the real repo would be circumvented.

Kelvin.

On 23/04/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:


On 4/23/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
> I had some recent comments on a release candidate I posted for
> consideration/voting [1].
> In particular the comment ...
>
> - There are no SDO artifact jars to review, are the SDO jars going to be
> installed to the Apache maven repository?
>
> I want to post my release artifacts to the incubator repo but I'm unsure
> whether this is OK.

i'm not sure i know the official answer but i do have a strong personal
opinion

as a release manager,  i would be uncomfortable posting an artifact
anywhere that is mirrored before a release vote. there are a couple of
reasons behind this opinion:

* in the event of an IP issue with the release, the manager can only
be helped by apache if they are acting on the instructions of apache.
this is only possible after a release vote.
* i've had bad experiences in the past trying to recall bad releases
from maven repositories

AIUI it would be possible to set up a local repository in your home
directory. others can then configure maven to use this. that's the
approach that i would take.

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Posting release candidate artifacts to incubator repo

[kelvin goodson]

I had some recent comments on a release candidate I posted for
consideration/voting [1].
In particular the comment ...

- There are no SDO artifact jars to review, are the SDO jars going to be
installed to the Apache maven repository?

I want to post my release artifacts to the incubator repo but I'm unsure
whether this is OK.
Refs [2] and [3] discuss posting artifacts which have not passed the voting
process,  but I can not derive from them a conclusion whether this is OK or
not.
Please can you advise if I am OK to go ahead and post such artifacts to the
incubator repo.

[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg16525.html
[2] http://marc.info/?t=11760705873&r=1&w=2
[3] http://marc.info/?l=incubator-general&m=117606976901938&w=2

Fwd: New dependency on GroboUtils, and hence MIT license

[kelvin goodson]

I think I should perhaps have asked the attached question here ...

-- Forwarded message --
From: kelvin goodson <[EMAIL PROTECTED]>
Date: 16-Mar-2007 16:44
Subject: New dependency on GroboUtils, and hence MIT license
To: tuscany-dev 

http://issues.apache.org/jira/browse/TUSCANY-1179 has a useful concurrency
test case attached to it which would introduce a test scope dependency on
GroboUtils, from http://groboutils.sourceforge.net/,  and therefore on the
MIT license (http://groboutils.sourceforge.net/license.html ).  Note, we
don't need to distribute this in a release,  but anyone building and testing
SDO would download it from a maven repository as part of the build/unit test
process. The license looks OK to be, but having dug around a bit I'm still
not completely confident I can introduce this dependency. Is there a
precedent for using this license in Tuscany?  Do I need IP clearance, and if
so how do I ask for it?

Regards, Kelvin.

Re: JIRA "patch available" column

[kelvin goodson]

Marshall,
 thanks for that pointer.  I've now got a little bit further,  but not
quite far enough.  So given that there are examples of people out there that
have got this right,  I'd like to be able to mimic their solutions exactly.
It seems to me that the solution will require the addition of a custom
field.  Considering where i have got so far,  there is distinct possibility
of creating a half baked solution that we would want to alter in the future.

So far I have set up a dummy server to play with, within my company's
firewall and added a custom field,  but the data type of my custom "Patch
Available" field  is "Multi Checkboxes",  and I have only defined a single
checkbox element "Patch Available". I would have preferred a simple boolean
type,  but that doesn't seem to be available in the set of types (
http://www.atlassian.com/software/jira/docs/latest/customfields/overview.html
).

Also, it seems so far that I can only have this field altered by someone
with jira-developer access or greater after the jira has been created (a
jira-user seems to have authority to set the field value at origination).  I
would like for jira-users to be able to set this flag  on supplying a
patch,  but perhaps that just doesn't fit the ACL model,  so we may just
have to live with committers updating the jira on seeing an incoming patch.

I don't want to alter our live JIRA system with a second rate solution,
since any improvements at a later stage would be likely to cause confusion
because there would have to be 2 differently named fields and users would
have to apply two separate filters in order to search for such jiras.

If you have any ideas that would be really helpful, thanks.

--
Kelvin

On 23/02/07, Marshall Schor <[EMAIL PROTECTED]> wrote:



http://www.atlassian.com/software/jira/docs/v3.7.2/navigatorviews.html?clicked=jirahelp

scroll down to "Customizing your Issue Navigator columns"

-Marshall Schor

kelvin goodson wrote:
> I'd really like to update the Tuscany JIRA environment to have a "patch
> available" column (similar to Geronimo's here --
>
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10220&status=1
)
>
> but have no idea how to do it.
> Can anyone point to me some infor please?
>
> Regards, Kelvin.
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

JIRA "patch available" column

[kelvin goodson]

I'd really like to update the Tuscany JIRA environment to have a "patch
available" column (similar to Geronimo's here --
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10220&status=1)
but have no idea how to do it.
Can anyone point to me some infor please?

Regards, Kelvin.

missing announcement on announce mailing list

[kelvin goodson]

I sent a note to announce?apache.org a week ago to announce Tuscany's SDO
Java M2 release.  I have just got back the  following message


Hi! This is the ezmlm program. I'm managing the
[EMAIL PROTECTED] mailing list.

I'm sorry, the list moderators for the announce list
have failed to act on your post. Thus, I'm returning it to you.
If you feel that this is in error, please repost the message
or contact a list moderator directly.


but I don't know who the moderators are.  Can someone help please?

Regards, Kelvin Goodson.

[ANNOUNCE] Tuscany SDO Java Milestone 2 Release

[kelvin goodson]

The Apache Tuscany community is pleased to announce its Milestone 2 release
of SDO (Service Data Objects).

You can download binary and source distributions from:
http://incubator.apache.org/tuscany/downloads.html

For further information, visit our web site at:
http://incubator.apache.org/tuscany

For detailed information about what's new in this release see
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubator-M2/distribution/RELEASE_NOTES.txt

Incubation

Tuscany is an effort undergoing incubation at the Apache Software Foundation
(ASF), sponsored by the Web Services PMC.

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.

Please feel free to send any feedback to our mailing lists:
tuscany-dev@ws.apache.org
tuscany-user@ws.apache.org

Any contribution in the form of coding, testing, improving the
documentation, and reporting bugs is always welcome. For more information on
how to get involved with the development of Tuscany, visit our Get Involved
page at:
http://incubator.apache.org/tuscany/get-involved.html


Thank you for your interest in Apache Tuscany!

Re: [VOTE] - Restarting the vote to --- Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts

[kelvin goodson]

Passed with +1 votes from rubys, farra and davanum and no -1s.
Thanks to all for reviewing and commenting.
Kelvin.

On 06/11/06, kelvin goodson <[EMAIL PROTECTED]> wrote:


I understand it is good practice to restart a vote if the vote thread
becomes heavy with discussion.  This is the case with the vote that was
begun at
http://www.mail-archive.com/general@incubator.apache.org/msg11201.html
which contains some issues raised and comments to address each of those
issues.

So please vote to ratify the Tuscany PPMC vote to release SDO for Java M2
artifacts at 
http://people.apache.org/~kelvingoodson/sdo_java/RC5a/<http://people.apache.org/%7Ekelvingoodson/sdo_java/RC5a/>which
 have been voted for by the Tuscany PPMC.

Vote thread:*
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg09797.html

Result thread:

http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg10046.html

Kind Regards, Kelvin.

Re: [VOTE] Ratify Tuscany PPMC vote to release DAS for Java M2 artifacts

[kelvin goodson]

> key ID 96324791 used to sign releases is not available from the usual
> public key server networks. please upload to pgp.mit.edu (web
> interface) or use gpg (to upload to any well known pubilc keyserver).


I had lodged this key at http://keyserver.veridis.com,  but wasn't sure if
this would be widely available.  I'm a novice in this field.  I have now
uploaded the key to pgp.mit.edo and I see 

C:\> gpg --search-keys goodson
gpg: searching for "goodson" from hkp server pgp.mit.edu
(1) Kelvin Goodson <[EMAIL PROTECTED]>
 1024 bit DSA key 96324791, created: 2006-10-17

Regards, Kelvin.


On 07/11/06, Luciano Resende <[EMAIL PROTECTED]> wrote:


One more thing, about the signatures,the public key for verifying the
signatures may be found in :
https://svn.apache.org/repos/asf/incubator/tuscany/KEYS

- Luciano Resende

On 11/6/06, Luciano Resende <[EMAIL PROTECTED]> wrote:
>
> Thanks Robert for looking into this, more comments inline...
> Please let me know if you have any further questions.
>
> On 11/6/06, robert burrell donkin <[EMAIL PROTECTED] >
wrote:
> >
> > On 11/5/06, Luciano Resende < [EMAIL PROTECTED]> wrote:
> > > The Tuscany PPMC has voted to Release DAS for Java API
Implementation
> > as
> > > part of the M2 release.
> > > In accordance with Incubator release procedures we are asking the
> > Incubator
> > > PMC to  approve this release.
> >
> > +0 (a couple of questions which i'd like answering before i can +1)
> >
> > please fix:
> > 
> >
> > md5 sums are not in the correct format. please delete all but the last
> > line. (AIUI they are read automatically by some scripts.) this does
> > not require a rebuild.
>
>
> The files should be in the right format now.
>
> questions
> > 
> >
> > sample-companyweb-1.0-incubator-M2.war lacks LICENSE and NOTICE files.
> > this means that it cannot be distributed as a raw artifact. is the
> > intention to ban this artifact from distribution via maven?
>
>
> LICENSE and NOTICE are available inside the war file at
> WEB-INF\classes\META-INF, please let me know if they are in the wrong
place.
>
>
> RAT:
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/das/1.0-incubator-M2/samples/testing/tomcat/datasource.xsl
> >
> > lacks a license header. is there a reason (for example, is it
> > generated) or is it just an oversight?
>
>
> This was an oversight on my part, I have created a JIRA and a patch was
> applied to the trunk.
> http://issues.apache.org/jira/browse/TUSCANY-900
>
> Would this be enough ?
>
>
> important (but can be fixed for next release)
> > -
> >
> > key ID 96324791 used to sign releases is not available from the usual
> > public key server networks. please upload to pgp.mit.edu (web
> > interface) or use gpg (to upload to any well known pubilc keyserver).
>
>
> Sure, the key is from kgoodson, that was of great help signing and
> uploading the DAS artifacts. I have forwarded this comment to him.
>
> stylistic (best practice)
> > ---
> >
> > release names can be a form of advertising and can also allow the
> > trademark to be used to prevent unauthorised jars being distributed
> > with similar names. so, i'd recommend ensuing all releases are
> > prefixed with 'apache-tuscany' when tuscany graduates. i have no
> > objection to using this naming in the incubator (though some people
> > may).
> >
> > the compressed archives unpack into the current directory. this is a
> > real PITA for most users and a bad practice. there are two good
> > approaches: either structure the release so that all  duistributions
> > unpack into the same directory (with name based on the release) in a
> > way that elegantly combines or have each unpack distribution into a
> > separate, meaningfully but uniquely named directory.
>
>
>
> I'm aware of this, and have submitted a patch to fix this in the trunk,
> but unfortunately it is not available in this release.
http://issues.apache.org/jira/browse/TUSCANY-886
>
>
> - robert
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

[VOTE] - Restarting the vote to --- Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts

[kelvin goodson]

I understand it is good practice to restart a vote if the vote thread
becomes heavy with discussion.  This is the case with the vote that was
begun at
http://www.mail-archive.com/general@incubator.apache.org/msg11201.html
which contains some issues raised and comments to address each of those
issues.

So please vote to ratify the Tuscany PPMC vote to release SDO for Java M2
artifacts at http://people.apache.org/~kelvingoodson/sdo_java/RC5a/ which
have been voted for by the Tuscany PPMC.

Vote thread:*
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg09797.html
Result thread:
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg10046.html

Kind Regards, Kelvin.

Re: [VOTE] - Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts

[kelvin goodson]

Hi,
 I wonder if I could draw your attention to this vote ratification please?
Nobody has raised any show-stopping objections to any of the content. On the
other hand,  nobody has voted yet. I have been reading all the helpful
suggestions made in this thread and I have been reporting back on my
activities in the light of those suggestions in my earlier posts to this
thread.

In addition to my other reports in this thread I have been following up the
MANIFEST suggestion for inclusion of the Application-Vendor-Id in the maven
users group. So that means that for all the issues raised I believe I have
either addressed and rectified them, or explained the current state, or made
active steps to pursue improving that state where I understand the points
raised, but don't currently understand how to rectify those points.

Can you let me know if ratification of this vote is dependent on any further
activity on my part please?

Best Regards, Kelvin.

On 01/11/06, kelvin goodson <[EMAIL PROTECTED]> wrote:


Robert, thanks for your comments.

I believe the tag issue is now resolved, by earlier notes on this thread.
(http://mail-archives.apache.org/mod_mbox/incubator-general/200610.mbox/[EMAIL 
PROTECTED]
)

The CCLA issue has also been resolved by jeremy boynes 
(http://www.mail-archive.com/tuscany-commits@ws.apache.org/msg00018.html
)

The MANIFEST requirement is an unknown quantity to me,  but I will
investigate.

For the most part the instances of files that you reference which do not
have license headers are that way intentionally since either they are
generated or because they are present for verification of test execution,
and must be equivalent to the data generated in the execution of the tests.
This is true of all of the files in the test/resources hierarchy that don't
have headers. There are some files that were in error in the samples
hierarchy which I have fixed up in the trunk as you asked.I missed these
when I ran rat against the source because we had a different source code
structure at that time. The files in the model directory are generated and
until now I had never looked inside them.  If anything I I had assumed that
thery were of a format that wouldn't take a comment.  I see now that the
.ecore file and the .genmodel files are generated XML.  so i have added
license headers to these two, but I can not modify the .mdl file without
risking breaking it.  I will investigate whether this file format has a
comment syntax i can use to apply a header to the file.

I looked at rearranging my source and binary distros in the way you
suggested.  The binary distro is the way it is (i.e. it unpacks into the
working directory) because of maven assembly plugin defaults.  I have tried
to figure out how to reconfigure maven to put a base directory into the
archive,  but it wasn't obvious from the assembly plugin documentation and
my attempts to play with the configuration failed.  The issue I have over
having a common base directory for the spec, impl and sample source
distributions is that as I understand it the root directory of the
distributions each need to contain a BUILDING.txt file.  Having a common
name for the root directory would cause one extraction to overwrite the
contents of the first.  I could move BUILDING.txt down to a 2nd level of
directory,  but that might not make it so obvious what to do with the
archives.  Any pointers as to how best to do this for the future would be
most welcome, thanks.

So the one remaining thing is the MANIFEST file issue.  In the interest of
expediting this release, would you be happy if I opened a JIRA for that
issue and committed to resolve it before a further release?

Best Regards, Kelvin.


On 28/10/06, robert burrell donkin < [EMAIL PROTECTED]> wrote:
>
> On 10/25/06, kelvin goodson <[EMAIL PROTECTED]> wrote:
> > The Tuscany PPMC has voted to release the SDO for Java API
> implementation as
> > part of the M2 release.
> > In accordance with Incubator release procedures we are asking the
> Incubator
> > PMC to
> > approve this release.
>
> reviewing http://people.apache.org/~kelvingoodson/sdo_java/RC5a/
> <http://people.apache.org/%7Ekelvingoodson/sdo_java/RC5a/>
> (since the email doesn't include the explicit reference)
>
> major
> ---
>
> no major issues
>
> there are a few minor questions that need clearing up in 'important'
> below. i'd be happy to see these issues resolved in the source without
> recutting the release provided that the provinance of these files is
> ok. (running RAT will give exact filenames.)
>
> important
> ---
> i can't find a tag in subversion. please take a tag next time (or
> explain your tag naming system if i've missed it).
>
> the files in 
http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/resources/
>
> appear to

Re: [VOTE] - Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts

[kelvin goodson]

Robert, thanks for your comments.

I believe the tag issue is now resolved, by earlier notes on this thread.
(http://mail-archives.apache.org/mod_mbox/incubator-general/200610.mbox/[EMAIL 
PROTECTED]
)

The CCLA issue has also been resolved by jeremy boynes
(http://www.mail-archive.com/tuscany-commits@ws.apache.org/msg00018.html
)

The MANIFEST requirement is an unknown quantity to me,  but I will
investigate.

For the most part the instances of files that you reference which do not
have license headers are that way intentionally since either they are
generated or because they are present for verification of test execution,
and must be equivalent to the data generated in the execution of the tests.
This is true of all of the files in the test/resources hierarchy that don't
have headers. There are some files that were in error in the samples
hierarchy which I have fixed up in the trunk as you asked.I missed these
when I ran rat against the source because we had a different source code
structure at that time. The files in the model directory are generated and
until now I had never looked inside them.  If anything I I had assumed that
thery were of a format that wouldn't take a comment.  I see now that the
.ecore file and the .genmodel files are generated XML.  so i have added
license headers to these two, but I can not modify the .mdl file without
risking breaking it.  I will investigate whether this file format has a
comment syntax i can use to apply a header to the file.

I looked at rearranging my source and binary distros in the way you
suggested.  The binary distro is the way it is (i.e. it unpacks into the
working directory) because of maven assembly plugin defaults.  I have tried
to figure out how to reconfigure maven to put a base directory into the
archive,  but it wasn't obvious from the assembly plugin documentation and
my attempts to play with the configuration failed.  The issue I have over
having a common base directory for the spec, impl and sample source
distributions is that as I understand it the root directory of the
distributions each need to contain a BUILDING.txt file.  Having a common
name for the root directory would cause one extraction to overwrite the
contents of the first.  I could move BUILDING.txt down to a 2nd level of
directory,  but that might not make it so obvious what to do with the
archives.  Any pointers as to how best to do this for the future would be
most welcome, thanks.

So the one remaining thing is the MANIFEST file issue.  In the interest of
expediting this release, would you be happy if I opened a JIRA for that
issue and committed to resolve it before a further release?

Best Regards, Kelvin.


On 28/10/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:


On 10/25/06, kelvin goodson <[EMAIL PROTECTED]> wrote:
> The Tuscany PPMC has voted to release the SDO for Java API
implementation as
> part of the M2 release.
> In accordance with Incubator release procedures we are asking the
Incubator
> PMC to
> approve this release.

reviewing http://people.apache.org/~kelvingoodson/sdo_java/RC5a/
<http://people.apache.org/%7Ekelvingoodson/sdo_java/RC5a/>
(since the email doesn't include the explicit reference)

major
---

no major issues

there are a few minor questions that need clearing up in 'important'
below. i'd be happy to see these issues resolved in the source without
recutting the release provided that the provinance of these files is
ok. (running RAT will give exact filenames.)

important
---
i can't find a tag in subversion. please take a tag next time (or
explain your tag naming system if i've missed it).

the files in 
http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/resources/

appear to be missing license headers. please conform that this is
either an oversight or that they are generated.

the status file is worrying: there are two CCLAs pending. please
confirm that this is either an oversight or that these CCLAs are not
pertinent to this material.

MANIFESTs are missing Implementation-Vendor-Id (yes, i know it's a
PITA and the various jarspecifications are a mess). best to add it if
you can do so without too much pain.

files in
http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/impl/model/
are missing license headers. please confirm that this was an oversight
or provide a reason why they don't need them.

a few files in 
http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/impl/src/test/resources/

are missing license headers. please confirm that this was an oversight
or provide a reason why they don't need them.

stylistic


the download directories are a bit of a hotch-potch. the binary
unpacks to the current directory, sample unpacks to samples, sdo impl
unpacks to sdo, sdo api to sdo-api. it's best to have a naming plan
and stick to it. releases which unpack to the current directory
irritate

Re: clarification on SF license and sandboxes

[kelvin goodson]

thanks,  i'll pursue that

On 01/11/06, Craig L Russell <[EMAIL PROTECTED]> wrote:


It's best practice to require that contributions be accompanied by
the checkbox to grant the license. I haven't seen any official Apache
policy guideline on this subject.

Is the contributor willing to re-attach the file to the JIRA, this
time with the checkbox ticked? That's the best way to handle it.

Craig

On Nov 1, 2006, at 6:47 AM, kelvin goodson wrote:

> Can anyone tell me if it's OK to put code into a sandbox that has been
> attached to a JIRA without granting ASF license?
>
> Thanks

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Re: [VOTE] - Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts

[kelvin goodson]

Bill,

  thanks for your comments.  I have made fixes in the trunk for the license
file suggestions you raise where I am certain of the required changes (
http://svn.apache.org/viewvc?view=rev&revision=470007)
and I have raised a JIRA (
http://issues.apache.org/jira/browse/TUSCANY-894) to make certain of
my new understanding that the CPL is no longer required
in our LICENSE file.

There is documentation in the binary distribution in the javadoc folder,
which is pointed to from the readme.html file.
There is documentation in the samples distribution in the site/apidocs
folder (not my choice of layout,  its what maven defines as the standard
location and I haven't been able to work out how to configure that)
There are instructions in the source distribution on how to build the
javadoc that is found in the binary and samples distributions.

Best Regards, Kelvin.


On 27/10/06, Bill Dudney <[EMAIL PROTECTED]> wrote:


Hi Kelvin,

The release includes the license and notice files but I don't see any
file pointing out the licenses of the individual jar files included
in the release.

The notice file is some what ambiguous on what is included under
which license. It refers to the EPL and CPL (both are fine AFAIKT
from [1]). But it seems like the notices of which jar is licensed
under which license should be more explicit [2].

Since none of the license stuff is board approved yet its not binding
(AFAIK) so take that for what its worth.

One other thing is the lack of docs, I could not find any.

TTFN,

-bd-

[1] http://people.apache.org/~cliffs/3party.html
[2] http://people.apache.org/~cliffs/3party.html#labeling

On Oct 25, 2006, at 11:09 AM, kelvin goodson wrote:

> The Tuscany PPMC has voted to release the SDO for Java API
> implementation as
> part of the M2 release.
> In accordance with Incubator release procedures we are asking the
> Incubator
> PMC to
> approve this release.
>
> Vote thread:*
> *http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg09797.html
> Result thread:
> http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg10046.html
>
> Regards, Kelvin Goodson.
> **


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

clarification on SF license and sandboxes

[kelvin goodson]

Can anyone tell me if it's OK to put code into a sandbox that has been
attached to a JIRA without granting ASF license?

Thanks

Re: [VOTE] - Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts

[kelvin goodson]

README file added at
https://svn.apache.org/repos/asf/incubator/tuscany/tags/README.txt
Regards, Kelvin.

On 28/10/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:


On 10/28/06, Luciano Resende <[EMAIL PROTECTED]> wrote:
> Just trying to help, the SDO tag is available here :
>
>
>
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubator-M2/

thanks

bit of an unconvention organisation but nothing wrong with that.
perhaps it might be useful to have  a short README in
https://svn.apache.org/repos/asf/incubator/tuscany/tags/

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] - Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts

[kelvin goodson]

The Tuscany PPMC has voted to release the SDO for Java API implementation as
part of the M2 release.
In accordance with Incubator release procedures we are asking the Incubator
PMC to
approve this release.

Vote thread:*
*http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg09797.html
Result thread:
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg10046.html

Regards, Kelvin Goodson.
**