[sakai2-tcc] Sakai trunk name? - Re: [cle-release-team] [Building Sakai] Removal of indies and project versions

[Aaron Zeckoski]

I think the plan is to begin to collapse projects together where it
makes sense. That will definitely be easier to maintain in the long
run.
I think some projects might stay separate (e.g. kernel) but I am not
sure about that. I would say we probably should just move open issues
over to SAK and then close the old projects and leave them as they are
(so that no one can create or modify the existing issues). This way
all the links don't break (or will JIRA be smart enough to forward the
old links?).

Maybe we just need to experiment on a smaller one first?

-AZ


On Tue, Sep 17, 2013 at 8:08 AM, Steve Swinsburg
<steve.swinsburg at gmail.com> wrote:
> We could adjust the projects to have he one set of version numbers going
> forward, so they don't need to be adjusted individually for each release.
> One update and they all get the new version.
>
> Though, are we planning on collapsing all jira projects into the one now?
> Since that will take care of all of this. Or will that be too intrusive?
> Note that all issue keys will be renamed…
>
> cheers
> S
>
>
>
> On 17/09/2013, at 9:57 PM, Neal Caidin <neal.caidin at apereo.org> wrote:
>
> [ TCC/ PMC and CLE release team]
>
> Hi,
>
> So with the removal of indies and project versions, I presume that Jira
> needs to be updated next to reflect the merged state of the Indies and to
> set the next version number of the release (for tracking purposes). Can we
> wait till just before we release the next major version of Sakai (currently
> called 2.10 or Trunk) or should we do it soon, so that we don't have to do
> double the work in configuring Jira and so we can get word out to the
> community and start explaining the rationale of the name, and a rough idea
> of plans-to-come?
>
> Just asking.
>
> Thanks,
> Neal
>
>
>
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
>
>
>
>
>
>
>
>
>
> On Sep 13, 2013, at 9:53 AM, Steve Swinsburg <steve.swinsburg at gmail.com>
> wrote:
>
> This has been the case for some time, trunk has been the same as trunk all,
> but it will be good to finally simplify this.
>
> Cheers,
> S
>
> Sent from my iPad
>
> On 13/09/2013, at 21:58, Neal Caidin <neal.caidin at apereo.org> wrote:
>
> YES!
>
> The team wants to get rid of TRUNK-ALL because it is redundant.
>
> Cheers,
> Neal
>
>
>
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
>
>
>
>
>
>
>
>
>
> On Sep 13, 2013, at 7:52 AM, Mark Breuker <mbreuker at loi.nl> wrote:
>
> Hi Aaron,
>
> Does this mean that the main code line can now be checked out from TRUNK
> again instead of TRUNK-ALL?
>
> Cheers,
>
> Mark
> Mark Breuker
> Product Owner
> Tel.: +31 71 5451 203
> Leidse Onderwijsinstellingen bv
> Leidsedreef 2
> 2352 BA Leiderdorp
> www.loi.nl________________________________________
> Van: sakai-dev-bounces at collab.sakaiproject.org
> [sakai-dev-bounces at collab.sakaiproject.org] namens Aaron Zeckoski
> [azeckoski at unicon.net]
> Verzonden: donderdag 12 september 2013 21:45
> Aan: Sakai-Dev Developers; cle-release-team at collab.sakaiproject.org
> Onderwerp: [Building Sakai] Removal of indies and project versions
>
> This is a "heads up" (warning) for all developers and contrib tool authors.
>
> With the completion of https://jira.sakaiproject.org/browse/SAK-23907
> we will have removed all indies (projects which were versioned
> separately from the main Sakai version and downloaded as a binary
> instead of built during regular builds) and all indie project versions
> (e.g. sakai.jsf.version) from the corporate POM (a.k.a. master). This
> change includes the kernel. This has been committed to trunk as of
> today and should be working for all core projects.
>
> Any contrib tools which referenced older versions manually (e.g.
> 1.4.0-SNAPSHOT for kernel) or used the project versions will fail to
> build against trunk after today. All non-core code should use the
> Sakai master pom as parent and should not reference versions directly
> but should instead exclude the version for all Sakai dependencies and
> all maven dependency management to handle the versioning.
>
> Look at the projects in the core for examples of the right way to do this.
>
> Let me know if you have any questions.
> -AZ
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> 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"
>
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile