Does RTEMS5.1 have a release plan?

[Joel Sherrill]

Hi

Just so everyone knows Chris and I were at the GSoC Mentor Summit this
weekend. We spent a significant chunk of time triaging and fixing tickets.
This was on top of Chris helping me de-duplicate some of the getting
started documentation.

I can only ask the community, system administrator, and other core
developers to assist in fixing and closing the 5.1 tickets.

Thanks.

--joel

On Sun, Oct 14, 2018, 8:42 PM jameszxj <jameszxj at gmail.com> wrote:

> OK, I know. Thanks for the working .
>
> ------------------ Original ------------------
> *From: * "Chris Johns"<chrisj at rtems.org>;
> *Date: * Fri, Oct 12, 2018 10:21 PM
> *To: * "jameszxj"<jameszxj at gmail.com>;"devel"<devel at rtems.org>;
> *Subject: * Re: Does RTEMS5.1 have a release plan?
>
> On 11/10/18 9:01 pm, jameszxj wrote:
> >       We use the master rtems5 version in our project, it works fine. In
> the
> > next few months, we will release a project version, so we want to know if
> > RTEMES5.1 has a release date?
>
> The RTEMS 5 process is long overdue and I thank you for asking. We all
> need to
> again focus on it especially me. The delays are some what technical as
> well as
> related to me and personal issues that were out of my control this year.
> The
> release work is unfunded and they take time to make, create and verify.
>
> You can view the outstanding tickets here:
>
>  https://devel.rtems.org/milestone/5.1
>
> Any one can help by taking a look at them and asking here or the ticket
> what you
> can do.
>
> The ticket https://devel.rtems.org/ticket/3537 is new and it is actually
> pretty
> critical effecting all releases of RTEMS, 4.10 and 4.11 will not build. I
> will
> be making a post about it soon.
>
> Chris
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181014/08dfc04c/attachment-0002.html>