|
Written by Paolo Brandoli
|
|
Thursday, 12 August 2010 21:58 |
|
Well, the conversion from Hg to Fossil seemed ok, but at a closer look it was clearly messed up. So, this is the plan: - new development will be carried out using Fossil: previous versions of the source code will not be stored in Fossil
- older versions of Imebra will be stored in an Hg repository, which will not be updated with newer releases
|
|
|
Written by Paolo Brandoli
|
|
Sunday, 01 August 2010 21:35 |
|
The first SCM used for Imebra was SVN. This was back in 2005. In 2008 the SVN repository was imported into a Mercurial one. And today the Mercurial repository has been successfully imported into a Fossil repository. |
|
Read more...
|
|
Written by Paolo Brandoli
|
|
Tuesday, 01 June 2010 15:10 |
|
Despite the success of the library among the open source coders, very few customers are using the library commercially. In order to boost the development and the quality of the library, I'm desperately looking for a sponsor that can finance the development (and will have steering powers regarding the features) |
|
Last Updated on Tuesday, 01 June 2010 15:38 |
|
Read more...
|
|
|
Changing repository hosting |
 |
 |
 |
|
Written by Paolo Brandoli
|
|
Tuesday, 27 July 2010 19:49 |
|
I'm in the process of selecting a different HG repository hosting service. At the moment the library is hosted on Bitbucket, but development of the hosting service seems to have stagnate and lately they had several stability issues. I've tried out CodebaseHQ, but they don't allow public HG repositories, so I closed the account after few days. Now I'm trying Firefly from Activestate, but my instance of Trac crashed few seconds after they initialized it: still down (after 4 days) and the support is still looking into it. Will I stay with Firefly? It doesn't look like. |
|
Last Updated on Tuesday, 27 July 2010 20:11 |
|
Read more...
|
|
Written by Paolo Brandoli
|
|
Wednesday, 07 April 2010 21:13 |
|
The next version of Imebra, called Imebra 2010, is being polished for the prime time. The new version reduces the memory usage (in the best case it uses only 25% of RAM compared to the current version, and when using the transformsChain the memory saving is even better). |
|
Last Updated on Tuesday, 01 June 2010 15:33 |
|
Read more...
|
|
|
|
|
<< Start < Prev 1 2 Next > End >>
|
|
Page 1 of 2 |