Hi,
1/ > « [...] in other words fossil was happy enough at that time to release 
1.36 [etc...] »

Software that doesn't have any bugs, is utopia.At least here (in my country), 
we don't dream ...
2/ > « [...] Quite frankly creating a new fossil version each time a new 
sqlite3 version (even minor) is out could lead to a loop [etc...] »

Seriously ? Nope.Fossil needs SQLite to run appropriately, SQLite could exist 
without Fossil. We can use Git (Yeah the evil for some Fossil user).
SO,a) SQLite was 3.15.0 and now is 3.15.1, which should mean a bug fix, even a 
minor one.b) Fossil must use the SQLite that is supposed without bugs, which is 
... 3.15.1.c) We can conclude that we could wait for 10 days...That is the 
point, not the loop discuss which is not relevant here. We could create 1.36.1 
then 1.36.2 then 1.36.3, I will stay with SQlite 3.15.1 with Fossil 1.36.0 
INSIDE sqlite.org if I do wish that.The main component of Fossil is SQLite.

> « [...] Beside that, could you try to discuss technical stuff without being 
> such hostile? »

People try to talk : why don't you try ?Someone is clearly hostile ? Try to 
demonstrate that such behavior is not relevant if you can...

  
Best Regards

K.

      De : Luca Ferrari <fluca1...@infinito.it>
 À : Fossil SCM user's discussion <fossil-users@lists.fossil-scm.org> 
 Envoyé le : Dimanche 13 novembre 2016 10h58
 Objet : Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 
64bit binary
   
On Sat, Nov 12, 2016 at 1:24 AM, K. Fossil user
<ticketpersonnal-fos...@yahoo.fr> wrote:
> Explain me why a SO serious project could not wait for 10 days or if it is
> not that possible (I don't see why ??), why don't Fossil create a 1.36.1?

Sorry pal, my guess is that the latest sqlite3 was not required by
fossil 1.36, in other words fossil was happy enough at that time to
release 1.36.
Quite frankly creating a new fossil version each time a new sqlite3
version (even minor) is out could lead to a loop, since sqlite3 needs
fossil to manage the code base and so each time a new fossil version
is out due to a new sqlite3 version, a new sqlite3 version should be
released leading to a new fossil version...

Beside that, could you try to discuss technical stuff without being
such hostile?

Luca
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


   
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to