You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could not find information on which repository platform to prefer. There are Github Issues as well as Sourceforge Tickets and Sourceforge forums. For 1.25.9 there is a Github Release and a SourceForge Tag as well. There is also a repo on Bitbucket.
I have a bunch of (non-security) bugs to report and I would like to know whether GitHub is the best place to do so.
Update: I ask this because there are 2 issues reported by myself about 2 years ago that seem completely untouched since then (#786#787) and I don't want to put more effort in reporting the wrong way/ on the wrong platform.
The text was updated successfully, but these errors were encountered:
Hey @idrassi - good to see that you found some time for VeraCrypt recently. As this is a meta question I hope it is ok to link you and it does not feel like skipping a queue.
No problem to answer this question.
Basically, Github is for a developer oriented/technical audience whereas Sourceforge is for standard users issues and general discussions.
The source code is duplicated across several providers for redunduncy...it is better to avoid putting VeraCrypt git repository and its history into a single hande.
Concerning #786, the approach proposed by @fzxx looks the best to me and i'm planning to implement it.
Concerning #787, it seems easy to fix. I will look into it.
I could not find information on which repository platform to prefer. There are Github Issues as well as Sourceforge Tickets and Sourceforge forums. For 1.25.9 there is a Github Release and a SourceForge Tag as well. There is also a repo on Bitbucket.
I have a bunch of (non-security) bugs to report and I would like to know whether GitHub is the best place to do so.
Update: I ask this because there are 2 issues reported by myself about 2 years ago that seem completely untouched since then (#786 #787) and I don't want to put more effort in reporting the wrong way/ on the wrong platform.
The text was updated successfully, but these errors were encountered: