Thank you, I'm somewhat aware of the reasoning and case itself, let me have a look at the outcome of this cooperation ...
Thanks for the extra confidence of not being a late rushed crap due to providing install logs, test logs and generally outlining the details and what you did. It shows that you really thought about impact, regressions and more. I checked the upload in the PPA as if it would be in NEW queue, namespacing (lustes- and lib names that match) and licenses (no warnings) are fine. The packaging best practises you already iterated on the last few days. Thanks! Ask in regard to the changelog (maybe it is in git but not in the PPA uploads I checked): - it is almost a hard requirement to map to this bug there, please add "(LP: #2168274)" - it would be lovely but not required if there could be a bit of a summary what was done (not all details, but high level if you started from scratch and why some options have been chosen, ...) This is almost free text and a bit more than "Initial release" would help. I know that you know what it is all about, but others do not. AA pre-ack for this case under https://ubuntu.com/project/docs/release- team/freezes/#new-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2168274 Title: Soft FFe / intention to upload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lustre/+bug/2168274/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
