Carla Mott wrote:
> It is a bit of a manual process now to go to the download page
> and look to see what the next promoted build number will be.
>
> Dinesh,
>
> Any way we can make this info available in the workspace? What
> would it take and is it worth it?
Currently build_id varible is present in appserv-core/build.properties
which is overriden by nightly build by passing -Dbuild_id=<latest>
So we can have actual build_id in glassfish/bootstrap module in any
common properties file (e.g. we can have this in
glassfish.subcomponent.properties), which is accessed to all modules as
this module needs to be checked out for any workspace command. We can
update this file once build is promoted, so developers can +1 to this in
their checkin comments/target milestone.
thanks
Dinesh
> What to people think about an automatic email notification to the dev
> alias when the builds are posted? Each night you get an email when
> the build is copied to the download server and on Wed there would be
> an additional notification that the promoted builds are out. Would
> this be a reasonable alternative?
>
> Carla
>
> Sanjeeb Kumar Sahoo wrote:
>
>> 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
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>