Re: [Simulavr-devel] stable version for download?

[Thomas K]

Hi Klaus,

about outstanding changes: in the moment only the change for control 
start address. (which Albrecht has tested by an patch)

about branching for release 1.1: I have no problem to branch before my 
changes for USI. Means, that release 1.1 doesn't get USI and also not 
the control start address change.

As I check every time changes arrive master branch (not only my changes 
and then, if I see it) that all build and that "make check" is ok, I 
would tell, that's mostly stable. :-) Maybe check, if that, what's in 
examples directory, is building and working. (and have to be changed, if 
not ok) This is also a type of "regression check - by hand". :-) 
Ofcourse, the "best bugs" will find the "customer" - Murphy greets!

Maybe let us branch now. (with the decision, from which point?) and have 
a delay till beginning of march, if we see some bugs, then release.

cu, Thomas


Am 10.02.2016 um 20:12 schrieb Klaus Rudolph:
> Albrecht wrote:
> > > at first: Please use latest git master content. The version 1.0.0 contains so 
> > > many bugs that I can not answer any question to that outdated version.
> > Wouldn't it be a good idea, to remove this version and put a better
> > one onto the project home page?
> Yes, absolutely!
>
> I wrote a notification on the homepage which in hope will give a first hint! :-)
>
> As second, I want to have a more or less stable version as 1.1.0 in place. But actually 
> there are so many changes ongoing, that we currently could not present that as 
> "stable" one. Maybe the last before the big changes Thomas provided is a 
> candidate, but this version misses all the new features which are in this patch 
> provided...
>
> I also asked Thomas to get some docs for the last change to do a review and to write some 
> test cases which I will help with. After that work, we maybe can prepare the next 
> "release". One of my problems is, that we have so many interfaces which are not 
> covered by testcases, that changes in the pin/port library are a good candidate to break 
> e.g. verilog. So some tests are helpful...
>
> As I noticed on the homepage using the head of master branch is the current 
> advice for users. If users doing so, they will maybe find new introduced bugs, 
> but this will also help stabilizing the code. It is open source... ;)
>
> @Thomas: How many changes do you have in work and what is your expectation for a 
> "stable" release build time line?
>
> Regards
>   Klaus
>
> _______________________________________________
> Simulavr-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/simulavr-devel