I'm on the fence about how to handle documentation in respect to new and older non-supported versions.
I don't think that there should be no document updates to unsupported (EOL) versions, just that they should be very low priority. If someone in the community decides to supply a patch containing fixes / updates then they can be reviewed and applied on a case by case basis. Cheers, Jamie On Tue, Oct 25, 2011 at 2:56 PM, Glen Mazza <[email protected]> wrote: > Philosophically, I would advise against new documentation of any version > that is now unsupported. Once a project moves on, it moves on. Otherwise, > Karaf is placed at a competitive disadvantage when it has to be documenting > historical artifacts while a potential new competitor, by virtue of lacking > any history, can concentrate purely on present and future functionality. > > Glen > > On 10/25/2011 06:41 AM, Jean-Baptiste Onofré wrote: >> >> Hi Charles, >> >> for the commands, it should be already the case, as we have the >> cmdhelp-maven-plugin. >> >> I think that it could be interesting on the features-maven-plugin to have >> a help goal to generate the list of features, including description and >> info. >> >> Waiting for that (I will raise the Jira), I'm gonna create this page by >> hand. >> >> Regards >> JB >> >> On 10/25/2011 12:37 PM, Charles Moulliard wrote: >>> >>> Hi, >>> >>> It could be interesting that we create in a scalate page of Karaf Doc >>> a table listing all the commands/features that we have with Karaf >>> since release 1.x. that will help users to check what is new in >>> release x.y compare to a.b >>> >>> Regards, >>> >>> Charles Moulliard >>> >>> Apache Committer >>> >>> Blog : http://cmoulliard.blogspot.com >>> Twitter : http://twitter.com/cmoulliard >>> Linkedin : http://www.linkedin.com/in/charlesmoulliard >>> Skype: cmoulliard >> > > > -- > Glen Mazza > Talend - http://www.talend.com/apache > Blog - http://www.jroller.com/gmazza/ > Twitter - glenmazza > >
