On Mar 21, 2015, at 10:11 AM, Vasco Alexandre da Silva Costa
<vasco.co...@gmail.com> wrote:
> On Sat, Mar 21, 2015 at 7:19 AM, Christopher Sean Morrison <brl...@mac.com>
> wrote:
>
> If a callout is warranted in the schedule, there should be several instances
> of “test, debug, document” throughout your timeline, but still not one big
> 2.5 week one at the end. That’d be breadth-first waterfall-style cleanup.
> It’s just not acceptable from a risk-management perspective, and essentially
> something we’ve learned to not even allow for GSoC.
>
> Not necessarily. For example if you issue a code freeze before doing a
> version bump where you only accept bugfixes and don't accept any feature
> improvements it doesn't mean you are using a waterfall model. Is the Linux
> kernel development model a waterfall model? I would say it isn’t.
I would agree. When you have ongoing continuous integration cycles and
depending on the length of the cycles relative to the overall effort invested,
it’s arguably not waterfall. When it’s only one cycle, about 17% of the
timeline, and at the end — it fits the classic verification/debugging
characterization rather well. Regardless, it really doesn’t matter what we
call it. It’s highly “undesirable” for GSoC projects. :)
> I will change the planning timetable to work in the fashion you describe.
Appreciated. For everyone following the thread, I will add that discussions
like these are good to see. We expect give and take compromises and
collaborative discussions throughout development from everyone. We certainly
won’t always agree and contrary decisions will suck. It takes time and
commitment to earn a meritocratic position (which I’m sure, Vasco, you're well
aware of given your OSS experience). With that, however, also comes the
ability to influence change, take BRL-CAD in directions we weren’t even
considering (looking at all you web devs). :) Networking and building working
relationships are really the most important aspect of GSoC.
Cheers!
Sean
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
