apoch / epoch-language

Home of the Epoch Programming Language Project
Other
72 stars 3 forks source link

Code review prior to release #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Perform a complete code review of the current codebase, looking for 
formatting/documentation, general cleanup opportunities, and appropriate code 
improvements.

Original issue reported on code.google.com by don.ap...@gmail.com on 29 Nov 2009 at 11:05

GoogleCodeExporter commented 9 years ago
At this point the R8 code is going to either have to be delayed for a 
substantial 
amount of time, or the code review process will have to be deferred. For 
scheduling 
reasons I think it is more appropriate to defer the review, since it is likely 
to 
turn up some major areas that can be reworked.

The main goal of the project at the moment is to ship a solid, usable preview 
release 
for GDC'10. Shipping some subpar code is fine as long as we have a very strong 
package ready for people to check out. Delaying R8 will only serve to further 
decrease the amount of time available to work on the GDC release, which is 
already 
dangerously slim.

All things considered, I think it is a more effective use of time to ship R8 as 
soon 
as possible, and then return to code improvement once the pressure is off a bit 
(i.e. 
post-GDC).

Original comment by don.ap...@gmail.com on 1 Feb 2010 at 5:29