VCS best practice for development vs production

Alan Davey david.a.davey at gmail.com
Wed Jan 31 14:32:44 UTC 2024


Hi Paul,

If you are able to use JSON export/import for your libraries, why would you
want to use an Omnis based VCS instead of github, bitbucket, etc.?  Those
repositories have lots of nice add-ons and hooks to better manage and
automate your CI/CD pipelines.  My goal is to get away entirely from the
Omnis VCS at some point so that multiple developers can finally work on the
same classes at the same time.

Regards,

Alan

On Mon, Jan 29, 2024 at 8:49 PM Paul Mulroney <
pmulroney at logicaldevelopments.com.au> wrote:

> Hi Doug,
>
> Thanks for your email - another excellent overview of Git and SVN.
>
> I should've said "if only we could build an Omnis-based VCS using JSON and
> git ..."  vcs is a general term, but when I think of the Omnis Version
> Control System see in my head as all caps.
>
> Regards,
> Paul.
>
> > On 30 Jan 2024, at 9:19 am, Doug Easterbrook <doug at artsman.com> wrote:
> >
> > hi paul.
> >
> >> Now, if only we could build a VCS using the JSON export/import and git
> ...
> >
> >
> >
> > not sure what you mean by this or if you are asking a question.
> >
>
>
> I was going to look for my missing watch, but I could never find the time.
> (http://onelinefun.com)
> --
> Paul W. Mulroney                                            We Don't Do
> Simple Pty Ltd
> pmulroney at logicaldevelopments.com.au       Trading as Logical Developments
> www.logicaldevelopments.com.au                   ACN 161 009 374
> Ph: +61 8 9458 3889                                       86 Coolgardie
> Street
>
>  BENTLEY  WA  6102
>
>
>
>
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>


More information about the omnisdev-en mailing list