No, I have not used Polarion. I have ran through the demos and and read the
white papers on their site. Pretty complete application. Definitely worth
a closer look. I recommend calling their sales staff. They are pretty
helpful and can answer the questions your asking with more authority.
Keep in mind, the requirements you're asking for are a mix of a couple
systems. Take some time divide them up, you'll see a grouping pattern
emerge. I think with Polarion and some other tools like the SVNManager, you
can get what you want. Subversion is still to young in the client side of
things to find products that encompass everything.
Johnathan
On 5/2/06 2:12 PM, "bruce" <bedouglas@earthlink.net> wrote:
> Hi Johnathan,
>
> Have you (or anyone else) actually used the Polarion application?
>
> Does it permit:
> -Source/Repository management (Copy/Delete/Modify/Etc...)
> -User ACL (Access List/control)
> -Workflow, moving files between folders based on process
> -Workflow, user notification, based on process events
> -Etc...
>
> Thanks,
>
> -Bruce
>
>
> -----Original Message-----
> From: Johnathan Gifford [mailto:jgifford@wernervas.com]
> Sent: Tuesday, May 02, 2006 11:52 AM
> To: SVN Users email list
> Subject: Re: SVN Browser/Management Application...
>
>
> Polarion (http://www.polarion.com) is a workflow/development life cycle
> application utilizing Subversion.
>
> Johnathan
>
>
> On 5/2/06 1:47 PM, "Baz" <brian.ewins@gmail.com> wrote:
>
>> On 5/2/06, bruce <bedouglas@earthlink.net> wrote:
>>> Hi Frank...
>>>
>>> What we actually need is a Workflow app, built on top of
> Subversion/SVN...
>>>
>>> -Bruce
>>
>> I presume you mean you need process definitions versioned. For that
>> you can just use the subversion client library; you'll have to write
>> the workflow side of things yourself (or just google for it).
>> Workflow's a pretty vague term, even if tools follow the wfmc
>> standards (theres loads of optional bits). Generally you can't find
>> workflow tools to do what you think you wanted to do, you have to
>> change your processes to match the available tools or it'll cost you.
>>
>> The one subversiony thing you mentioned that isn't covered by the
>> client library is user management. The way you can do this is to use
>> svn with apache, and switch the apache authentication module you're
>> using to be one for which management tools exist, eg LDAP, SSPI. Or if
>> you're not going to expose svn to the end users, but manage everything
>> behind your own webapp, you can just use properties on files to
>> indicate ownership etc, and manage authn/authz for yourself. If you're
>> doing *that* you might as well look at something like Apache
>> Jackrabbit.
>>
>> -Baz
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 2 21:22:10 2006