I did some research and I did not found an answer to that problem.

I must be missing something ... I though these can't be possible without our own repo. The idea behind having our own repo is: get freebsd ports tree add our own ports ----> build pkgs repo (Synth will take care of dependencies and changed options) ---> user will upgrade thru pkg command. ASX Devel...

Yea I will do it.

True but doesn't seems to be a problem, because there library get updated. Once we get our pkg repository this will change for sure.

I am starting this topic here because it might always evident for use to communicate on IRC and at less here of decision will documented. Right now I am on favour of going for latest and releasing more often something every 2 or 3 month until it is possible to do it monthly. You mention "we nee...

The upgrade of 10.X to 11.X is not that mush complicate, because the freebsd-update tell you the command needed to do the pkg upgrade. I did it to time without any issue.

There is link on 3 page on the website.

Yeah you are right, 10.* would not be supported, only all release that will come after the release that we start supporting this.

I am looking in to how to make possible all this from the update-manager. At one point it need to be able to update of GhostBSD version.

Oh point is that GhostBSD 10.1 if any one download it and run update some package will break, because lots package is changing and it is running on latest, but even with quarterly after a year the same problem might happen. But if we release more often this could be avoided, but there is some inevit...

To make GhostBSD semi rolling release, it would be simpler and you can almost all ready do it by making a change in /etc/pkg/FreeBSD.conf replace quarterly by latest to be more hardcore you could use ports. I might be able to pull this of for 11.0 and make a new release every month or 2, this way ne...