Peter Law
2016-03-13 12:21:05 UTC
Hi all,
I've been asked to look after the competition software again this
year. We now have a well-proven base to build on, so I doubt we need
to make many changes this year.
That said there are a small number of improvements and fixes which I
think we should make. In addition there is some testing to ensure that
system updates haven't broken anything. We will also of course need to
make a number of year-specific changes, including the scoring things.
Since everything should already be in a working state (I'm not aware
of any substantial changes since last year's competition), I'd like to
keep things that way. To that end, all changes should be developed in
feature branches and/or submitted as patches for review, rather than
direct merging.
This will keep the master branch of all repos in a state which is
immediately-shippable. If you're aware of any repos which aren't
already in this state, please shout now.
My intention is that we should work on getting the system completely
deployable first (I believe this is done), then fix any bugs and
finally add any new features which are needed. I'll be adding the
things which I think are critical to the "SR2016 Competition"
milestone on trac.
In order to avoid a last-minute rush, the deadline for changes will be
2 weeks before the competition, on the weekend of 16th April.
If you'd like to get involved with any part of this please reply below
so I can coordinate efforts and access to hardware.
Thanks,
Peter
I've been asked to look after the competition software again this
year. We now have a well-proven base to build on, so I doubt we need
to make many changes this year.
That said there are a small number of improvements and fixes which I
think we should make. In addition there is some testing to ensure that
system updates haven't broken anything. We will also of course need to
make a number of year-specific changes, including the scoring things.
Since everything should already be in a working state (I'm not aware
of any substantial changes since last year's competition), I'd like to
keep things that way. To that end, all changes should be developed in
feature branches and/or submitted as patches for review, rather than
direct merging.
This will keep the master branch of all repos in a state which is
immediately-shippable. If you're aware of any repos which aren't
already in this state, please shout now.
My intention is that we should work on getting the system completely
deployable first (I believe this is done), then fix any bugs and
finally add any new features which are needed. I'll be adding the
things which I think are critical to the "SR2016 Competition"
milestone on trac.
In order to avoid a last-minute rush, the deadline for changes will be
2 weeks before the competition, on the weekend of 16th April.
If you'd like to get involved with any part of this please reply below
so I can coordinate efforts and access to hardware.
Thanks,
Peter
--
You received this message because you are subscribed to the Google Groups "Student Robotics Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to srobo-devel+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Student Robotics Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to srobo-devel+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.