Bug 1431969
| Summary: | pull gluster-block v0.1.1 into d.g.o | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Prasanna Kumar Kalever <prasanna.kalever> |
| Component: | project-infrastructure | Assignee: | bugs <bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | anoopcs, bugs, gluster-infra, nigelb, prasanna.kalever |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-17 09:13:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Prasanna Kumar Kalever
2017-03-14 07:56:56 UTC
Can you bump up the version to 0.2 please? That way users on 0.1 can upgrade to this one. Hi Nigel, As this doesn't fall under a major fix in v0.1 we would like to go with the release 2 of 0.1 version. I got an opportunity to raise your thought with block team yesterday and the team think this should be pushed as v0.1-2. Thanks! okay so we currently have: https://download.gluster.org/pub/gluster/gluster-block/0.1/ The new release will be: https://download.gluster.org/pub/gluster/gluster-block/0.1-2/ Would it make sense instead to do 0.1.1 instead? This way you can use the dashed numbers as numbers for the build in case there are build failures on your first attempt. Happy to go with 0.1-2 as well. Let me know which works best. So if you see the package name here [1] it is gluster-block-0.1-1.x86_64.rpm The new package name will be gluster-block-0.1-2.x86_64.rpm So ideally, the new path should be https://download.gluster.org/pub/gluster/gluster-block/0.1-2/ Thoughts ? [1] https://download.gluster.org/pub/gluster/gluster-block/0.1/fedora/25/x86_64/ (In reply to Prasanna Kumar Kalever from comment #4) > So if you see the package name here [1] it is gluster-block-0.1-1.x86_64.rpm > > The new package name will be gluster-block-0.1-2.x86_64.rpm > > So ideally, the new path should be > https://download.gluster.org/pub/gluster/gluster-block/0.1-2/ Why should this be under different directory? I would say we put new rpms under 0.1 directory itself i.e, https://download.gluster.org/pub/gluster/gluster-block/0.1/fedora/25/x86_64/ > > > Thoughts ? > > > [1] > https://download.gluster.org/pub/gluster/gluster-block/0.1/fedora/25/x86_64/ Different directories makes it cleaner to download the latest package and also use the older packages. Wouldn't that be less confusing? My knowledge around rpm repos aren't perfect, so happy to be proven wrong here. +1 Nigel. I am okay this way either. This is now sorted: https://download.gluster.org/pub/gluster/gluster-block/ I've also setup this repo file: https://download.gluster.org/pub/gluster/gluster-block/gluster-block.repo If users have that installed, they can download be on the latest version as we release it. I must apologies for wrong package name. Thanks to Kaleb, Niels as well as Nigel for corrected me. In "0.1-2" the "-2" belongs to revision. Means every time we build a package we do increment this, or if we have build failures due to spec issue we do modify the spec and increment the post-fix. Since there are code changes, this release should go with 0.1.1 tag. So now we have to change the 0.1-2 to 0.1.1, Nigel will I get your support here ? copr link to package https://copr.fedorainfracloud.org/coprs/pkalever/gluster-block/build/527601/ This has been done. I've confirmed that upgrades from 0.1-2 to 0.1.1 works from the d.g.o page. All seems to be working well. |