I agree it makes sense, we can use git tags , or branches. Having separate docs for every version is how it works for all other languages I have used. Its zero extra work.

I dont know about the generation of pdfs though, I am not familair with CI / Jenkins and how easy it is to assign specific builds to git tags / branches.

On Sat, Apr 4, 2015 at 4:04 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:

Would it make sense to freeze the documentation for each image version? Maybe
a branch per image? This way, people who choose/need to work with previous
image versions have an accurate reference. From my limited Git experience it
shouldn't be much extra work.

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/UpdatedPharoByExample-for-3-0-4-0-5-0-tp4817514.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.