via @dotnet : Packaging and Publishing a .NET MAUI Library with GitHub Actions
https://ift.tt/a4tKkVe
#DotNet #MAUI #GitHubActions #DevOps #NuGet #LibraryPublishing #MSBuild #Automation #Versioning #PackageSigning #AzureDevOps #ContinuousIntegration #ContinuousD…
Amazon Q in Connectのバージョン管理機能を試してみた
https://dev.classmethod.jp/articles/amazon-q-connect-version-management/
#dev_classmethod #Amazon_Q_in_Connect #Amazon_Connect #Versioning #AWS
New to PsyArXiv: DOI Versioning
You might have noticed some changes in how your preprints are appearing on PsyArXiv, and wondered “what the hell is going on?” The big change is that the Center for Open Science/Open Science Framework has implemented DOI (Digital Object Identifier) versioning for all of their preprint communities, including PsyArXiv. This means that every time you upload a new version of your preprint manuscript, it will be given a new DOI. It also means that URLs for papers will have a suffix like _V1 or _V2 after the unique OSF preprint identifier. You will still be able to view current and previous versions in the same way that you have previously, and the system (via Crossref) knows that each of these versions are linked.
In practice, what does this mean for you when you’re uploading a preprint? For PsyArXiv, it won’t make much of a difference at all. You’ll still be able to upload your preprints in the same way, and upload updated versions when you need to. The only difference is that any new manuscript versions will have a different DOI to the original version. If you are only making a change to the manuscript metadata, that won’t lead to a new DOI being minted.
Because PsyArXiv uses a post-moderation approach, any submitted preprints will still go live immediately, and will then later go through a moderation process by our moderation team.
DOI versioning may have an impact on your current use if you need to withdraw a preprint from PsyArXiv. For example, you might find yourself submitting to a journal that does not permit preprinting (*I guess these still exist somewhere?). When you submit a withdrawal request, it will relate to a specific version. So, if you need to ensure that all versions of a preprint are removed, you’ll need to communicate this request to PsyArXiv (e.g., submitting a withdrawal request for each version) or COS support.
If DOI versioning isn’t going to make things different for users, you might wonder why you’d want to have different DOIs for different versions of a preprint. Well, having DOI versioning has been recommended by Crossref’s Preprint Metadata Advisory Group (see here:, Section 5.2.2 in particular), and is seen as best practice that supports an open peer review model to track review feedback and changes to the paper over time. For example, you could have an overlay journal that could use DOI versioning to track original submissions, an updated version in response to reviewer comments, and a final version accepted for publication. Another advantage is that translations of articles can have their own DOI, and different translated versions can be linked using appropriate meta-data. So, all in all, DOI versioning allows for more flexibility and opens up new possibilities for communities in terms of open reviewing.
If you’d like a little more detail on creating a new article version, take a look at the OSF’s help guide here, and here for some more information on how DOI versioning relates to new approaches to peer review.
I hope the above information is useful – Happy preprinting!
Dermot Lynott is an Associate Professor at Maynooth University, and the current chair of the PsyArXiv Scientific Advisory Board.
#DOI #openAccess #openResearch #openScience #preprints #versioning
Understanding Semantic Versioning
Git tag v1.0.0 (MAJOR.MINOR.PATCH)
MAJOR — Breaking changes 💥
MINOR — New features ✨
PATCH — Bug fixes 🔧
There are types of pre-release versions:
alpha — raw version of the build
beta — testing version of the build
rc — release candidate or nearly finished release
1.0.0-alpha < 1.0.0-beta < 1.0.0-rc < 1.0.0
#tech #versioning #git
Автоматизация версионирования в Kotlin Multiplatform: Решение для Android и iOS
Привет, Хабр! В этой статье я делюсь решением, как настроить версионирование приложения для Android и iOS с помощью Kotlin Multiplatform. Я рассказываю о том, как минимизировать человеческий фактор, автоматизировав процесс обновления версий, и как избежать дублирования информации в разных частях проекта. В статье представлен пример кода, который можно адаптировать под свой проект.
https://habr.com/ru/articles/895362/
#kmp #multiplatform #versioning #android #ios #compose_multiplatform #kotlin_multiplatform #kmm #mobile #kotlin
Blender's new "Oscar-winning" version #tool is here to finally help software enthusiasts achieve... well, nothing much really. 🤔 After all, who needs actual awards when you can navigate an endless maze of version numbers and download links instead? 🎉✨
https://www.blender.org/download/releases/4-4/ #Blender #OscarWinning #Versioning #SoftwareHumor #DownloadLinks #EndlessMaze #HackerNews #ngated
#ayuda fediverso
que solucion es mejor para hacer #backup de un servidor (los archivos)?
aplicaciones en #docker , como #bludit , #forgejo , #peertube entre otras..
querria algo que tenga #versioning y soporte #s3 e idealmente interfaz web para gestionar.
estoy probando #backrest pero no veo que tenga versioning?
@t3rr0rz0n3 @matiargs @pijusmagnificus @samcre
se agradece #boost
Fallthrough episode 10 is live! APIs, versioning, and HTTP. Alternatively, why semantic versioning is a lie and people don't make use of HTTP's powerful features. https://fallthrough.fm/ep/10 #podcasts #software #http #api #versioning
there are two types programming language communities, identified by how they engage with semver
1. the type that labels a package version 0.32474 after its been used in mission critical production code making billions of dollars and literally saving Earth from the goa’uld because, like, the API just isn't stable yet
2. the type that are on version 312.2.42 after a full month of being out. 311 has an optional config change. 313 is going to seem like it does nothing but actually subtly inverts the behaviour of the entire API in a way that seems totally logical to the maintainers and exactly no-one else
My manager flicked this one through. Just so accurate 😭
Time-travel, DEVONthink style 🕰️ 🧳 #devonthink #versioning #comingsoon
Suppose you're reading `(next)`, which indicates the upcoming #feature #version of a #software project. The last version was 0.12.0 — what would you expect the next version to be?
We are talking about Semantic Versioning: https://semver.org/ #semver #versioning
https://pridever.org/ Pride Versioning 🏳️🌈
https://github.com/romversioning/romver Romantic Versioning
https://semver.org/ Semantic Versioning
#programming #versioning #version #coding #pride #prideversioning #romanticversioning #semanticversioning #semver
ooooh
Mah Felloh Gamers
https://www.thecanary.co/discovery/sport-and-gaming/2025/01/21/play-offline-games/
#game #gaming #RetroGaming #gamer #gamers #over30gamers #nerd #nerds #geek #geeks #videoGame #videoGames #videoGaming #review #PeerReview #peer_reviewer #guide #tip #tips #advice #advisory #idea #ideas #framework #infrastructure #outline #versioning
Corso GIT e GitHub per PRINCIPIANTI
https://peertube.uno/videos/watch/9c1ca9b3-640e-40af-9393-25e8a1ef5310
@jcrabapple
#iceshrimp just has a stupid #versioning schema. The last major version was in 2023.12. Since then they did minor releases, like security fixes and released them by adding and increasing the third number, now we are at Iceshrimp v2023.12.11, released on Nov 20, 2024
https://iceshrimp.dev/iceshrimp/iceshrimp/releases?page=1
