21 Jan
2012
21 Jan
'12
3:20 p.m.
Timothy Pearson wrote:
You would start by uploading your patched packages
into a new
3.5.13-updates PPA. There they can receive testing from our userbase
before being merged into the official repositories.
If this sounds like something you would like to do, please let me know and
I will contact you off-list with account information.
I'm not sure how Git works, but wouldn't it be better to have something
like a separate testing branch based on the 3.5.13 code (maybe also call
it R13?) which could result in a new release like 3.5.13a or R13.1
instead of patching things with the package scripts?
Then packages based on this branch could be tested and maybe there could
be a quicker bugfix release before R14 is released. At least all
packagers could choose to get the source from this branch then and get a
few more fixes already. Now it would be more effort for all the
packagers to manually add fixes to their packaging scripts (which would
only be temporarily as well).
Isn't it also easier for the infrastructure to have extra PPAs based on
separate Git branches? In any case, regular updates to stable Trinity
versions with only smaller bugfixes sounds like an attractive idea to me :)
Best regards,
Julius