May be Mike can organize this release flow... 🙂
CC'ed Mike Perez, I think team need some manager observability (a little)


k

> On 25 Jan 2023, at 16:26, Christian Rohmann <[email protected]> 
> wrote:
> 
> Hey everyone,
> 
> 
> On 20/10/2022 10:12, Christian Rohmann wrote:
>> 1) May I bring up again my remarks about the timing:
>> 
>> On 19/10/2022 11:46, Christian Rohmann wrote:
>> 
>>> I believe the upload of a new release to the repo prior to the announcement 
>>> happens quite regularly - it might just be due to the technical process of 
>>> releasing.
>>> But I agree it would be nice to have a more "bit flip" approach to new 
>>> releases in the repo and not have the packages appear as updates prior to 
>>> the announcement and final release and update notes.
>> By my observations sometimes there are packages available on the download 
>> servers via the "last stable" folders such as 
>> https://download.ceph.com/debian-quincy/ quite some time before the 
>> announcement of a release is out.
>> I know it's hard to time this right with mirrors requiring some time to sync 
>> files, but would be nice to not see the packages or have people install them 
>> before there are the release notes and potential pointers to changes out. 
> 
> Todays 16.2.11 release shows the exact issue I described above ....
> 
> 1) 16.2.11 packages are already available via e.g. 
> https://download.ceph.com/debian-pacific
> 2) release notes not yet merged: (https://github.com/ceph/ceph/pull/49839), 
> thus https://ceph.io/en/news/blog/2022/v16-2-11-pacific-released/ show a 404 
> :-)
> 3) No announcement like 
> https://lists.ceph.io/hyperkitty/list/[email protected]/message/QOCU563UD3D3ZTB5C5BJT5WRSJL5CVSD/
>  to the ML yet.
> 
> 
> Regards
> 
> 
> Christian
> 
> 
> _______________________________________________
> ceph-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to