[REF] more often tagging or syncing with upstream

[Jiri Vanek]

On 03/17/2016 06:25 PM, Andrew Hughes wrote:

Ping?

FYI - https://bugzilla.redhat.com/show_bug.cgi?id=1318988 I already started the wheels of destiny, 
and I'm pretty sure the not-reproducible tarball will be the reelase blocker :(

J.
> ----- Original Message -----
>> Hello!
>>
>> I would like to introduce the aarch32 project to Fedora arm repositories.
>> To create clearly reproducible source tarball I need some anchor.
>> I think you will agree that cloning "tip" do not cover the reproducibility.
>> Also I think you will agree that keeping somewhere list of changset ids used
>> for source tarball is
>> not exactly convenient.
>>
>> So I would like to kindly ask you for favour and to tag your project forest
>> once per day or at least
>> once per week or just when things look little bit more stable then yesterday
>> (eg tomorrow:) )
>>
>> We had chosen this approach for aarch64 releases [1] by prefixing by
>> "aarch64" and incrementing
>> build.  As upstream builds are not exactly continuous, it works fine. But of
>> course feel free to
>> chose whatever suits you.
>>
>> I think that having small fedora arm32 community in testing audience may be
>> just benefit for project.
>>
>> Thank you in advance!
>>
>>    J.
>>
>>
>>
>> [1]
>> http://hg.openjdk.java.net/aarch64-port/jdk8u/
>> 2 weeks ago 	andrew 	Added tag aarch64-jdk8u72-b16 for changeset
>> 92af9369869fdefault tip
>> 7 weeks ago 	andrew 	Added tag aarch64-jdk8u72-b15 for changeset
>> 618f7e7b68f4aarch64-jdk8u72-b16
>> 7 weeks ago 	andrew 	Merge jdk8u72-b15aarch64-jdk8u72-b15
>> 2 months ago 	asaha 	Merge
>>
>>
>
> I don't think it needs to be as often as "once per day" as I doubt
> the RPMs will be updated that frequently. It would however be good

sure

> to have a known good point to base Fedora RPMs on. This is beneficial
> to the AArch32 project as well, as it is then clear what is being used
> by these binaries out in the wild.
>
> Thanks,
>