[sldev] Etiquette for posting patches-in-progress?

Able Whitman able.whitman at gmail.com
Tue Jul 17 15:07:35 PDT 2007


If I've got a patch for a JIRA issue that's not quite finished, but in a
state that can be tested, would it be good practive for me to attach the
patch to the JIRA issue, with a note that it's not the final version?

I'm trying to find the most convenient way to share in-progress patches, and
the nice thing about putting them in JIRA is that it's a central place for
all the resources related to a particular bug. So for things like the
Sandbox (i.e., the Yet-To-Be-Named) edition, all the current patches could
be found in JIRA without having to have some submitted via email, some
downloaded from other sites, etc.  The downside is that currently there's no
common way to flag a patch as "attached, but not ready for import".

Maybe a "ready for import" flag could be added? Or maybe the right solution
is to post the patch elsewhere (like on my own site, like I do currently),
and only attach patches to JIRA when they're done. I'd like to do whatever
is simplest and least confusing, but I'm not sure that one solution meets
both criteria. :)

--Able
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20070717/b4c76e5a/attachment.htm


More information about the SLDev mailing list