Nice. Always keeping master bug fix complete with all completed features make people more likely to use tip. Another related method of managing versions that I've seen is to create forks when you want to do a release. On 2 Dec 2013 18:00, "Bruno Medeiros" <brunodomedeiros+...@gmail.com> wrote:
> On 02/12/2013 10:35, eles wrote: > >> On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote: >> >>> On 18/11/2013 15:32, ilya-stromberg wrote: >>> >>>> On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote: >>>> >>>>> Quick question: with the current version is it possible to use it with >>>>> a dub project at all (maybe via a manual project setup)? >>>>> >>>>> I was trying to manually set it up, pointing "sources" as the source >>>>> folder and trying to get the ~/.dub/packages into the list of >>>>> libraries, but it did not seem to like it... >>>>> >>>> >>>> Yes, manual setup is possible, but you must use absolute path without >>>> `~`. >>>> >>> >>> Exactly, although you can use some Eclipse resource variables in the >>> path of linked folders. >>> >> >> why this? >> >> https://github.com/bruno-medeiros/DDT/commit/ >> b7a57f9e0d7915734ba6b175acfc1fd53a7a92f4 >> >> > The commit it reverted was not meant to go to master, but to a branch. The > idea is that master is to be kept potentially shipable at all times, and > dub support is not ready (nor was it disabled in the original commit, which > is another way that it could be allowed to be commited to master). > > -- > Bruno Medeiros - Software Engineer >
