[svsm-devel] [EXTERNAL] SVSM Development Call Feb. 7th, 2024 (and Cargo workspace transition)

[Carlos Bilbao]

Hello,

I have an open PR and don't mind rebasing it. Since we already have both
Cargo.lock and Cargo.toml, I'd appreciate it if tomorrow we could go
through what this change may entail in practice.

Thanks,
Carlos Bilbao

On 2/6/24 11:41, Jon Lange wrote:
> Realistically, there will not be a point in time at which there are no pending PRs, so there will always be some number of PRs subject to conflict no matter when the transition is made.  It seems much better to make the transition as early as possible to reap the benefits of the transition.  Count me as another voice in strong support of option (1).
> 
> -Jon
> 
> -----Original Message-----
> From: Svsm-devel <svsm-devel-bounces at coconut-svsm.dev> On Behalf Of Jörg Rödel
> Sent: Tuesday, February 6, 2024 8:29 AM
> To: svsm-devel at coconut-svsm.dev; linux-coco at lists.linux.dev
> Subject: [EXTERNAL] [svsm-devel] SVSM Development Call Feb. 7th, 2024 (and Cargo workspace transition)
> 
> Hi,
> 
> As some of you already noticed there is a PR now which transforms the SVSM repository into a cargo workspace.
> 
> I consider the move to a cargo workspace an important change which should better happen sooner than later, but it is also very intrusive, basically breaking any other pending PR.
> 
> So there are two possible strategies right now:
> 
> 1) Merge the cargo workspace PR and let everyone else rebase their work on-top. That is work for everyone, but should not cause major hickups as only file paths will change and not the actual file content
> 2) Merge some of the pending PRs first and then do the cargo workspace transition. This requires re-basing the cargo workspace PR, which is also quite some work.
> 
> I am leaning towards option 1) as I think the sooner the transition is done the better, but I am open to other opinions on this. So if you think option 1) will not work/causes too much hassle or we should do something different, please speak up. Merging PRs is stopped until there is a decision on this, which I hope will be made after the SVSM Development call tomorrow.
> 
> The call is happing as usual tomorrow at 9am PST/5pm UTC/6pm CET.
> 
> You are all invited to join the discussion at:
> 
> https://meet.google.com/ppv-xehx-dvb
> 
> Please also let me know of any additional agenda items you want to discuss, either by replying to this email or raising them in the meeting.
> 
> A public Google calendar is available here:
> 
> https://calendar.google.com/calendar/u/0?cid=Y181NWEzOGYzNDYwYzYzODc2MmE3NWQ0ZmQ2ZWRhM2IxY2Y0NTVlYzRjZmQ3ZjgzMjAxZTNjYmY4MTdiNDIwZGQ4QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20
> 
> Looking forward to see you all there and discuss the above topics!
> 
> Regards,
> 
> Jörg Rödel
> jroedel at suse.de
> 
> SUSE Software Solutions Germany GmbH
> Frankenstraße 146
> 90461 Nürnberg
> Germany
> https://www.suse.com/
> 
> Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)
> 
> --
> Svsm-devel mailing list
> Svsm-devel at coconut-svsm.dev
> https://mail.8bytes.org/cgi-bin/mailman/listinfo/svsm-devel
>