| Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? |
|
Both "you must integrate often" and "you must use OSGi version convention" are already Simrel rules. Simrel process is filled with rules that half the projects ignore. Enforcement is difficult since the only available stick is to drop the project and everything that depends on it from Simrel, yet no one wants to see Simrel reduced to a fraction of projects that it currently contains and be in a state where we can't even produce some of the most popular packages.
The current simrel process was designed at a time when there were significantly fewer projects, these projects were well staffed and everyone following the platform's release schedule. That's not today. The modern simrel should have fewer rules (let's accept the reality) and be able to accommodate projects that have radically different release cadence. Both very active projects that release every month and projects that release once every few years should be able to participate at their own pace.
Thanks,
- Konstantin From: cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of Stephan Herrmann <stephan.herrmann@xxxxxxxxx>
Sent: Saturday, December 16, 2017 4:54 PM To: cross-project-issues-dev@xxxxxxxxxxx Subject: Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? Another option could be: even "inactive" projects could be required,
to perform builds against each SimRel milestone, even when contributing a previous version. This should ensure that code still works (compiles and passes tests) against updated dependencies. I don't think this should be much of a burden on "maintainers". Stephan On 16.12.2017 17:43, Konstantin Komissarchik wrote: > Dani, > > > DTD did participate in Oxygen, but DTP is in maintenance mode with no one actively working on it. The only time a new build or > release is made is when a critical need arises. Such event happened in Oxygen M4 with Lucene changes, so DTP produced a 1.14 build > at that point and went dormant again. In particular, it was not rebuilt with the following milestones. > > > In my opinion, the deprecate and announce policy of API removal isn't effective for projects like DTP. There is a huge code base. > Only a small part is going to be examined and only when something breaks. There is no one to notice the deprecation warnings. > Similarly, when the announcement comes, it relies on someone either (a) recognizing that their project depends on that API, or (b) > proactively searching through the code base for references. Neither of these is very likely to happen for a maintenance mode > project. What would have helped is strict adherence to OSGi versioning convention (major version bump) as that would have broken DTP > aggregation and triggered a need for a rebuild, so problematic references would have been caught and fixed. > > > Thanks, > > > - Konstantin > > > > > ------------------------------------------------------------------------------------------------------------------------------------ > *From:* cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of Daniel Megert > <daniel_megert@xxxxxxxxxx> > *Sent:* Saturday, December 16, 2017 9:25 AM > *To:* Cross project issues > *Subject:* Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? > Hi Konstantin > > Did DTP not participate in Oxygen in June? There the class was already deleted, so, DTP should have run into this in June already. > > Note that we announced the deletion on this mailing list. > > Dani > > > > From: Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> > To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx> > Date: 15.12.2017 17:46 > Subject: Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? > Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx > ------------------------------------------------------------------------------------------------------------------------------------ > > > Dani, > > It wasn’t an internal. It was a deprecated class that was removed. Since DTP isn’t actively being developed, no one saw the > deprecation warnings. A major version bump would have allowed the removal to be caught earlier… > > org.eclipse.jface.util.ListenerList (removed) > > org.eclipse.core.runtime.ListenerList (replacement) > > > Thanks, > > - Konstantin > > *From: *_Daniel Megert_ <mailto:daniel_megert@xxxxxxxxxx>* > Sent: *Friday, December 15, 2017 3:17 AM* > To: *_Cross project issues_ <mailto:cross-project-issues-dev@xxxxxxxxxxx>* > Subject: *Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? > >> platform made an API change after that which broke some of the DTP functionality > > Do you have a bug report for that? The platform usually doesn't break APIs. Did DTP maybe use internals? > > Dani > > > > From: Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> > To: "cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx> > Date: 14.12.2017 22:11 > Subject: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? > Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx > > Could someone forward this to the Planning Council, please? > > I am currently working with Nick Boldt to transition DTP releng responsibility. In the meantime, the version of DTP in Oxygen.2 has > compatibility issues. It was last build with Oxygen.0.M4 and platform made an API change after that which broke some of the DTP > functionality. The 1.14.1 release that contains the fix is ready to go. Since EGit has initiated a respin, would it be possible for > DTP to join. The change is low risk. Basically changing package names for a class that now must be found in a different plugin and > corresponding version updates. > > Thanks, > > - Konstantin > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit_ > __https://eur03.safelinks.protection.outlook.com/?url="" > <https://nam01.safelinks.protection.outlook.com/?url="">> > > [attachment "FFF7BF32D87F47C29797A125AC60E634.png" deleted by Daniel Megert/Zurich/IBM] > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://eur03.safelinks.protection.outlook.com/?url=""> > <https://nam01.safelinks.protection.outlook.com/?url="">> > > > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://eur03.safelinks.protection.outlook.com/?url=""> > _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://eur03.safelinks.protection.outlook.com/?url=""> |