KStars v3.5.0 Release Date?

[Hy Murveit]

Eric,

I would add to your list:

- KStars Handbook (review update sections to reflect 3.5.0) and finally
(perhaps manually if necessary) put the latest handbook online.

- Review the extraction settings. I spent a bit of time looking at the
default HFR settings, and based on some experimentation (truth be told,
with a limited amount of data) adjust things a little differently than my
first guess (which was basically focus' settings).
*Rob*: My intuition is that I should adjust the default StellarSolver
star-extraction settings for Focus and Guide as well in
stellarsolverprofile.cpp
<https://invent.kde.org/education/kstars/-/blob/f952564f40ac7e01c2ba382889b1b4f1048b12e1/kstars/ekos/auxiliary/stellarsolverprofile.cpp#L19>.
I don't know whether you've already verified them, and want to release them
as they are, or whether they are a first shot and you'd welcome adjustment?

Also, Eric, I suppose I should be adding these things here:
https://invent.kde.org/education/kstars/-/issues
Is that right? Sorry about that--ok, after this thread ;) But seriously,
your email is a good summary, and from that link
it doesn't seem as easy to see which are "must do by 3.5.0" and which are
"nice to have someday".
A 3.5.0 punchlist would be a nice thing to have.

Hy

On Wed, Nov 4, 2020 at 12:58 PM Eric Dejouhanet <eric.dejouhanet at gmail.com>
wrote:

> Hello,
>
> Where do we stand now in terms of bugfixing towards 3.5.0?
>
> - StellarSolver has all features in, and 1.5 is finally out at Jasem's PPA.
> - However Gitlab CI still complains about that lib package (see
> https://invent.kde.org/education/kstars/-/jobs/75941)
> - Unitary tests are being fixed progressively, mount tests are down to
> ~20 minutes (yeees!)
> - From my tests, the remote Astrometry INDI driver is not usable
> anymore from Ekos.
> - The issue raised with flat frames is confirmed fixed (at least by me).
> - Meridian flip is OK (but I had not enough time to test TWO flips in a
> row).
> - Memory leaks are still being researched in Ekos.
> - There is an issue when duplicating an entry in a scheduler job,
> where the sequence associated is copied from the next job.
>
> Could we get a 3.6 branch where we will merge development of new features?
> And master for bugfixing 3.5.x until we merge 3.6 new features in?
> (we'd still have to port bugfixes from master to 3.6)
> I don't think the opposite, master for 3.6 and a separate living
> 3.5.x, is doable in the current configuration (build, ppas, MRs...).
>
> --
> -- eric.dejouhanet at gmail.com - https://astronomy.dejouha.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20201104/573e0b38/attachment.htm>