[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] new target milestones in bugzilla
|
According to Wayne, only bug fixes in a Service Release.
So if you are contributing to SR1 and SR2, you can only contribute bug
fixes, no new features or functionality.
This doesn't stop you from releasing in 3 months, a 1.1.0 that contains
new features, and bug fixes, but it does mean you'll have to have a
maintenance branch, and a 1.1.x development branch.
As a side note, bug fixes in a service release don't have to go through
IP review or release process, if you do a 1.1.0 then that will need to
go through the full release process.
Dave
On 06/28/2011 11:45 AM, Igor Fedorenko wrote:
I don't believe this is the case. To the best of my knowledge, we can
release m2e 1.1.0 in September with new features/etc, should we decide
this is necessary.
Also, as I mentioned already, helping writing new m2e extensions is our
highest priority at the moment and we schedule our work accordingly.
We'll make selective bugfixes, but otherwise anything that does not help
writing m2e extensions will have to wait until there is enough
documentation, examples, fixes to the mapping logic and so on.
--
Regards,
Igor
On 11-06-28 7:23 PM, David Carver wrote:
The only down fall to this approach is that it means in eclipse
terminology no new Features or enhancements. Only bug fixes. Many of the
requests I'm seeing on m2e-users are not necessarily bugs, but
enhancement/feature requests.
So in this case, any Enhancements or new functionality, would need to go
into a new branch for Juno.
Dave
On 06/28/2011 09:14 AM, Igor Fedorenko wrote:
Cool. Created Indigo SR1/SR2 milestones.
--
Regards,
Igor
On 11-06-28 5:07 PM, Milos Kleint wrote:
On Jun 27, 2011, at 3:36 PM, Igor Fedorenko wrote:
Guess my message came out little confusing. Let me try again
I would like to propose keeping single development stream both for
Indigo SR1 and Juno work and only do 100% backwards compatible
bugfixes
and enhancements. We'll use version
1.0.100.qualifier/1.0.200.qualifier
in the code and "Indigo SR1"/"Indigo SR2" milestones in bugzilla. Our
Juno contributions will be aligned with Indigo SR work and we'll
decide
what to do next after SR2 is out next February.
Any concerns, comments, objections?
+1 on having the bugzilla names "Indigo SR1/Indigo SR2"
Having just one stream sounds like a good idea too.. of course only
until we find out we need 2 streams :)
Milos
--
Regards,
Igor
On 11-06-24 3:16 PM, Igor Fedorenko wrote:
We need to decide on versions first.
As suggested by Pascal, SR1 version will be 1.0.100, so we have some
room to deliver new maven runtimes and hotfixes off marketplace.
What version should we use for Juno? 1.1.0? Do we even want separate
vesrions for Indigo sr1 and Juno?
-- Sent from my SGS Milos Kleint<milos@xxxxxxxxxxxx> wrote:
hello,
can someone add new target milestones for m2e in bugzilla? or
instruct me how to do it myself? The current targets are only
0.13, we probably need some post 1.0.0 ones. I would suggest
1.0.1 and/or 1.1
Regards
Milos
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
