+1 with the 'older documentation' link.
On Sat, May 3, 2014 at 5:40 PM, Sean Busbey <[email protected]> wrote: > Hi David! > > I purposefully only included not linking to the docs from the main nav > menu, because I also think the docs should stay online, at the same URLs. > > I haven't been keeping up with the website redesign, so I didn't want to > get caught up in specifics of how we might get people to them. Provided > there's some place we can add an "older documentation" section of links, > would that address your concern? > > Nonactive release are always available for download form the archive, which > is linked at the bottom of the releases page. > > The main point of the downloads page is to draw people to versions we want > them to use, so I'd rather restrict 1.4 to the archive. Is your concern > that people have a way to get to the 1.4 artifacts or that they be > prominent? > > Once artifacts have been posted to the apache maven repository they should > be available indefinitely, so we would not remove any 1.4 related ones. > > -- > Sean > On May 3, 2014 4:01 PM, "David Medinets" <[email protected]> wrote: > > > -1 because I suggest the 1.4-related documentation remain on the site. I > > believe existing users of 1.4 will not be moving to 1.5 for a long time. > So > > the same reason, I think the release download link should remain for the > > same reason. > > > > Does EOL mean the releases will be removed from official maven > > repositories? > > > > > > On Sat, May 3, 2014 at 4:41 PM, Sean Busbey <[email protected]> wrote: > > > > > Accumulo Folks, > > > > > > I would like to declare end of life for the 1.4 branch of development. > > It's > > > been active for a little over two years and the release of 1.6.0 means > we > > > now have three active releases. > > > > > > Declaring end of life would mean > > > > > > * Posting an ANNOUNCE message to the user list > > > * No longer accepting issue fix version targets for future 1.4 releases > > > * Removing fix version targets of 1.4.x for existing open issues > > > * The end of having a long lived 1.4 related branch in git > > > * Removing direct references to 1.4.x releases on our download page > > > * No longer linking to the 1.4 related documentation from the main > > > navigation area > > > > > > Our issue tracker shows that candidate version 1.4.6 currently has: > > > > > > * 9 closed issues, none of which are blockers or critical. > > > * 1 issue in patch available status, marked critical > > > * 18 open issues with a target fix version of 1.4.6, four of which are > > > marked critical. > > > > > > Because there is existing work, but not yet enough to warrant a > release, > > I > > > propose > > > that on successful passing of this vote we create a "1.4.6-eol" tag > with > > > the then > > > current state of the development branch. > > > > > > Please vote > > > > > > [ ] +1 I am in favor of announcing End of Life according to the above > > plan > > > [ ] +-0 I am indifferent > > > [ ] -1 I am opposed to the above End of Life plan because... > > > > > > I'm treating this like a release vote. Thus, it will be handled with > > > Majority Approval: > > > to pass it will need 3 committers to +1 and more committers voting +1 > > than > > > -1. > > > > > > Vote will remain open for 72 hours, until Tuesday, May 6 2014, 20:40 > UTC > > > > > > -- > > > Sean > > > > > >
