Google Code In (GCI) starting in 2 days

[Joel Sherrill]

On Dec 14, 2015 5:57 AM, "Gedare Bloom" <gedare at rtems.org> wrote:
>
> Yes, removing notepads and removing task variables are good tasks.
> They'll need a little more write-up yet, although we can start by
> opening up two tasks to "investigate/fix" the tickets and see what
> students do with it. I will add them soon.

Can a procedure for deprecating a feature be added? Include  marking it as
deprecated with the warning, filing a ticket with one final release first
it to remain in, then removing it.

It may also be an opportunity to have a prepaid for removing a test. That
has the straightforward git commands but should mention configure.ac
possibly, Makefile.am and a search through BSP test configurations.

Having these procedures as we move forward should be a good thing and the
GCI procedure can reference them.

> On Mon, Dec 14, 2015 at 7:46 AM, Sebastian Huber
> <sebastian.huber at embedded-brains.de> wrote:
> > Hello,
> >
> > are these two tickets suitable for a GCI task?
> >
> > http://devel.rtems.org/ticket/2493
> > http://devel.rtems.org/ticket/2494
> >
> > --
> > 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.huber at embedded-brains.de
> > PGP     : Public key available on request.
> >
> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> >
> _______________________________________________
> 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/20151214/3d051fec/attachment-0002.html>