Hi Daniel,
I've worked in that flavour as well. The bottom line is as long as you can
establish a working process before the project gets under way and the
customer understands the overhead required by the CNC's for the various
methods, then we can all get along.
Regards,
Gerald
DBohner
<
[email protected]
om> To
Sent by:
[email protected]
jdelist-bounces@j cc
delist.com
Subject
Re: Can we Build packages from DEP
03/08/2006 04:38 environment?
PM
Please respond to
JD Edwards®
EnterpriseOne
Gerald,
I think you misunderstand the reason why the are called OMW PROJECTS. Most
development is based on a Project Basis. If you are suggesting that a
developer move objects out of a PROJECT and place them in ?the black whole?
? then I?ll try to add just a tad bit of clarity ? from a Developer?s point
of view.
The developer is assigned a task. They create a PROJECT to keep all the
objects necessary for that ?assigned? task ? and they maintain all the
objects for that task in that project. They promote the PROJECT because it
maintains all the relationships to complete the assignment ? in one
ORGANIZED area.
The developer then promotes their Project to a status (something safe, like
you said ? 23). The CNC should monitory all projects at this status ? and
consider them, once they hit 23, to be OK for a PY build (your setup may
vary).
At an assigned time during the day ? the CNC will promote every PROJECT at
a status 23! to a Status 26, then start the build process. The Developers
should not be allowed (either by rule or agreement) to demote from a 26 to
21 until after the build process? it?s the client?s decision?.
Now ? if the objects actually get tested ( ) ? one or more of them
may fail the success test. That said ? the entire project (the Developer?s
One Project with All Their Goop) get?s rolled back?.
Rolling back that one Project ? is a lot friendlier than kicking objects
in/out of a black-whole project?. The name of the game is ownership,
control and COMMUNICATION?. If a black hole project is used ? then what
happens when an object (a single object) needs to be rolled back ? and 75
of the other objects are fast-tracked to Production?
To cut short ? here?s a better solution? or at least a better solution I?ve
experienced at some of the sites I?ve worked at.
(db)?s Suggested Solution:
Every Developer (or SME) tha! t will be doing Projects is assigned a
?COPY-THIS? project (yo! u can na me it whatever you want). Within that
project are all the PVC Admins, CNC Groups and any other Owners that may
ever need to be tied to the project. When the developer is assigned a new
task ? they COPY the ?COPY-THIS? project to ?whatever? they are going to
call the new project.
When they are ready to have it built ? they promote to a Status 23, and the
CNC?s pick it up at the pre-defined time. Since all the CNC/PVC folks are
already ?owners of the project ? they don?t have to go looking for it (just
monitor Status 23).
I?m sure there are loopholes to the process that we can all dream up ? but,
I can tell you that the process works solidly at several organizations.
(db)
Member - iConsortium Always looking for new gigs! Daniel Bohner | JDE
Developer Independant-JDE/Web/Photo
www.ExistingLight.Net |
[email protected] JDE XE - 8.10 | AS/400