JIRA maintenance

[Sean Schofield <se...@gmail.com>]

Manfred,

If we're going to use the 1.0.10 version in JIRA here is what I
suggest.  Find any issue that is currently marked with that version
and change to nightly (there shouldn't be many since you just added
it.)  Then edit the versions and rename nightly to 1.0.10.  This way
all of the issues marked nightly will be changed to 1.0.10 without
adding a log entry in JIRA and sending new emails.

Either we have a Nightly and change later (like I was suggesting) or
we abandon Nightly and have just 1.0.10.  I'm ok with dropping nightly
if you and Oliver feel that this is the way to go but we have to fix
it now so we don't have to manually change all of the ones marked
"nightly" later on down the road.  Better to manually fix the one or
two marked 1.0.10 then the dozens marked nightly.

sean

Re: JIRA maintenance

[Manfred Geiler <ma...@gmail.com>]

+1 for "Nightly build" and renaming it just in time
This procedure also allows us to adapt the actual release number later
whenever we are not sure if the next release will be a bug fix or a
feature release.
-Manfred

2005/5/22, Sean Schofield <se...@gmail.com>:
> Yes we're all agreed on "M" as well.  At least that was the decision
> for the last release.  I can't imagine that we'll change that.
> 
> sean
> 
> On 5/20/05, Grant Smith <gr...@marathon-man.com> wrote:
> > +1 for keeping it "Nightly build", then renaming it when we release
> > 1.0M10 (we're at 1.0M9 now, right ? I thought we all agreed on the "M"...)
> >
> >
> >
> > Sean Schofield wrote:
> >
> > >Yes I suggest we keep it Nightly Build as well because we actually
> > >have a nightly build that users can grab and the issue will be fixed
> > >there.
> > >
> > >sean
> > >
> > >On 5/20/05, Martin Marinschek <ma...@gmail.com> wrote:
> > >
> > >
> > >>+1 for renaming the nightly version to 1.0.x when the time has come
> > >>(Sean's suggestion)
> > >>
> > >>+1 for keeping the name "Nighly Build" - in fact it will be fixed in
> > >>this nightly's build, so there should not be too many misconceptions.
> > >>
> > >>regards,
> > >>
> > >>Martin
> > >>
> > >>On 5/20/05, Oliver Rossmueller <ol...@tuxerra.com> wrote:
> > >>
> > >>
> > >>>Sean Schofield wrote:
> > >>>
> > >>>
> > >>>
> > >>>>Manfred,
> > >>>>
> > >>>>If we're going to use the 1.0.10 version in JIRA here is what I
> > >>>>suggest.  Find any issue that is currently marked with that version
> > >>>>and change to nightly (there shouldn't be many since you just added
> > >>>>it.)
> > >>>>
> > >>>>
> > >>>>
> > >>>Sean,
> > >>>
> > >>>actually it was me who created the 1.0.10 entry.
> > >>>
> > >>>
> > >>>
> > >>>>Then edit the versions and rename nightly to 1.0.10.  This way
> > >>>>all of the issues marked nightly will be changed to 1.0.10 without
> > >>>>adding a log entry in JIRA and sending new emails.
> > >>>>
> > >>>>Either we have a Nightly and change later (like I was suggesting) or
> > >>>>we abandon Nightly and have just 1.0.10.  I'm ok with dropping nightly
> > >>>>if you and Oliver feel that this is the way to go but we have to fix
> > >>>>it now so we don't have to manually change all of the ones marked
> > >>>>"nightly" later on down the road.  Better to manually fix the one or
> > >>>>two marked 1.0.10 then the dozens marked nightly.
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>I was not aware it is possible to rename a version in Jira. If it works
> > >>>that way I'm fine with using the scheme you suggested. But shouldn't we
> > >>>rename "Nighly Build" to "Upcoming release" then to avoid any doubts a
> > >>>user might have about the meaning of "Fixed in Nightly Build" ?
> > >>>
> > >>>Oliver
> > >>>
> > >>>
> > >>>
> > >>>>sean
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>--
> > >>>Oliver Rossmueller
> > >>>Software Engineer and IT-Consultant
> > >>>Hamburg, Germany
> > >>>http://www.rossmueller.com
> > >>>
> > >>>
> > >>>
> > >>>
> > >
> > >.
> > >
> > >
> > >
> >
> >
>

Re: JIRA maintenance

[Sean Schofield <se...@gmail.com>]

Yes we're all agreed on "M" as well.  At least that was the decision
for the last release.  I can't imagine that we'll change that.

sean

On 5/20/05, Grant Smith <gr...@marathon-man.com> wrote:
> +1 for keeping it "Nightly build", then renaming it when we release
> 1.0M10 (we're at 1.0M9 now, right ? I thought we all agreed on the "M"...)
> 
> 
> 
> Sean Schofield wrote:
> 
> >Yes I suggest we keep it Nightly Build as well because we actually
> >have a nightly build that users can grab and the issue will be fixed
> >there.
> >
> >sean
> >
> >On 5/20/05, Martin Marinschek <ma...@gmail.com> wrote:
> >
> >
> >>+1 for renaming the nightly version to 1.0.x when the time has come
> >>(Sean's suggestion)
> >>
> >>+1 for keeping the name "Nighly Build" - in fact it will be fixed in
> >>this nightly's build, so there should not be too many misconceptions.
> >>
> >>regards,
> >>
> >>Martin
> >>
> >>On 5/20/05, Oliver Rossmueller <ol...@tuxerra.com> wrote:
> >>
> >>
> >>>Sean Schofield wrote:
> >>>
> >>>
> >>>
> >>>>Manfred,
> >>>>
> >>>>If we're going to use the 1.0.10 version in JIRA here is what I
> >>>>suggest.  Find any issue that is currently marked with that version
> >>>>and change to nightly (there shouldn't be many since you just added
> >>>>it.)
> >>>>
> >>>>
> >>>>
> >>>Sean,
> >>>
> >>>actually it was me who created the 1.0.10 entry.
> >>>
> >>>
> >>>
> >>>>Then edit the versions and rename nightly to 1.0.10.  This way
> >>>>all of the issues marked nightly will be changed to 1.0.10 without
> >>>>adding a log entry in JIRA and sending new emails.
> >>>>
> >>>>Either we have a Nightly and change later (like I was suggesting) or
> >>>>we abandon Nightly and have just 1.0.10.  I'm ok with dropping nightly
> >>>>if you and Oliver feel that this is the way to go but we have to fix
> >>>>it now so we don't have to manually change all of the ones marked
> >>>>"nightly" later on down the road.  Better to manually fix the one or
> >>>>two marked 1.0.10 then the dozens marked nightly.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>I was not aware it is possible to rename a version in Jira. If it works
> >>>that way I'm fine with using the scheme you suggested. But shouldn't we
> >>>rename "Nighly Build" to "Upcoming release" then to avoid any doubts a
> >>>user might have about the meaning of "Fixed in Nightly Build" ?
> >>>
> >>>Oliver
> >>>
> >>>
> >>>
> >>>>sean
> >>>>
> >>>>
> >>>>
> >>>>
> >>>--
> >>>Oliver Rossmueller
> >>>Software Engineer and IT-Consultant
> >>>Hamburg, Germany
> >>>http://www.rossmueller.com
> >>>
> >>>
> >>>
> >>>
> >
> >.
> >
> >
> >
> 
>

Re: JIRA maintenance

[Grant Smith <gr...@marathon-man.com>]

+1 for keeping it "Nightly build", then renaming it when we release 
1.0M10 (we're at 1.0M9 now, right ? I thought we all agreed on the "M"...)



Sean Schofield wrote:

>Yes I suggest we keep it Nightly Build as well because we actually
>have a nightly build that users can grab and the issue will be fixed
>there.
>
>sean
>
>On 5/20/05, Martin Marinschek <ma...@gmail.com> wrote:
>  
>
>>+1 for renaming the nightly version to 1.0.x when the time has come
>>(Sean's suggestion)
>>
>>+1 for keeping the name "Nighly Build" - in fact it will be fixed in
>>this nightly's build, so there should not be too many misconceptions.
>>
>>regards,
>>
>>Martin
>>
>>On 5/20/05, Oliver Rossmueller <ol...@tuxerra.com> wrote:
>>    
>>
>>>Sean Schofield wrote:
>>>
>>>      
>>>
>>>>Manfred,
>>>>
>>>>If we're going to use the 1.0.10 version in JIRA here is what I
>>>>suggest.  Find any issue that is currently marked with that version
>>>>and change to nightly (there shouldn't be many since you just added
>>>>it.)
>>>>
>>>>        
>>>>
>>>Sean,
>>>
>>>actually it was me who created the 1.0.10 entry.
>>>
>>>      
>>>
>>>>Then edit the versions and rename nightly to 1.0.10.  This way
>>>>all of the issues marked nightly will be changed to 1.0.10 without
>>>>adding a log entry in JIRA and sending new emails.
>>>>
>>>>Either we have a Nightly and change later (like I was suggesting) or
>>>>we abandon Nightly and have just 1.0.10.  I'm ok with dropping nightly
>>>>if you and Oliver feel that this is the way to go but we have to fix
>>>>it now so we don't have to manually change all of the ones marked
>>>>"nightly" later on down the road.  Better to manually fix the one or
>>>>two marked 1.0.10 then the dozens marked nightly.
>>>>
>>>>
>>>>        
>>>>
>>>I was not aware it is possible to rename a version in Jira. If it works
>>>that way I'm fine with using the scheme you suggested. But shouldn't we
>>>rename "Nighly Build" to "Upcoming release" then to avoid any doubts a
>>>user might have about the meaning of "Fixed in Nightly Build" ?
>>>
>>>Oliver
>>>
>>>      
>>>
>>>>sean
>>>>
>>>>
>>>>        
>>>>
>>>--
>>>Oliver Rossmueller
>>>Software Engineer and IT-Consultant
>>>Hamburg, Germany
>>>http://www.rossmueller.com
>>>
>>>
>>>      
>>>
>
>.
>
>  
>

Re: JIRA maintenance

[Sean Schofield <se...@gmail.com>]

Yes I suggest we keep it Nightly Build as well because we actually
have a nightly build that users can grab and the issue will be fixed
there.

sean

On 5/20/05, Martin Marinschek <ma...@gmail.com> wrote:
> +1 for renaming the nightly version to 1.0.x when the time has come
> (Sean's suggestion)
> 
> +1 for keeping the name "Nighly Build" - in fact it will be fixed in
> this nightly's build, so there should not be too many misconceptions.
> 
> regards,
> 
> Martin
> 
> On 5/20/05, Oliver Rossmueller <ol...@tuxerra.com> wrote:
> > Sean Schofield wrote:
> >
> > >Manfred,
> > >
> > >If we're going to use the 1.0.10 version in JIRA here is what I
> > >suggest.  Find any issue that is currently marked with that version
> > >and change to nightly (there shouldn't be many since you just added
> > >it.)
> > >
> > Sean,
> >
> > actually it was me who created the 1.0.10 entry.
> >
> > >Then edit the versions and rename nightly to 1.0.10.  This way
> > >all of the issues marked nightly will be changed to 1.0.10 without
> > >adding a log entry in JIRA and sending new emails.
> > >
> > >Either we have a Nightly and change later (like I was suggesting) or
> > >we abandon Nightly and have just 1.0.10.  I'm ok with dropping nightly
> > >if you and Oliver feel that this is the way to go but we have to fix
> > >it now so we don't have to manually change all of the ones marked
> > >"nightly" later on down the road.  Better to manually fix the one or
> > >two marked 1.0.10 then the dozens marked nightly.
> > >
> > >
> > I was not aware it is possible to rename a version in Jira. If it works
> > that way I'm fine with using the scheme you suggested. But shouldn't we
> > rename "Nighly Build" to "Upcoming release" then to avoid any doubts a
> > user might have about the meaning of "Fixed in Nightly Build" ?
> >
> > Oliver
> >
> > >sean
> > >
> > >
> >
> >
> > --
> > Oliver Rossmueller
> > Software Engineer and IT-Consultant
> > Hamburg, Germany
> > http://www.rossmueller.com
> >
> >
>

Re: JIRA maintenance

[Martin Marinschek <ma...@gmail.com>]

+1 for renaming the nightly version to 1.0.x when the time has come
(Sean's suggestion)

+1 for keeping the name "Nighly Build" - in fact it will be fixed in
this nightly's build, so there should not be too many misconceptions.

regards,

Martin

On 5/20/05, Oliver Rossmueller <ol...@tuxerra.com> wrote:
> Sean Schofield wrote:
> 
> >Manfred,
> >
> >If we're going to use the 1.0.10 version in JIRA here is what I
> >suggest.  Find any issue that is currently marked with that version
> >and change to nightly (there shouldn't be many since you just added
> >it.)
> >
> Sean,
> 
> actually it was me who created the 1.0.10 entry.
> 
> >Then edit the versions and rename nightly to 1.0.10.  This way
> >all of the issues marked nightly will be changed to 1.0.10 without
> >adding a log entry in JIRA and sending new emails.
> >
> >Either we have a Nightly and change later (like I was suggesting) or
> >we abandon Nightly and have just 1.0.10.  I'm ok with dropping nightly
> >if you and Oliver feel that this is the way to go but we have to fix
> >it now so we don't have to manually change all of the ones marked
> >"nightly" later on down the road.  Better to manually fix the one or
> >two marked 1.0.10 then the dozens marked nightly.
> >
> >
> I was not aware it is possible to rename a version in Jira. If it works
> that way I'm fine with using the scheme you suggested. But shouldn't we
> rename "Nighly Build" to "Upcoming release" then to avoid any doubts a
> user might have about the meaning of "Fixed in Nightly Build" ?
> 
> Oliver
> 
> >sean
> >
> >
> 
> 
> --
> Oliver Rossmueller
> Software Engineer and IT-Consultant
> Hamburg, Germany
> http://www.rossmueller.com
> 
>

Re: JIRA maintenance

[Oliver Rossmueller <ol...@tuxerra.com>]

Sean Schofield wrote:

>Manfred,
>
>If we're going to use the 1.0.10 version in JIRA here is what I
>suggest.  Find any issue that is currently marked with that version
>and change to nightly (there shouldn't be many since you just added
>it.)  
>
Sean,

actually it was me who created the 1.0.10 entry.

>Then edit the versions and rename nightly to 1.0.10.  This way
>all of the issues marked nightly will be changed to 1.0.10 without
>adding a log entry in JIRA and sending new emails.
>
>Either we have a Nightly and change later (like I was suggesting) or
>we abandon Nightly and have just 1.0.10.  I'm ok with dropping nightly
>if you and Oliver feel that this is the way to go but we have to fix
>it now so we don't have to manually change all of the ones marked
>"nightly" later on down the road.  Better to manually fix the one or
>two marked 1.0.10 then the dozens marked nightly.
>  
>
I was not aware it is possible to rename a version in Jira. If it works 
that way I'm fine with using the scheme you suggested. But shouldn't we 
rename "Nighly Build" to "Upcoming release" then to avoid any doubts a 
user might have about the meaning of "Fixed in Nightly Build" ?

Oliver

>sean
>  
>


-- 
Oliver Rossmueller
Software Engineer and IT-Consultant
Hamburg, Germany
http://www.rossmueller.com