Bill Shannon wrote:
> Carla Mott wrote:
>
>>
>>
>> Hi all,
>>
>> When fixing bugs please update the field 'target milestone'. This
>> is the build where the fix fist appears and is based on the promoted
>> build schedule. Select the value for tne next promoted build (or
>> the current nightly build). If the current nightly is b38 please
>> use that number as the target milestone (your fix will appear in
>> promoted
>> build b38).
>>
>> Since the builds are promoted on Wed and they are started on Tues
>> midnight
>> PST you may want to watch the time of the commit and update accordingly.
>>
>> Updating the target milestone builds helps to accurately record which
>> bugs
>> were fixed in the different releases and gives our users the ability to
>> track what we are doing.
>
>
> Stupid question, but... When I'm about to do a cvs commit, where do I
> look to find out what the next build is going to be? Do I have to go
> to the GlassFish download page, see what the most current build available
> is, and add "1"?
>
> I don't suppose the message that CVS includes at the top of my commit
> comments can be dynamically generated to include the build number that
> my commit will appear in?
>
> How about a file that's part of each module that contains only the build
> number?
Why per module? Won't a file in glassfish/bootstrap dir be enough?
> When a build is promoted, the file could be updated in all
> modules automatically.
Do we not have to update the file just after the code is checked out for
a promoted build? I say this because we don't lock the workspace while a
build is being promoted and promotion process takes 3~4 hours to finish.
Thanks,
Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>