https://bugs.kde.org/show_bug.cgi?id=400652
Andrius Štikonas <andr...@stikonas.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In|3.4 |4.2.0
--- Comment #10 from Andrius Štikonas <andr...@stikonas.eu> ---
(In reply to Nate Graham from comment #9)
> Is the next version 3.4? Also, would you be at all interested in putting
> Partition Manager on the Release Service and using the common versioning
> convention? You wouldn't have to handle packaging anymore, and the app would
> get regular releases automatically, and it would be easier to predict what
> the next version would be. :)
The next version is 4.2.0 (current version is 4.1.0) and I was going to release
it on 16th October (I still need to email kde-i18n list about it).
Putting it on Release Service might be OK, I'm not opposed (but not for 4.2.0
release, I want to get it out sooner rather than later) to it but this needs
some further discussion with Adrian de Groot, as Calamares depends on it and
there is a question of API/ABI stability, although I guess we don't need to be
ABI stable as this is not a framework, I think some kdepim packages are in a
similar position.
What I would definitely suggest, is putting KTorent/Libktorrent on release
service because KGet (which is part of release service) depends on libktorrent
for bittorrent plugin, and I'm not even the main contributor, recently
Alexander Trufanov was doing most of the work.
By the way, adding support for whole disk partitions led me to notice a very
curious sfdisk bug (https://github.com/karelzak/util-linux/issues/1156), sfdisk
is unable to create MBR partition table if you have FAT/NTFS filesystem on
whole device. And after looking at util-linux source code for some time it was
"Of course..." (FAT and NTFS filesystems have MBR table inside them).
--
You are receiving this mail because:
You are watching all bug changes.
