On 08/17/2011 11:43 PM, Marlon Pierce wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Normally all of our SVN check-ins should be associated with Jira tasks.
Should we continue this or suspend it for sandbox checkins?
I would prefer we associate SVN check-ins as much as possible with JIRA issues,
including for sandbox checkins.
The thing with sandbox tasks/issues of course is: they are not related to the
main/current development cycle/version, so setting a "fix for" etc. doesn't make
much sense.
But it would be good to somehow make it clear such JIRA issues are related to
sandbox development.
One way would be to add a new "sandbox" JIRA component.
Or maybe even better, add a "sandbox-science-gateway" JIRA component. I prefer
then using a "sandbox-" prefix instead of "-sandbox" postfix to get all sandbox
"components" to be logically grouped together.
Concerning JIRA components in general, I think we can and should use them more.
Right now there only "site" and "build & development" are defined, but adding a
few sensible onces like "portal", "shindig","persistence", "security" etc. will
help classify our issues better.
And even more so when we start adding more rave-components sub modules.
Regards,
Ate
Marlon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOTDYZAAoJEEfVXEODPFIDywwH/0mNqwO0QIHrBQ5PVSPTMSnj
xzIbJWOLz/zAAhSgahuBELzDB1BrwmQ2ohdx046Pt83rAN0O50RZbh+jRFh2LxvD
DKVLWMg2EAFgVRhxQ7NqlxcTctjzTVB+vGvYR7OEqGqXvYh3gwOXqO7DcHWEfEjw
eKGndQyw7/yDRWR2pRt1lBX4O/Qb6yiITVIBmmV1/s2fjkn09WbXs/zyFiqy1Pq5
SvNIleqx+KCmbiuTNOGhmFW2EKMft8k75LqTE1pFfuvINEoSTwAepfOjT7sCYt5b
vYdii4uW2+uZNElpe279CojwxHBkgF1Yaz0w10FnFWsaeWb+kSUHdZV+Xe1GCNo=
=77tw
-----END PGP SIGNATURE-----
