Ricardo Wurmus <rek...@elephly.net> writes:

> Releases are made a short time after the core team branch is merged.
> This would give us a new release whenever e.g. the default GCC and
> glibc is bumped up.  We could aim for a release two months after the
> merge to allow for minor fixes after the merge.

I think agreeing on and following a release schedule is the crucial
part.  Both for how frequently core team branch is merged
(aspirationally) as well as how long (roughly) after the merge the
release is made.

I propose that we have a time-based release model rather than a
feature-based one (similar to the Linux kernel).  However, what's
perhaps even more important is to have a release model that we adhere
to.

-- 
Suhail

  • On the quest for ... Cayetano Santos
    • Re: On the q... Ricardo Wurmus
      • Re: On t... Suhail Singh
        • Re: ... Greg Hogan
          • ... Suhail Singh
            • ... Suhail Singh
            • ... Cayetano Santos
              • ... Suhail Singh
                • ... Cayetano Santos
                • ... Ricardo Wurmus
                • ... Suhail Singh
                • ... Development of GNU Guix and the GNU System distribution.
                • ... Development of GNU Guix and the GNU System distribution.

Reply via email to