2012-04-19: StandUp Reports (expand all) (collapse all)
What I did in the last day / week
Renovate the state of our agile project, align ticket priorities, figure out the (two?) beta crashes, and identified a couple non-crashing errors.
What I will do today / this week
Remove abandoned legacy SCPlugin dependencies, Contextual Menu plugin glue, and as much unneeded targets, code and complexity.
Either unify the build process on XCode 3 or 4, or both. Both being the optimal state.
Via build integration, we can establish the correct, mutual use of shared libraries & svn, thus resolving associated tickets involving bad certificates and those involving Subversion exceptions (various, crashing SVNDaemonUIPlugin.app, and causing EasySVN.app to thrash, attempting to relaunch SVNDaemonUIPlugin.app, and restarting itself).
Quick, band-aid fix for these issues is to back the Subversion & libs to the ones that functioned correctly in alpha, while prudently adding an error message should any problems crop up at launch (instead of simply trying to launch again). I will attempt this quick workaround, merely for today's build.
The thorough fix is to unify, merge the linking to a single XCode project and solve any library deficiencies with uniformity.
Either unify the build process on XCode 3 or 4, or both. Both being the optimal state.
Via build integration, we can establish the correct, mutual use of shared libraries & svn, thus resolving associated tickets involving bad certificates and those involving Subversion exceptions (various, crashing SVNDaemonUIPlugin.app, and causing EasySVN.app to thrash, attempting to relaunch SVNDaemonUIPlugin.app, and restarting itself).
Quick, band-aid fix for these issues is to back the Subversion & libs to the ones that functioned correctly in alpha, while prudently adding an error message should any problems crop up at launch (instead of simply trying to launch again). I will attempt this quick workaround, merely for today's build.
The thorough fix is to unify, merge the linking to a single XCode project and solve any library deficiencies with uniformity.
What are my roadblocks and what do I need?
easysvn.xcodeproj
XCode 4 && hopefully XCode 3
SCPluin.xcodeproj
XCode 3 && if above fails, necessarily XCode 4
XCode 4 && hopefully XCode 3
- portability of easysvn.xcodeproj (Metric for success: fresh install Mac, fresh install XCode, not logged in as root, and if the project doesn't have only a single target to build, the project file must be accompanied by an .rtf/.rtfd "Build ~ How To" that contains the sequence of targets to build, handles any caveats or gotchas, and preferrably contains any screenshots to assist a new Developer perform the build, no additional MacPorts installs unless specified in the "Build ~ How To.rtf/.rtfd")
SCPluin.xcodeproj
XCode 3 && if above fails, necessarily XCode 4
- trimming of SCPluin.xcodeproj (Metric for success: remove excess legacy code / targets / dependencies from the Contextual Menu Plugin days of SCPlugin, ... fresh install Mac, and all the documentation requirements above, etc.)
No report from: | ||
---|---|---|
a_smirn | littlewang2011 |
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Macintosh svn client is powered by Assembla.