Re: Project Prefix Issue!

Looking at the wiki.apache.org/xalan -- It looks like I used
"xalan_c-1.11" in the tables of distribution artifacts.

I will make the changes to my staging area, hopefully tomorrow!

Sincerely,
Steven J. Hathaway
Xalan Documentation Project


> Project Prefix Issue!
>
> The project prefix for distributions should be consistent.
>
>     Either use  "xalan_c-1.11" or "xalan-c-1.11"
>
> What do you recommend?
>
> Sincerely,
> Steven J. Hathaway
>
> On 10/21/2012 6:46 PM, Steven J. Hathaway wrote:
>> I mistyped the staging area
>>
>>   http://people.apache.org/~shathaway/files/dist/xalan-c
>>
>> Sorry for the inconvenience.
>>
>> Sincerely,
>> Steven J. Hathaway
>> Xalan Documentation Project
>>
>> On 10/21/2012 3:28 PM, shath...@e-z.net wrote:
>>> Greetings, Xalan-C/C++ V1.11 Team
>>>
>>> I have completed a staging area on my committer's website.
>>>
>>> Please review and comment.  If there are no objections to
>>> documentation and proposed release artifacts, I will ask
>>> for a vote next weekend.
>>>
>>> My Website: http://people.apache.org/~shathaway
>>>
>>> xalan-c Distro Staging: http://people.apache.org/files/dist/xalan-c
>>      Should Be: http://people.apache.org/~shathaway/files/dist/xalan-c
>>>
>>> Binary distributions:
>>>
>>>     Xalan-C for Windows VC71, VC80, VC90, VC100
>>>
>>>     Combined Xalan-C/Xerces-C for Windows VC71, VC80, VC90, VC100
>>>
>>> Docs distributions:
>>>
>>>     With API containing full interactive graphics.
>>>     With API only containing tabular and source links.
>>>
>>> Source Distributions:
>>>
>>>     Xalan-C tar.gz  -- for UNIX/Linux platforms
>>>     Xalan-C zip     -- for Windows platforms
>>>
>>> Our official Xalan-C/C++ website is curent with my website staging.
>>>
>>> Sincerely,
>>> Steven J. Hathaway
>>> Xalan Documentation Project
>>>
>>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
> For additional commands, e-mail: dev-h...@xalan.apache.org
>
>


Reply via email to