Topic: Development Plans for the Next Release of GParted (0.27.0)
With the next release of GParted we plan to add new enhancements to GParted.
GParted 0.27.0 is planned for release on October 10, 2016.
Candidates under consideration include:
Done? - Bug# - Description
Yes - Bug 766989 - zfsonlinux support - need file system name support of ZFS type codes
Mike Fleetwood has created a patch.
Yes - Bug 767842 - File system usage missing when tools report alternate block device names
Mike Fleetwood has created a patch set.
Yes - Bug 771323 - GParted is showing duplicate mount points for unmounted encrypted file systems
Mike Fleetwood has created a patch set.
Yes - Bug 771670 - Usage of active encrypted swap is not shown
Mike Fleetwood has created a patch set.
Yes - Bug 771693 - Mount Point column is wider than the screen on openSUSE using btrfs root with lots of mounted subvolumes
Mike Fleetwood has created a patch set.
Yes - Bug 771816 - GParted never exits if the main window is closed before the initial device load completes
Mike Fleetwood has created a patch.
Yes - Bug 772123 - GParted is unresponsive while gpart is running
Mike Fleetwood has created a patch.
Yes - Bug 768239 - sizes are wrong with musl libc due to use of non-standard sscanf "%Ld" modifier
Natanael Copa has created a patch.
No - Bug 627701 - option to encrypt new partitions (using LUKS)
Mike Fleetwood is working on this enhancement.
No - Bug 688883 - Improve SSD handling by using TRIM
Mike Fleetwood is working on this enhancement.
No - Bug 755429 - Add read-only display of LVM volume groups and logical volumes
Wrolf Courtney is working on this enhancement.
no - Bug 671784 - enhancement: convert partitions from one file system to another
Massimiliano Ghilardi is working on this enhancement.
no - Bug 673166 - NTFS partition trashed when resized to minimum size
Vladimir Panteleev has provided a patch.
Because there have been no other reports of this issue since 2012, the problem is either extremely rare or has been fixed in upstream ntfs-3g and this work-around patch is not required.
Your comments and responses are welcome in this forum post.