Comments (4)
Regarding release stats. I found that page
- https://tooomm.github.io/github-release-stats/
This could help @jrswedlow to quickly get information assuming that there is a release alongside the tag.
To filter by IP etc., we will need to use the API
from openmicroscopy.
We would need to code something to go through all of them, but good to know that the stats are there.
from openmicroscopy.
This one is actually nicer in terms of display https://qii404.me/github-release-statistics/
Code available at https://github.com/qishibo/github-release-statistics
from openmicroscopy.
Thanks for opening this. I see for classes of improvements. Trying to express my views and sense of priorities for each of them
-
CI & deployment pipelines: migrating to GitHub Actions as the primary tool for CI/CD is in line with the efforts that have been made in the last 12-18 months. No objections
-
Version bumps and updates: this is a natural requirement that follows the splitting of the code base into separate repositories. Anythin that reduces the manual maintenance and using either existing tools (dependabot) or custom scripts to automate update PRs following upstream releases is useful and integrates with our development worfklow. As a bonus, what would be interesting (also beyond the scope of OMERO) would be to easily generate and maintain a graph of the relationships between all these repositories.
-
Artifacts hosting:
a. for all components which do not have a dedicated repository (DOckerHub, Maven Central, PyPI), GitHub releases certainly feels as the platform of choice. It has been reliably used for OMERO binaries since 12+ months and my vote is for pushing more
b. for Java components, Maven Central offers well-defined advantages in terms of third-party hosting, availability to the community and integrates with services like javadoc.io which don't need to be replicate. The primary downside based on the experience with theome-*
low-level Bio-Formats components is the cost for chained release so I would not understimate the impact as this has the potential for increasing the complexity of the release process. There was a brief discussion about potentially reducing the number of server components which could also be included in this discussion and might be worth capturing -
increase omego exposition in our tooling. Here again some mixed views
a. For
x.y.z
versions, assuming we move to GitHub releases and drop the build number suffix, we are close to being able to completely predict server URLs that can easily retrieve viawget/curl
,urllib3
... For this use case, adding a library dependency in our system administration community to wrap such a basic command feels overkill.
b. For installing major/minor/latest versions, somethign is needed to provide the layer of redirection. With binaries hosted on downloads.openmicroscopy.org, we can control this redirection via our web server proxy but there is no built-in mechanism in GitHub releases to achieve the same requirement
c. part of the idea behindomego
is to build some form of in-house package manager - that's definitely how it is used inhttps://github.com/ome/omero-install/pull/266. We are successfully using the library at the Ansible role level but it is fair to say the current team has limited experience in developing, designing and maintaining such software. Prior to extending and recommending it, I think we need to collectively agree that we are ready to support it moving forward.
from openmicroscopy.
Related Issues (20)
- Scripts warn unnessarily to master.err
- Invalid directory specified for file system service HOT 5
- RFE: change default branch to master
- Should websockets be enabled by default? HOT 1
- failed upgrade to Omero5.5 - Ice 3.6 not found HOT 2
- More non-parallel test assumptions
- omero db script → psql: identifiers truncated
- Document Python logging properties
- Manage services from the omero settings HOT 1
- missing OMERO.insight-5.4.10-ice36-b105-linux.zip HOT 4
- AdminService load Experimenters and Groups options with GroupExperimenterMap
- Improve performance of graph operations. HOT 2
- Annotations displaced when opening saved qpdata file HOT 1
- Alternate gradle/maven artifactory location? HOT 3
- CZI file Exposure time HOT 4
- Fix JSON API JavaScript login example HOT 1
- Increase the usage of compound assignment operators HOT 1
- Remove Pixels name, repo and path columns HOT 3
- OMERO.server: JDK 17 support HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openmicroscopy.