hiya, On Wednesday 21 May 2008 07:02:30 am Lucas Nussbaum wrote: > What you propose sounds like adding a lot of information to the PTS > page. Why did you choose that, instead of a separate website > (http://patches.d.o)? after looking over the sources for the pts, i agree that the best place to do this is no in the pts itself, but to have a portal/summary from the pts to a page with the full information. > > - - feature-branch patches for v3 (git) format packages, if possible > > (would require more thinking through and i do not intend to do this > > initially) > > It's not clear yet whether this format will be accepted in the archive. right, that is simply me acknowledging that this is a potential case that could be covered. > > additionally, for each patch, when possible provide the following > > information: > > > > - - which version of the package introduced it > > how are you planning to determine that? why is that important? how is perhaps left for future exploration, but i assume via tracking each source package upload. as for why, i thought it was pretty self-evident. > > - - any notes at the top of the patch > > - - any relevant vcs metadata > > - - any relevant bts metadata (could be found using heuristics in the > > previous items) > > example? i'll try and generate (or create a mock-up page at least) over the next few days for an example package or two. sean
Attachment:
signature.asc
Description: This is a digitally signed message part.