Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-docs-dev] Bugzilla mapping

Thanks Steffen.

BTW, I was thinking that we could evolve the plug-in versions separately from the feature version, which might give us a little more sanity on the planning side.  The benefit might be minimal however, since projects such as EGit and VEX have their own versioning scheme anyways.

David

On Tue, Jan 4, 2011 at 4:42 PM, Steffen Pingel <steffen.pingel@xxxxxxxxxxx> wrote:
Great, then I'll go ahead and create the milestones and versions
accordingly. The benefit of following a separate version scheme is
that WikiText can change API, i.e. bump its version to 2.0,
independently of other Mylyn projects.

Steffen


On Tue, Jan 4, 2011 at 4:36 PM, David Green <david.green@xxxxxxxxxxx> wrote:
> Sounds like there's no benefit to changing the versioning scheme, so we
> should go ahead with making the bugs reflect the proper version of WikiText
> as you suggest.
> David
>
> On Tue, Jan 4, 2011 at 3:47 PM, Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
> wrote:
>>
>> On Tue, Jan 4, 2011 at 3:36 PM, David Green <david.green@xxxxxxxxxxx>
>> wrote:
>> > Steffen,
>> > Would it make things easier to keep the Mylyn versioning scheme?
>>
>> It won't make a difference in terms of effort as far as I know.
>>
>> > So far the
>> > WikiText release cycle has been in lock-step with Mylyn.  It might help
>> > to
>> > eliminate some confusion if we keep it that way.
>>
>> The release cycle is unaffected. I am only wondering about the
>> milestone/version scheme in Bugzilla.
>>
>> > The WikiText feature
>> > version could reflect the Mylyn release version, and the plug-in
>> > versions
>> > could be evolved separately (as they have been).  What do you think?
>>
>> The WikiText feature version has been different all along.
>>
>> It could be equally confusing to see WikiText 1.4 under Installed
>> Software in Eclipse and a 3.5 milestone in Bugzilla. Some of the other
>> Mylyn projects will also follow their own scheme, e.g. Mylyn Reviews
>> or Builds which will start with version 0.7.
>>
>> Steffen
>>
>> >
>> > David
>> > On Tue, Jan 4, 2011 at 3:04 PM, Steffen Pingel
>> > <steffen.pingel@xxxxxxxxxxx>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> as part of bug 332298 we are moving WikiText bugs from the Mylyn
>> >> product to the new Mylyn Docs product. Since WikiText has followed
>> >> it's own versioning scheme I'm wondering if we want to map milestones
>> >> and versions accordingly (see below). The alternative would be to keep
>> >> the Mylyn scheme starting with version/milestone 3.1 .
>> >>
>> >> Thoughts?
>> >>
>> >> Steffen
>> >>
>> >>
>> >> Proposed milesteone mapping:
>> >>
>> >> 3.1.0 > 1.0.0
>> >> 3.1.1 > 1.0.1
>> >> 3.2.0 > 1.1.0
>> >> 3.2.1 > 1.1.1
>> >> 3.2.2 > 1.1.2
>> >> 3.2.3 > 1.1.3
>> >> 3.3.0 > 1.2.0
>> >> 3.3.1 > 1.2.0
>> >> 3.3.2 > 1.2.1
>> >> 3.3.3 > 1.2.1
>> >> 3.4.0 > 1.3.0
>> >> 3.4.1 > 1.3.1
>> >> 3.4.2 > 1.3.2
>> >> 3.5.0 > 1.4.0
>> >>
>> >> All WikiText bugs:
>> >>
>> >>
>> >>
>> >> https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=version&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=Mylyn&product=Mylyn&component=WikiText&longdesc_type=allwordssubstr&longdesc="">
>> >>
>> >> --
>> >> Steffen Pingel
>> >> Committer,
http://eclipse.org/mylyn
>> >> Senior Developer, http://tasktop.com
>> >
>> >
>> >
>> > --
>> > David Green
>> > VP of Engineering, Tasktop
>> > Committer, Eclipse Mylyn
>> > http://tasktop.com
>> >
>>
>>
>>
>> --
>> Steffen Pingel
>> Committer, http://eclipse.org/mylyn
>> Senior Developer, http://tasktop.com
>
>
>
> --
> David Green
> VP of Engineering, Tasktop
> Committer, Eclipse Mylyn
> http://tasktop.com
>



--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com



--
David Green
VP of Engineering, Tasktop
Committer, Eclipse Mylyn
http://tasktop.com


Back to the top