Re: traditional AS/400 code base CMS transition -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: traditional AS/400 code base CMS transition
From: DrFranken <midrange@xxxxxxxxxxxx>
Date: Wed, 15 Jan 2020 13:12:09 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Midrange Dynamics would be my first suggestion.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 1/15/2020 9:45 AM, Jay Vaughn wrote:

So, our company was just acquired by another company with deeper pockets
and SoftLanding is asking an arm and a leg now to transfer the CMS to our
new company.

So, we are exploring alternatives.

Could have up to 10-20 iseries devs working on the code base (which is
large - hundreds for files/tables and thousands of pgms)

Any suggestions?

Is there a sharp learning curve for github enterprise (pro), compared to
what we are used to now with TO?

tia

jay

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.