Hi Tom, On Friday 28 May 2010 10:53:42 am Tom Sharpless wrote: > What has happened to the idea of keeping (past and future) releases in > the SVN repository?
Most voices were against it. I did research on the topic and could probably implement something if there is a use case with benefit/effort >1. > Released code needs to > adhere to a higher standard of buildability and documentation that's what tarballs are for. > 2) It validates lots of existing documentation about how to build > Hugin yes, the SVN->Hg move has made a lot of documentation outdated. > the project should be as helpful as possible to people who just want > to build (and distribute) stable releases Agree. The use case here would be to update the documentation and help those people cope with the new repository. Also: for stable releases there are the tarballs. Nothing has changed with them AFAIK, other than we forgot the monthly poll to ask ourselves if "trunk" (or now in new Hg terminology "default") contains enough new features to warrant branching out a release. The release cycle's documentation [0] is now technically outdated (need to replace hg commands with svn commands) but the process is still the same. > The fact that Hugin releases have so far > not lived in SVN actually since 0.8.0 releases have lived in SVN, each with its own branch according to [0]. After a few fixes and enough polish, the branch florish into a tarball. Yuv [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Release -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
