On Wed, 2018-04-04 at 11:07 -0400, Randy Barlow wrote:
> On 04/03/2018 07:02 PM, Adam Williamson wrote:
> > On Tue, 2018-04-03 at 15:25 -0400, Randy Barlow wrote:
> > > One question comes to mind though - won't this be a problem in the
> > > future too? How can we guarantee that users can keep upgrading to 14,
> > > 15, 16, etc. since Fedora doesn't keep in-between updates in the repos?
> > When I maintained ownCloud, I just shipped upstream major version bumps
> > as downstream stable updates. I wrote a wiki page explaining that the
> > upstream ownCloud upgrade policy was the reason for doing this. It's
> > still there:
> > 
> > https://fedoraproject.org/wiki/OwnCloud#ownCloud_package_update_policy
> Hey Adam!
> I think that's a reasonable stance to take on the update policy, but it
> doesn't quite address the specific problem I was getting at. I wasn't so
> much worried about pushing major updates to our users as I was worried
> about a user *missing* a major update while it was still in the repos. I
> probably didn't express this clearly enough, but to expand my example:

I used to keep a side repo with builds of each major version around to
cover this scenario. Not sure if James does the same. I stopped using
*cloud when I stopped maintaining it. Not worth the hassle.
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to