On Wed, Sep 24, 2014 at 02:24:28PM +0300, Andrej N. Gritsenko wrote: > Henry Gebhardt has written on Tuesday, 23 September, at 23:15: >> Two minor things: a) To avoid confusion, I would start with the ABI_VERSION >> equal to the current release number, e.g. 0.8.0. We can always let them >> diverge later. > > In general, soname numbers are not (and never should be) relevant to the > software release - those numbers are just compatibility numbers, and for > first non-alpha release of library ABI version should be 1, with age and > revision at 0. But while the 0.8.0 will be in development (alpha, 0.7.99 > or whatever), it would stay at 0.0.0. :)
Not sure I agree. Yes, they are only compatibility numbers, but we want to minimize confusion. We are treating the 0.x.y releases as almost stable already. And although it doesn't really matter, starting with 0.8.0 as the first ABI version would let everyone know since when this library exists. No need to read any documentation. We can leave it at 0.8.y for as many releases as we want to. > >> b) It seems the file src/panel.c needs a new name. How >> about src/panel_ui.c? > > In fact, it is not UI at all, the src/panel.c represents implementation > of LXPanel widget and its API functions. If you mean it's too much alike > new created by me lxpanel.c file then why not choose another name for the > latter instead? How about main.c then (because it contains exactly main() > and relevant functions) for it? Yes, I agree. I just couldn't come up with a better solution. main.c is a common way to name the source file that contains the main() funciton. Thank you, Henry ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
