Hi,
2014-06-05 3:11 GMT+02:00 Misagh Moayyed <[email protected]>: > …oh, one more thing to consider: > > > > - Rather than providing binary downloadable artifacts per release > on the jasig website, it seems like the release engineer for a given CAS > release has all the right permissions and tools to take advantage of the > Github’s releases feature, where the binary artifact, cas-webapp as well as > release notes can directly be hosted and uploaded there. The jasig website > could then perhaps just include a link to the latest release, or to the > download area. > If you have to create a link in the Jasig web site, I'm not sure to see the benefit: using the text editor for the web site is a bit painful, either for just a link or a more complete description... > > > My objective really is to try and simplify the release process, by keeping > code, docs, and artifacts all close in the same spot and seems like Github > serves this need quite well for the time being. I imagine this would also > be much easier for CAS users as well, where they get the code, docs, and > the downloadable artifact and release notes (Just the piece that is > uploaded to the jasig wiki that is) all from the same place. > I'm in line with your objective, but we didn't talk about the worse part from my point of view: the Maven release prepare and perform tasks... Best regards, -- Jérôme LELEU Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
