[sakai-pmc] PROPOSAL: svn cleanup

Kirschner, Beth bkirschn at umich.edu
Tue Dec 10 12:28:27 PST 2013


On Dec 9, 2013, at 6:01 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:

> Megan: Thanks for the note. I'll wait to hear from UMich about that project.
> 
UM is not using https://source.sakaiproject.org/svn/gradtools - it can be removed (we are using https://source.sakaiproject.org/svn/msub/umich.edu/ctools/gradtools/ -- looks like that was created in 2009).

> Matt: I was going to use svnadmin to do it but the easier option is to just move them into a /svn/deprecated folder, so will do that for now.
> 
I like the /svn/deprecated option

> Cris: The only ones are hybrid and pure-poms so in the interest of simplicity, those will be dropped from this proposal and can be moved when 2.9 becomes unsupported. I dislike updating tags - if there is another 2.9 release they could possibly be adjusted then.
> 
> Seth: Is this a -1 to the whole proposal or just specific parts? We have historically moved projects that are deprecated, but haven't for some time (see the existing contrib/deprecated folder). This brings us up to date with that practice. 
> 
> cheers,
> Steve
> 
> 
> On Tue, Dec 10, 2013 at 4:14 AM, Seth Theriault <slt at columbia.edu> wrote:
> On Mon, Dec 9, 2013 at 10:27 AM, Matthew Jones <matthew at longsight.com> wrote:
> > Rather than move them to contrib, which would lose the history unless we/you
> > use svnadmin to dump and reload into contrib (which you may or may not be
> > considering), perhaps keeping them in that repo and moving them all into
> > /svn/deprecated or /svn/msub/deprecated would be a better/easier idea.
> 
> I don't see any real reasons to specifically move these projects to
> contrib. It just creates more work and ways to break things.
> 
> Seth
> 
> 
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc



More information about the sakai-pmc mailing list