<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Good point. I actually considered introducing this kind of scheme in the VersionInfo field, but got vexed by the<BR>
<BR>
"Keep to 27 chars"<BR>
<BR>
comment.<BR>
<BR>
Anybody knows about that? Why 27? Would less be critical? More?<BR><BR>
If we can manage it reasonably, I would like to introduce an Enum just tagging release-type to that string.<BR>
<BR>
Other than that, the revision number should be in there.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR><BR><BR><BR> <BR>> Date: Wed, 11 Mar 2009 15:11:56 -0400<BR>> From: coyle+opensim@knifejaw.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Proposal: Light-weight Release Cycle<BR>> <BR>> On 2009-03-11 07:49:46 -0400, stefan@tribalmedia.se wrote:<BR>> > 7) The "-release" tag is branched to a "-post-fixes" branch for continued<BR>> > service awaiting the next cycle.<BR>> <BR>> May I request that anything committed to -post-fixes after branching<BR>> result in an incremented tag (0.6.4.1-release or 0.6.4a-release or<BR>> something) & accompanying change in VersionInfo.cs? Otherwise one<BR>> has no way of knowing whether someone is running the tagged release<BR>> or one of the versions that came out of the -post-fixes branch. There<BR>> was a lot of confusion in #opensim with 0.6.3 because changes were<BR>> committed to the -post-fixes branch but the versions both before and<BR>> after the commit were referred to as "0.6.3".<BR>> <BR>> Thanks.<BR>> <BR>> -Coyle<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></body>
</html>