Applying a trick I learned from Edward de Bono, create a good idea out of an absurd one, namely become a time traveller...

Although design including code design moves forward in time, as soon as those are complete, you should ideally jump mentally into the future, starting with how the system will be supported and maintained after it is live and work backwards to the last relevant task which might be deployment of a given release into production. Does git cover it or do you need additional tools such as puppet? Will there be configuration files and installation scripts? What will the UAT and test environments be like and how will they be provisioned from your repository? How will you create the configuration data that distinguishes between say production, test and development environments and what tools will use that data? Only when you know that can you wind the clock back to the end of the development cycle where you can now make a list of deliverables by type, from your code design and implementation plan. After that you can jump back to where you are now in reality, design your git repository using your own correct rule (only push what is custom-built otherwise configure it to be installed wherever its needed) and you are good to go forward.

One world, one people

In reply to Re: Catalyst versionning by anonymized user 468275
in thread Catalyst versionning by QuillMeantTen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.