-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since we have bugs fixed and would like to get those out, but with the addition of a few features, I'd prefer to minimize what new features we work to include in 2.5 to prevent feature creap.
I untagged the following items related to the frontend because I haven't begun work on them yet. If I get them implemented before we try to get 2.5 out, I'll tag them again. VCL-801 (Improvement) rework how frontend determines to prompt user for image revision VCL-728 (Improvement) Add description column to variable table I haven't done any work toward VCL-869. I'd say to untag it as well, but didn't do that yet since it affects thte backend too. I commented on VCL-870 and VCL-873 to remain tagged with 2.5. Josh On Monday, August 10, 2015 2:58:40 PM Andy Kurth wrote: > I was about to change the "fix version" from 2.4.3 to 2.5 in Jira and > noticed a bunch of issues already tagged for 2.5. These need to be sorted > out. > > We discussed how a roadmap would be decided and how issues would be tagged > last September (http://vcl.markmail.org/thread/xulfqvyg3sgqbong). My > understanding is that there was agreement that issues other than bug fixes > would not be tagged with a specific version without discussion. It seems > as though we need to revisit this discussion. Another thread would be best > as to not hijack this one. > > The issues tagged 2.4.2 have not been altered so the 2.5 issues can be > sorted out with less confusion. The following issues were tagged 2.5 and I > am reasonably certain they have not been implemented. I untagged them from > 2.5: > > VCL-790 (Improvement) create section of web site for managing connect > methods > VCL-526 (Sub-task) add section to site to manage connect methods > VCL-571 (New Feature) EC2 API provisioning module > VCL-572 (New Feature) Automatically install updates when an image is loaded > VCL-579 (New Feature) provision ESXi as an end-user environment > VCL-718 (Improvement) Add optional automatic execution of sdelete.exe to > reduce vmdk size > VCL-680 (New Feature) Support for Apache CloudStack > VCL-336 (New Feature) Add support for IPv6 > VCL-388 (New Feature) Windows lab machine provisioning > VCL-416 (Improvement) Fix the default user profile when capturing an image > VCL-465 (Improvement) Add support for computers with a single NIC > > The following issues tagged 2.5 need to be checked. Leave a comment in the > issue if you determine that it indeed should be tagged 2.5. Otherwise, > untag it and reply to this message indicated you did so. > > VCL-873 (Bug) web UI only accepts 1 ssh identity key under User Preferences > VCL-870 (Bug) the foreign keys are not in sync between the vcl.sql and > update-vcl.sql files > VCL-869 (Improvement) remove computer.vmtypeid and add something to > vmprofile > VCL-866 (Bug) Makeproduction doesn't work correctly > VCL-846 (Bug) Improve flow of handling nodes for deleted reservations > assigned to new reservations > VCL-801 (Improvement) rework how frontend determines to prompt user for > image revision > VCL-796 (Improvement) tomainteance reservations should not be allowed to be > created at end of indefinite server reservations > VCL-728 (Improvement) Add description column to variable table > VCL-670 (Improvement) user provided data loaded at request time > VCL-614 (Improvement) static IP adresses - confirming IP is available > > Thanks, > Andy > > On Mon, Aug 10, 2015 at 1:46 PM, Aaron Coburn <[email protected]> wrote: > > +1 for calling it 2.5 > > > > Aaron Coburn > > > > > On Aug 10, 2015, at 1:40 PM, Andy Kurth <[email protected]> wrote: > > > > > > +1 for calling it 2.5. Good point. > > > > > > I can probably get all of the Windows 10 changes done by tomorrow. > > > > > > -Andy > > > > > > On Mon, Aug 10, 2015 at 10:40 AM, Josh Thompson <[email protected]> > > > > > > wrote: > > >> -----BEGIN PGP SIGNED MESSAGE----- > > >> Hash: SHA1 > > >> > > >> I think including Windows 10 support is a good idea. However, I'd > > > > prefer > > > > >> not > > >> to include things other than bug fixes or very minor changes in a 3rd > > > > level > > > > >> dot release. I'd suggest just moving forward to 2.5. I have a few > > > > small > > > > >> improvements to the Computer Profiles page I'd like to include as well. > > >> > > >> Any estimate on when support for Windows 10 could be ready? > > >> > > >> Josh > > >> > > >> On Friday, August 07, 2015 3:39:18 PM Andy Kurth wrote: > > >>> We intended 2.4.3 to be a minor bugfix-only release, but with the > > > > recent > > > > >>> release of Windows 10 I think it would be worthwhile to add support > > >>> for > > >> > > >> it > > >> > > >>> in this release. The subsequent 2.4.4/2.5 VCL release may not happen > > >> > > >> for a > > >> > > >>> while and people are going to want to start using it within VCL. > > >>> > > >>> I have taken a quick look at Windows 10 and created a base image. The > > >>> current Windows 8.x code should work well enough but I did notice some > > >>> minor problems. I created a Jira issue yesterday where the problems > > >>> encountered are being detailed: > > >>> https://issues.apache.org/jira/browse/VCL-893 > > >>> > > >>> Thoughts? > > >>> > > >>> Thanks, > > >>> Andy > > >> > > >> - -- > > >> - ------------------------------- > > >> 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 > > >> > > >> iEYEARECAAYFAlXIt/wACgkQV/LQcNdtPQM+KgCferyObGGPFgYBKM+fOiKU3EEe > > >> ++EAn2qQvS8+0wiyc9qn/AbSvLuZTAYU > > >> =2Crw > > >> -----END PGP SIGNATURE----- - -- - ------------------------------- 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 iEYEARECAAYFAlXI/psACgkQV/LQcNdtPQOCxACeJdkmJAocvY6V3xjBzjnDP19B aRwAn3g9gZouc8MSzy7F5eYc0MQCcX8C =CcXH -----END PGP SIGNATURE-----
