| Re: [jetty-dev] documentation versioning |
I think master should be versioned to the current jetty release, so change the pom.xml to be version 9.0.2.v20130417.Since we are using the maven resource filtering, expressions like ${project.version} can be automatically resolved in the documentation. This means that all examples of things like the jetty-maven-plugin, or names of dependencies jetty-server-9.0.0.M2 could be the correct version under our /current documentation.Come time for the next release, we just grab current in the jetty-website repo and copy it over to the named version 9.0.2.v.20130417 and then set the version in the pom.xml of jetty-documentation to the next release. That way all of our changes over the month or so that the release is the latest, are automatically updated under current and all the examples are fresh and correct.If you _need_ an instance set to a particular version, then we can just leave it hard coded...no fancy expressions needed.I want to do this to combat the folks that carefully cut and paste from examples and get old versions of dependencies, or plugins, or whatever.If we like this idea I'll cruise through the code and it get fixed and make the lion share of changes, I suspect some perl -pie will be in order.Oh...and for documentation that would be future related, like if we want to get a jump on servlet 3.1 documentation, we can either fork master and do work there...or we can come up with a DRAFT like tag for FUTURE with pages that have future content. I don't anticipate us getting that far ahead in documentation...but that would be a good problem to have down the road :)thoughts?jesse--Jesse McConnell <jesse@xxxxxxxxxxx>
Intalio, the modern way to build business applications.
Webtide, advice and support for jetty and cometd.