I agree that we wish to update old versions. It isn't so much work if:
1. We remain reasonably consistent, so merges can easily be done across
multiple branches. Therefore, keep your merges small and limited to single
files where possible - if you have more to update, do it in different
branches.
+1 with a note.
I've been involved with projects who have versioned docs with users on
multiple versions and an issue which came up quite frequently was that it
was a hassle to update legacy versions with more information.
A somewhat contrived example could be that we want to add additional
Hey everyone,
There's currently quite a few version of juju available [0] from various
sources (cloud archive, ubuntu archive, stable ppa, source). While I know
the release team is doing a great job in making sure that versions of juju
are consistent across platforms, it's inevitable that users
+1
On Jan 14, 2015 12:54 PM, Marco Ceppi marco.ce...@canonical.com wrote:
Hey everyone,
There's currently quite a few version of juju available [0] from various
sources (cloud archive, ubuntu archive, stable ppa, source). While I know
the release team is doing a great job in making sure that
