Dims,
Do you know who I should speak to about obtaining write access to that repository?
The snapshots are really just head builds. Can we define a process where more stable builds are declared on a semi-regular basis?
WRT my other suggestions, once I get a few spare minutes I will look into creating a WS commons virtual component complete with a site, Jira, and mailing lists. I'll post back to [EMAIL PROTECTED] once I have a chance to look into this. If anyone else has time I'd be happy to get some help.
Lawrence Mandel
| Davanum Srinivas <[EMAIL PROTECTED]>
12/06/2005 11:02 PM
|
|
Lawrence,
- You should have write access to that repo.
- Snapshots are published every 6 hours
(http://cvs.apache.org/repository/ws-commons/jars/)
+1 to do all the things that you mentioned. Please feel free to take
ownership of the bits where you can help.
thanks,
dims
On 12/6/05, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
>
> I found a problem in XmlSchema which I'd like to fix but found that I don't
> have access to the repository. This lead me to what I think is a larger
> problem with the WS Commons projects. There is no information about these
> projects on the WS site, no bug tracking system, no regular builds, and no
> developers (publically) committed to this code.
>
> If we're to continue to have WS commons projects I'd like to suggest that
> either these be transformed into WS projects with their own sites, jira,
> etc., or that a page be added to the WS site that explains these common
> projects and provides references to the projects that own these common
> projects. (I'd still like to see public builds of these projects that other
> projects, such as Woden, can depend on.)
>
> Comments? Is someone already looking into some of these issues? If I'm way
> off here because I've missed some information please correct me. If this is
> the case we may just need to make the information more visible.
>
> Thanks,
>
> Lawrence Mandel
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
