* Building packages from a SHA instead of the tip of a branch
@ 2016-02-25 12:28 Loic Dachary
2016-02-25 17:37 ` Gregory Farnum
0 siblings, 1 reply; 3+ messages in thread
From: Loic Dachary @ 2016-02-25 12:28 UTC (permalink / raw)
To: Gregory Meno, Alfredo Deza; +Cc: Ceph Development
Hi Gregory and Alfredo,
The system in place to build packages uses the tip of the stable branch, which has been a recurring problem over the past years. It would make a lot of sense to use a specific SHA1 instead of "whatever is at the tip of the stable branch at the moment".
Is there already an issue in tracker.ceph.com for this ? If not, in which tracker do you suggest I file this feature request ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Building packages from a SHA instead of the tip of a branch
2016-02-25 12:28 Building packages from a SHA instead of the tip of a branch Loic Dachary
@ 2016-02-25 17:37 ` Gregory Farnum
2016-02-25 18:33 ` Loic Dachary
0 siblings, 1 reply; 3+ messages in thread
From: Gregory Farnum @ 2016-02-25 17:37 UTC (permalink / raw)
To: Loic Dachary; +Cc: Gregory Meno, Alfredo Deza, Ceph Development
On Thu, Feb 25, 2016 at 4:28 AM, Loic Dachary <loic@dachary.org> wrote:
> Hi Gregory and Alfredo,
>
> The system in place to build packages uses the tip of the stable branch, which has been a recurring problem over the past years. It would make a lot of sense to use a specific SHA1 instead of "whatever is at the tip of the stable branch at the moment".
>
> Is there already an issue in tracker.ceph.com for this ? If not, in which tracker do you suggest I file this feature request ?
It might be easier to build from a tag or to push a specifically-named
branch (infernalis-release-2016-02-25) as well. Just to think around
the problem. ;)
-Greg
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Building packages from a SHA instead of the tip of a branch
2016-02-25 17:37 ` Gregory Farnum
@ 2016-02-25 18:33 ` Loic Dachary
0 siblings, 0 replies; 3+ messages in thread
From: Loic Dachary @ 2016-02-25 18:33 UTC (permalink / raw)
To: Gregory Farnum; +Cc: Gregory Meno, Alfredo Deza, Ceph Development
Hi Greg,
On 26/02/2016 00:37, Gregory Farnum wrote:
> On Thu, Feb 25, 2016 at 4:28 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Gregory and Alfredo,
>>
>> The system in place to build packages uses the tip of the stable branch, which has been a recurring problem over the past years. It would make a lot of sense to use a specific SHA1 instead of "whatever is at the tip of the stable branch at the moment".
>>
>> Is there already an issue in tracker.ceph.com for this ? If not, in which tracker do you suggest I file this feature request ?
>
> It might be easier to build from a tag or to push a specifically-named
> branch (infernalis-release-2016-02-25) as well. Just to think around
> the problem. ;)
IIRC taging was not an option because people have scripts watching the tags (it's a distant memory though, maybe it does not matter anymore ?). I like the idea of having an infernalis-release-2016-02-25 branch. Unless the scripts are somehow sensitive to the branch name ?
Cheers
> -Greg
>
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-25 18:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-25 12:28 Building packages from a SHA instead of the tip of a branch Loic Dachary
2016-02-25 17:37 ` Gregory Farnum
2016-02-25 18:33 ` Loic Dachary
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox