How can I:
1) Upload scripts and CSS to the wiki? For styling, interactivity etc. 2) Colourize C# in the wiki? We could use http://code.google.com/p/google-code-prettify/ Will the wiki be the sole source or are we doing something nicer to the main domain? I'm also curious as to why (except that it was hammett's company before he started at MS) there's a castle stronghold logo on the main site; will it be funding the developers of the castle stack? Cheers, Henrik From: [email protected] [mailto:[email protected]] On Behalf Of Jonathon Rossi Sent: den 31 januari 2010 02:56 To: [email protected] Subject: Re: Finishing off the releases On Sun, Jan 31, 2010 at 11:13 AM, Henrik Feldt <[email protected]> wrote: Hello, No, there should not be that many remaining issues, but I can't tell for sure. I just checked out atlassian and the svn, where has the project moved? Hammett seems to have deleted everything in it. The project hasn't moved. I said we are planning the move, no data has been migrated for any project yet. So, svn write access, you have that. I will clone the git repo, when I find the project files, update it, and push it to the git repo which I assume will update the svn server through the hooks added? I don't quite understand what you are referring to here. The git repos on github are only test repos, don't fork them as per the description. Changes still have to be made on the svn server. You can upload files to sourceforge. Can I get an account at the wiki then so I can add documentation? Since you are in the process of merging it there should be no problem to merge what I write there. Sure, yes there is no problem with your changes being migrated later. What user name would you like? You can update the build configuration, right? Yes. Any of our active committers can do this for you when patches are applied and a branch is made. Most of the things in that guide are for committers; tags, run the team city build, update the svn externals (see question about git/hooks), uploading zip files, announcing the release on the front-page. The question then would be what of that should I do of them? Who to communicate with? If you have changes that need to be made before the release bring these up on the devel list and a committer will be able to commit your changes. Once you are happy that the project is ready to release a committer should be able to set up TeamCity, run a build, upload the package to sf.net and upgrade the web site (home and projects pages). So, could you please write a paragraph about what I should do to release? Summary: . Paragraph . Wiki access . Some questions to be answered . Some discussion questions to be discussed as per previous e-mails I don't know a lot about this area of functionality you are adding. One of the other committers should be able to help. Kind regards Henrik From: [email protected] [mailto:[email protected]] On Behalf Of Jonathon Rossi Sent: den 31 januari 2010 02:07 To: [email protected] Subject: Re: Finishing off the releases On Sun, Jan 31, 2010 at 10:37 AM, Henrik Feldt <[email protected]> wrote: Transactions: I was holding out till Git came around for everything. It doesn't work for me to create manual patches for every little change, plus I can't integrate bugfixes I do (through svn:externals, since I can't commit), nor git's submodules since it's not git. Also, even though I have a branch, I can't commit to it. This is the process other users have followed to become a committer without many issues, how many patches do you think you will have? I think I remember a topic were we said we wanted to make a release of everything before moving to git, so that we stayed focused on getting releases out first, and it gave everyone an incentive to get releases wrapped up and out. I don't have time for patching, re-patching, clicking what files to send along etc. Git would solve these problems as I can have my own repository locally and we don't have to mess with branches, plus you could pull from the repo I have. Could write a paragraph about how to go about with a release, please? Please see the release guide on the web site (http://www.castleproject.org/community/releaseguide.html), let us know if it doesn't cover something. Also, were the split documentation fixed and I can now add pages somewhere through an online editor (i.e. w/o downloading the xml files, messing with them, creating a patch, sending it etc, again I think this is too cumbersome)? Yes, we agree it is too cumbersome, however it is working for the moment. We are planning on trying out moving all the documentation (site docs and current wiki) to a new wiki. This should help remove a lot of friction with writing and updating documentation. I tried logging into confluence at using.castleproject.org, but can't get in, so I can't add pages and documentation. Why have a wiki if it's not a wiki and anyone can edit it? Any registered user can edit the wiki. There was a thread a few months back where I said I had to disable public user registrations because of the uncontrollable spam since the wiki software is from 2007 and doesn't do a good job with spam. If you need an account send me an email with you requested user name. This problem should be fixed in the next few weeks as we move the wiki content onto a new wiki. My point; it's too much work to get to work. Is it possible to remove some friction, please? Yes. Bare with us as we try to make things easier for everyone. Cheers, Henrik -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Simons Sent: den 23 januari 2010 02:22 To: Castle Project Development List Subject: Finishing off the releases There is still a few projects not released: ActiveRecordIntegration AutomaticTransactionManagement NHibernateIntegration Synchronize WCF Integration Transaction Services Could the project leaders of the projects above start planing their releases + update the projects web page with the dates of the release. Obviously ActiveRecordIntegration doesn't have a project leader, so I can take care of its release but the others, what is the delay? If you guys are busy, just let me know and I'll look after the release. Cheers John -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:castle-project-devel%[email protected]> . For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:castle-project-devel%[email protected]> . For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- Jono -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:castle-project-devel%[email protected]> . For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:castle-project-devel%[email protected]> . For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- Jono -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
