[cle-release-team] bind to stable master

Steve Swinsburg steve.swinsburg at gmail.com
Mon Jul 2 19:32:56 PDT 2012


Yeah there are definitely some projects in there that don't really need to be indies. I also think portal should be deindified.

cheers,
S

On 03/07/2012, at 12:04 PM, Matthew Jones wrote:

> I'm about to propose tonight that we get rid of most indies entirely, aside from maybe kernel and the 10 other projects that have no dependencies on anything other than kernel.
> 
> Basically everything on the top of the list:
> https://confluence.sakaiproject.org/display/REL/Indie+release+order+-+2.9 
> 
> We can't bind the snapshots to fixed versions of master because the properties are defined in the master. And the api and the implementation are the same version. And we don't monitor api changes anyway, so many are modified in the minor releases.
> 
> In 2.7 and 2.8, these properties were all maintained in the master, 4 pure-poms and in the local projects. It seemed like centralizing them would be easier, but it doesn't seem like there's any build process that works for both the organizations that customize the release (most of the SCAs that are doing this release work anyway) and the ones that don't customize the release.
> 
> The .x branch is supposed to be SNAPSHOTS but we shouldn't have all of the properties and dependencyManagement defined in master. This was just a convenience because so few people are actually working on Sakai and even fewer are releasing EVERY project. 
> 
> Just trying to revert all of these master parents tonight is giving me a headache.
> 
> Its super easy to release 1 tool/project. It's exhausting releasing 30.
> 
> On Mon, Jul 2, 2012 at 9:33 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> Hi all,
> 
> I'd like to propose that we bind projects for 2.9 and 2.10 to a stable master version, not a snapshot.
> 
> This will reduce the amount of setup required for Jenkins builds (we can remove the pre/post build steps), plus it aligns our Maven use with that of Jasig:
> https://wiki.jasig.org/display/JSG/Using+Maven+for+your+Jasig+project
> 
> This is what I was talking about at the conference when I suggested the release process was too complex.
> 
> cheers,
> Steve
> 
> 
> 
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20120703/1ef9199f/attachment-0006.html 


More information about the cle-release-team mailing list