On 09/11/17 05:58, Chris Johns wrote:
On 08/11/2017 23:29, Sebastian Huber wrote:
I can build RTEMS with the updated RTEMS tools and RSB (patches sent today). I
plan to commit this tomorrow. With respect to the documentation of the release
process please see also:
https://lists.rtems.org/pipermail/devel/2017-November/019400.html
I am sorry but I had not looked at the parts we need to update or seen anything
on this. I would like to have the list of all things we need to change and we
are agreed on. I would also like this process documented.
I added a ticket to document the process:
https://devel.rtems.org/ticket/3220
There is:
1. Documentation repo. Easy.
I will do this today.
2. Documentation website repo. Easy.
I don't know how to do this.
3. Release procedure repo. Easy.
Do we really need another repo? Could we please place this to the tools
or RTEMS.
4. Trac tickets. Not sure.
I will do this today.
5. Trac wiki. Medium(?). A wiki search of 4.12 gives 21 hits.
This is probably the most important area to fix:
https://devel.rtems.org/wiki/Release
I will do this today.
6. rtems.org website. That needs Joel.
Can we please consider these items before we switch? I am concerned not doing
this leave these things to me to clean up.
I can assure you that I will actively work to make a RTEMS 5.1 release
happen in this century.
I can do 1, 2, 3, and a bit of 4. I
will look after the https://devel.rtems.org/wiki/Release/ tree and the top
level. All I am after is an understanding these things will get done because the
patches you have posted are the first thing to change and the other parts need
to follow as soon as possible after that or we end up with a confusing message.
I hope that we are done with this by end of next week.
We should also have a formal announcement about the change and reason.
Yes, who will do this?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
