On Tue, Jan 20, 2015 at 5:52 PM, Andy Kurth <[email protected]> wrote:
> Why include a roadmap in RELEASE_NOTES at all? I though there was > agreement in the following thread that we would take a more > pragmatic approach to formulating a roadmap: > http://vcl.markmail.org/thread/xulfqvyg3sgqbong > > As such, I propose scrapping a roadmap in the RELEASE_NOTES file > altogether. I don't see many other projects including anything in > RELEASE_NOTES > other than notes about the release. > This is a good point - and we should consider the intended audience for whatever we release. The intended audience of RELEASE_NOTES consists of the people who *install* the release. They don't need the roadmap for that purpose. The people who want/need the roadmap are the ones who are interested in developing the next release(s) - i.e. the ones on this dev mailing list - and the roadmap is now incorporated in the files of this list. It would also be reasonable to have a separate document at the site "Roadmap-for-future-releases" so that anyone interested in future releases could easily find it to read and it wouldn't burden the release download. --henry > > -Andy > > > On Tue, Jan 20, 2015 at 1:57 PM, Josh Thompson <[email protected]> > wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > I just updated the Roadmap in the RELEASE_NOTES file as follows. Let me > > know > > if there are any notable features for 2.4 that I missed. I moved things > > that > > were previously listed for 2.4 that we haven't done to 2.5 and then > added a > > few things we did do in 2.4 to the list. I think we should shoot for > only > > having a few items for 2.5 so we can get something out sooner. It's been > > *way* to long since 2.3.2 was released. > > > > VCL 2.4 > > * Improve additional connect methods > > * NAT support > > * Scripted installation > > * Initial support for OpenStack > > * Initial power management control > > * Improve cluster reservations > > * Rewrite of resource management parts of frontend > > * New and Current Reservations pages combined and more dynamic > > * Support multiple web servers > > * Support for OpenNebula > > > > VCL 2.5 > > * Remove requirement for 2 NICs > > * Support for Spice remote display protocol > > * Support for ESX OS for end users > > * Initial support for EC2 > > * Improve Power management > > * Service deployment configuration management > > * Initial support for Libcloud > > > > VCL 2.6 > > * develop tools for managing both system and user storage > > - -- > > - ------------------------------- > > Josh Thompson > > VCL Developer > > North Carolina State University > > > > my GPG/PGP key can be found at pgp.mit.edu > > > > All electronic mail messages in connection with State business which > > are sent to or received by this account are subject to the NC Public > > Records Law and may be disclosed to third parties. > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v2 > > > > iEYEARECAAYFAlS+lyoACgkQV/LQcNdtPQP4CwCfYPKW80XvC66SQCwpaHmwGGLg > > h+UAn044a1DlU9pXjpM2hMYnYSEJG5B8 > > =RKdW > > -----END PGP SIGNATURE----- > > > > >
