<p dir="ltr"><br>
On May 12, 2015 10:33 AM, "DJ-Pfulio" <<a href="mailto:DJPfulio@jdpfu.com">DJPfulio@jdpfu.com</a>> wrote:<br>
><br>
><br>
> >> people. That was 1 current version per OS and perhaps 40 customizations 1-2 for<br>
> >> each client.<br>
> ><br>
> > I thought doing packaging only for LTS releases was the only way a small vendor<br>
> > could offer support. Test code and new features go in the 6-9 month release OS<br>
> > platforms.<br>
><br>
> I've had discussions with clients where we'd say - "we've never tried it - any<br>
> support calls will be time + materials." Usually the people running/using the<br>
> software, didn't have any budget control, so they wouldn't try it.<br>
><br>
> > So a single release of your product for RHEL 6 will also support centos 6 and<br>
> > SuSE 10 and a repackaging/recompile/relink will work for Ubuntu 12 and Debian<br>
> > wheezy (?). New features are for new customers on new platforms.<br>
><br>
> I never assume Ubuntu and Debian to be 100% compatible. Ubuntu has recently been<br>
> shipping non-stable kernel releases in their LTS releases - 3.13, 3.19, ...<br>
><br>
> > So you have an interim release for centos 6.5 that adds new features. Existing<br>
> > customers can upgrade to the new version based on $$$ :-) unless you're just<br>
> > giving it away and only selling support.<br>
><br>
> Releasing anything is a big deal. We'd contract technical writers for a few<br>
> weeks and the test team would be slammed for months even with the automated<br>
> testing tools. Every platform is a tiny bit different and bugs show up that just<br>
> don't make any sense - often because 3rd party tools aren't 100% consistent<br>
> either. Even with all this, releases would be staggered by which client was most<br>
> needy (largest contract). It usually wasn't an issue, since we only had about<br>
> 40 clients world-wide for that software.<br>
><br>
> > Look at setting up a koji system to support builds across all rpm platforms. I<br>
> > assume debian and ubuntu have something similar.<br>
><br>
> We had automated builds 25 yrs ago, if that is what you are saying.</p>
<p dir="ltr">Koji does builds and packaging for all selected platforms. It uses a chroot tool called mock to provide only the barest minimum of each base os kernel, libs, etc for each base release and update version. It outputs completed rpms , src.rpm and binaries, or fail logs sorted into web folders by package, release, base os, version, etc.</p>
<p dir="ltr"> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>
</p>