RE: change management software

Simon,

It's been 4 moths since I worked with Aldon and 5yrs.  since I set it up.
Not to mention that I've not ever set it up this way  ;-)  But I'll go ahead
and put a response out now and I'll see if I can get my hands on a manual to
double check myself on the structure here.

Aldon defines "application" with three parts.  Top level is the one or more
"Systems", next is one or more "Applications" followed by one or more
"Releases".

MY_SYSTEM
  |_______________/KillerApp1
  |                       |____________/v1Base
  |                       |____________/v2Base
  |                       |____________/v3Base -------Parent
  |                       |____________/v3Mods ----Child---+ 
  |_______________/KillerApp2
                         |____________/v1Base
                         |____________/v2Base
                         |____________/v3Base--------Parent
                         |____________/v3Mods-----Child---+------Parent
                         |____________/v3Eng------------------Child---+
                         |____________/v3Ger------------------Child---+


Aldon shows this structure as MY_SYSTEM/KillerApp1/v3Mods for example.  Each
release is defined as a "*BASE" or "*DELTA" release.  If *DELTA then you
have to define it as a child of some other (*BASE or *DELTA)  release.  I
believe you can have *BASE release themselves defined as a *CHILD to another
*BASE (or *DELTA?) but I don't. remember for sure.  For each release you
have the 4 environments (Dev/Int/QA/Prod).  Making a change in a "Parent"
automatically notifies children and as I recall you can also set it up for
automatic notifications of other releases.

Developer libraries, I'll have to double check this one.  I know each
developer can have his/her own.  I also know that you can use shared
libraries; but I'm not sure at what level the sharing can be set up.


Charles


> -----Original Message-----
> From: Simon Coulter [mailto:shc@xxxxxxxxxxxxxxxxx]
> Sent: Friday, December 05, 2003 6:34 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: change management software
> 
> 
> 
> 
> Perhaps I don't understand what you mean by environments. It sounded 
> like the environments are:
>      Production
>          QA
>              Integration
>                  Development
> 
> as a hierarchy and that you could have each of these levels within a 
> project (or application). For example:
>       KillerApp1
>          Production
>              QA
>                  Integration
>                      Development
>      KillerApp2
>          Production
>              QA
>                  Integration
>                      Development
> 
> 
> Could you show an Aldon structure based on my previous examples? How 
> would you create a structure that handles different base versions of 
> the same project with fix levels (deltas) and national language 
> support? How does Aldon handle individual developer libraries?
> 
> Regards,
> Simon Coulter.
> --------------------------------------------------------------------
>     FlyByNight Software         AS/400 Technical Specialists
> 
>     http://www.flybynight.com.au/
>     Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
>     Fax:   +61 3 9419 0175                                   \ /
>                                                               X
>                   ASCII Ribbon campaign against HTML E-Mail  / \
> --------------------------------------------------------------------
> 
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>