Talk:Q319417

Some editors tend to delete beta versions (prereleases) without explaining why. I see no compelling reason since testing those versions by as many clients as possible is essential to make these stable soon. It can happen once and the first time I said nothing. Now it happened already twice. Do not try a third time please; be a little bit more cooperative and constructive. #tia

See AMDmi3's tP as well.

Kind regards, Klaas `Z4␟` V:  08:50, 22 September 2019 (UTC)[reply]

Hello @KlaasZ4usV:,

As discussed with @AMDmi3: on his talk page, the release note issued by SQLite team on this page is a DRAFT for a pending release which is not even available on the project's download page. I completely agree with AMDmi3 PoV. We are NOT talking about beta versions (which are tagged, with a date release note and a download link). Please stop adding fake informations in this page.

Naked8Snake (talk) 08:27, 23 September 2019 (UTC)[reply]

The release is on the downloadpage with a link to the release notes referenced on the item's claim. All one needs to do is unpack the tarball, run a C-compiler and one can use this pending beta version. Many experienced users of sqlite3[.exe] do this already since the developers introduced their so-called amalgamation. This is where open-source software projects are all about. Users test them before a release/version/update becomes stable and published as an executable application for everyone. Therefore I reverted your destructive edit, Naked8Snake.
In bocca al lupo, Klaas `Z4␟` V:  10:18, 23 September 2019 (UTC)[reply]

WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.: could you give your opinion? Pamputt (talk) 07:10, 24 September 2019 (UTC)[reply]

@Naked8Snake: The version number would be "201909211731" not "3.30.0". It raises an interesting question whether there is a mechanism to state that software version "3.30.0" exists as a planned future version that has not yet been published. The English description for software version identifier (P348) states that it should only be used for current or past versions. Dhx1 (talk) 14:15, 24 September 2019 (UTC)[reply]

I see both of the sides, but in the end I think it's definitely wrong how it is added at the moment:

• This page says that version 3.30.0 is "pending"
• So does this page, that explicitly doesn't give a release date.
• The download page lists an Pre-release Snapshots without a version-number, but just a timestamp.

So there is no beta-version called 3.30.0, and this is not released on September 21. 2019, as the version by KlaasZ4usV would suggest. We can think about how we could indicate that version 3.30.0 is currently in development, but the current form contains wrong statements. -- MichaelSchoenitzer (talk) 21:25, 24 September 2019 (UTC)[reply]

I have modified a lot of software entries in WD, but I cannot recall a single one having nightly/daily/neutral build in this property. I'm not against indicating the location of current build, but IMHO, this information should not be stored in the "software version identifier" property. Maybe there's already some property for that, but I did not find it.

In the meantime, would it be possible to remove the wrong beta version introduced by Klaas? As pointed out, the informations provided are completely wrong! Thanks Naked8Snake (talk) 12:26, 25 September 2019 (UTC)[reply]

On this page one can read clearly all the dates, changes etc. about this pending release:

SQLite Release 3.30.0 (Pending). The date is in the name of the tarball ccyymmddhhmi. There are instances around the globe of users who have a C-compiler. The library is open source and therefore being tested by many experienced clients including yours truly ;-). Here and there one can find more info.

What's completely wrong with this, Naked8Snake? Thanks in advance for an answer, Klaas `Z4␟` V:  07:24, 26 September 2019 (UTC)[reply]

Three different people and myself have been telling what is wrong with was you are doing: software version identifier (P348) should be used for current or past version. A pending version is, by definition, neither current nor past and should, therefore, not be added to this property. I am certain that experienced users that would test a nightly build have better ways (a mailing list, the official website, a forum, a bug tracker) to check for a new build that looking at a property manually updated in WD Naked8Snake (talk) 15:18, 26 September 2019 (UTC)[reply]

So according to you the version type software beta version should not be used anymore?

The version is tagged pending in the chronology.

 Klaas `Z4␟` V:  12:31, 27 September 2019 (UTC)[reply]

I never said that beta (or alpha) version should not be stored, if there is a dated release note, I will input those versions myself. Proper release note for beta versions can be found on many software, such as Thunderbird, Postgresql or Python. For these software, the release note states clearly a release date and the fact that it is a beta version.

However, a version whose date is indicated as Pending is not release yet (also confirmed in the release note draft which indicates a temporary date of 2019-10-00) : the very definition of the word pending should be sufficient to convince you that the release has yet to happen.

Naked8Snake (talk) 13:14, 27 September 2019 (UTC)[reply]

I give up. You think to know more of SQLite and English than I do. The estimated date of "somewhere in October 2019" is when the development team plans to turn this beta into a stable one. Perhaps someone like you (who claims to be the ultimate expert) may get authorized to create a special version type for pending? Ave, Klaas `Z4␟` V:  07:59, 30 September 2019 (UTC)[reply]

One of the goal of Wikidata (and Wikipedia) is to provided verified information by reliable source (see WD:S). You are the one who is trying to add new information, so when users question the validity of a statement, you should provide a proper source for this information. As pointed out (by me and others), a daily/nightly build is not a beta version. First, SQLite has made some beta versions before, and they were properly identified in the release history page (search for beta or alpha in the page). Secondly, a Google search for "beta" or "alpha" on SQLite's official website only return these old beta versions, and do not show anything on a current beta. Therefore, I see no reason to consider the current pending version a beta (which you have to update frequently as the build gets updated, this is far from ideal as the "version" you add gets wrong pretty quickly).

Also, please stop implying that I claim to be an expert (in SQLite or Wikidata), as I said before, I see the point in adding a daily/nightly build property, but not in this property (I even asked other users if such a property existed). Since you seems so adamant to specify that a version is currently in preparation, maybe you should find a way to do it yourself. I see little interest for such information, but I won't stand against it as long as it is correctly entered in the database. You should try to reach people in project Wikidata:WikiProject Informatics or on the talk page of software version identifier (P348), they will probably be more informed than me on the subject.

Naked8Snake (talk) 09:21, 1 October 2019 (UTC)[reply]

the property reference URL accepts only valid URI values, but this causes that the references section to display the server part only which is not very intuitive. How do I add a more usable reference? Thanks in advance for your help :) --Uncopy (talk) 09:34, 18 August 2020 (UTC)[reply]