Not sure what kind of release you have in mind, but if it's major or minor (like in maj.min.fix) I'm not sure whether we should go on releasing PCManFM-Qt or libfm-qt on their own in the first place. As long as we publish releases of LXQt as a whole I figure it's pretty confusing for end users when a crucial component like PCManFM-Qt comes with its own release cycle.
Of course we could decide to drop the concept of releasing LXQt as a whole and publish releases of the various components independently. Several other components have seen important changes since 0.11, too. But I for one don't believe the project would benefit from this. If on the other hand your aim is to get important innovation into a stable release and hence included downstream quickly publishing LXQt releases more frequently, as intended anyway, is probably the better approach. Technically this has become really easy due to the work we've done before 0.11. E. g. right now I think the task list of milestone 0.12 is a bit too ambitious and would mean an inadequate delay. But if the development goes on like it did since September releasing 0.12 in about two months would make a lot of sense, IMO. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
