The fact that the entire process is manual and has so many steps and so many things to look after and take care of is PITA. It took me a few hours to get this thing out the door. Uploading to SF is just one thing, but pretty much everything can be automated, including making announcement on the groups and updating website.
Having numbers on builds between different versions just minimizes overhead when trying to work out issues people have. Being able to correlate build number to source code revision is very important IMO. Krzysztof 2010/8/23 John Simons <[email protected]>: > Is it really a big no no if the build number is different when we release > several version of the same project? > Just asking! > > John > > ________________________________ > From: Krzysztof Koźmic <[email protected]> > To: Castle Project Devel <[email protected]> > Sent: Sun, 22 August, 2010 9:26:34 PM > Subject: some thoughts on our build process > > Hey, > > having gone throuh the pain of releasing Core and Windsor today I wanted to > say one thing - it's extremely painful to go thought. All the (many) steps > are manual and require a lot of time to complete. It took me half of the day > to get it all working and out the door. That's not how it should be. I > chatted with Roelof and he proposed that we should look into automating as > much of the process as possible. I couldn't agree more. > > We should also change how we assing build numbers. Currently we use > autoincremented builds count from TeamCity which has the drawback that if we > release several version of the same project (for .NET 3.5, 4.0, 4.0 CP, two > versions of SIlverlight, possibly Mono in the future) all of them have > different numbers. For the release I manually set up the counter to be the > same for all builds but we should have it done automatically. > > This is a major issue and to keep shipping the software on a sustainable > pace we need to streamline and automate it a lot. > > Comments and ideas welcome. > > Krzysztof > > -- 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. > -- 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.
