[Building Sakai] Signup tool in Jira - Project or Component?

Anthony Whyte arwhyte at umich.edu
Fri Mar 21 07:49:48 PDT 2014 

> I vaguely remember the decision was made to keep legacy (closed) JIRAs in the separate JIRA project space, but move all open JIRAs into the Sakai project under it's own component. This was not just for contrib projects, but also for "indie" projects. 


No, I don't recall this being the decision.  At any rate, as earlier emails summarizing my Jira project merge work describe, I re-mapped all tickets from the source indie project to the SAK project target, then whacked the indie project.  I did this by re-mapping in Jira (not in the code) the indie version to the appropriate SAK version based on a release date comparison supplemented by my detailed release notes in Confluence (BLTI example below).  It's not hard to do so long as Jira is working properly, just tedious.  Contrib projects might be a bit trickier to re-map but one could compare signup tag dates (check the svn logs) against Sakai release dates and then re-map the Signup versions in Jira. 

Note that several indies (e.g., common, edu-services et al) were never provided with separate projects and continued to be tracked in the SAK project despite the version "mismatch" between indie release tags and Sakai releases.  So there is nothing new in tracking indie bugs in SAK using the SAK Affected/Fix versions in place of the inde version.  

Anth

[1] https://source.sakaiproject.org/contrib/signup/tags/

Begin forwarded message:

> From: Anthony Whyte <arwhyte at umich.edu>
> Date: September 17, 2013 5:11:11 PM EDT
> To: Developers Sakai-Dev <sakai-dev at collab.sakaiproject.org>, Sakai QA <sakai-qa at collab.sakaiproject.org>
> Cc: sakai-user at collab.sakaiproject.org
> Subject: JIRA: BasicLTI (BLTI) tickets moved to the Sakai (SAK) project; BLTI project deleted
> 
> Take note
> All Jira BasicLTI (BLTI) tickets have been moved to the Sakai (SAK) project.   Henceforward, contributors who need to create, edit, work on or review BasicLTI tickets must use the Sakai (SAK) project.  The BLTI project has been retired and deleted in line with our work aimed at simplifying both our builds and issue tracking.
> 
> What you must do
> When creating a BasicLTI ticket utilize the canonical SAK project and choose the appropriate component--"BasicLTI" or, if appropriate, "internationalization", "translation" or "performance"--and set the ticket's "affects version" to the version of Sakai in which you encountered the issue.  That's it.   
> 
> The CLE team will handle any version translation issues when addressing the ticket (e.g., a reported basiclti 2.9.3 bug gets addressed in trunk and the basiclti-1.3.x branch).
> 
> Re-mapping Jira project versions
> Jira BLTI version fields were re-mapped per the listing below [1].  The re-mapping is based on a review of the master poms of previous Sakai releases where the version of BasicLTI included in the distribution is specified.  Note that the versions listed in the former BLTI project were not exhaustive and masked ticket rollups of a number of off-cycle basiclti tags that were released from time to time. [2]   Except for BasicLTI trunk (re-versioned as 2.10-SNAPSHOT per SAK-23907) this re-mapping exercise is limited to Jira only.  Maintenance branch code has not been touched and will not be touched. 
> 
> Cheers,
> 
> Anth
> 
> _____________________________
> 
> [1] BLTI  Project versions ->  SAK project versions
> 
> 2.2     -> 2.10 [trunk]
> 2.1.2 -> 2.9.4 [tentative]
> 2.1.1 -> 2.9.3
> 2.1.0 -> 2.9.2
> 2.0.1 -> 2.9.1
> 2.0.0 -> 2.9.0
> 1.3.7-> 2.8.4 [tentative]
> 1.3.6 -> 2.8.3
> 1.3.5 -> 2.8.2
> 1.3.4 -> 2.8.1
> 1.3.3 -> 2.8.1 (off-cycle indie release)
> 1.3.1 -> 2.8.0
> 1.1.9 -> 2.7.2
> 1.1.6 -> 2.7.2 (off-cycle indie release)
> 1.1.5 -> 2.7.1
> 1.1.3 -> 2.7.0
> 1.0.0 -> 2.7.0 (off-cycle indie release)
> 0.5.0 -> 2.7.0 (off-cycle indie release)
> 
> [2] For a complete list of BasicLTI tags, see https://source.sakaiproject.org/svn/basiclti/tags/
> 
[3] https://jira.sakaiproject.org/browse/SAK-23907 

anthony whyte | its and mlibrary | university of michigan | arwhyte at umich.edu | 517-980-0228


On Mar 21, 2014, at 10:17 AM, Kirschner, Beth wrote:

> I vaguely remember the decision was made to keep legacy (closed) JIRAs in the separate JIRA project space, but move all open JIRAs into the Sakai project under it's own component. This was not just for contrib projects, but also for "indie" projects. 
> 
> I know that users (not developers) have been confused by having separate JIRA projects defined (sometimes they need to look in the Sakai project, sometimes a separate project, without any understanding of why). Barring any objections on this list (lazy consensus), I think you should:
> 
> 1) Rename "Contrib: Signup" to "Contrib: Signup-legacy"
> 2) Move all open Signup JIRAs into the Sakai project under the Signup component
> 
> I'd also suggest you propose the same course of action for other 'indie' projects (with the exception of Kernel): Lesson Builder, Polls, Profile2, Samigo, Search, Sitestats, Roster2, Delegated Access, 
> 
> - Beth
> 
> On Mar 20, 2014, at 3:44 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> 
>> As contrib projects move to core, IMO they should have their Jira project migrated to a Jira component within the SAK project and issues migrated.
>> 
>> That said Profile2 and a few others are still on their own.
>> 
>> cheers,
>> Steve
>> 
>> 
>> On 21 Mar 2014, at 6:33 am, Neal Caidin <neal.caidin at apereo.org> wrote:
>> 
>>> Hi All,
>>> 
>>> I need some help.
>>> 
>>> I'm not sure if we ever made a decision that Signup issues should be 
>>> reported in Jira under the Sakai project, using the Signup component 
>>> (which does exist), or if we were going to continue using the Signup 
>>> project in Jira to track issues.
>>> 
>>> Which is it? Asking on list, so we can all get on the same page.  Right 
>>> now, I think issues are being reported in the Signup Jira project.  I 
>>> believe we are in the process of "squashing" everything together, which 
>>> is why I thought that Sakai project/Signup component made more sense.
>>> 
>>> Thanks,
>>> Neal
>>> 
>>> -- 
>>> Neal Caidin
>>> Sakai Community Coordinator
>>> Apereo Foundation
>>> neal.caidin at apereo.org
>>> Skype me! (but let me know in advance for the first interaction) - nealkdin
>>> 
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>> 
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140321/1220d768/attachment.html

More information about the sakai-dev mailing list